bitchat now has regional chat, using geohashes and nostr (kind 20000). in TestFlight. https://github.com/permissionlesstech/bitchat/releases/tag/v1.3.0
So I can teleport (join) any geohash and chat there with others who are there?
Welcome!
💯
Wait for it when the kids get in touch with the technology we love the most
Spun back up the archive relay, also added a sync step to pull events from other relays https://hole.v0l.io/
Is this relay trying to archive every event it can find?
On my last bicycle tour I used my old Wahoo Elemnt Bolt computer to track my ride and I was really weirded by out the result because it definitely didn't track the actual route I rode.
Now I know it's a firmware issue: https://support.wahoofitness.com/hc/en-us/articles/28876447336210-ELEMNT-BOLT-1-and-ROAM-1-GPS-data-and-ride-recording-issues-August-17-and-later
Perhaps I shouldn't have done that firmware update the day before the ride.
My dad purchased a Bolt 3 of this issue 🤣
Google is killing the open web
It’s almost one year ago I advertised this Nostr message on a billboard near the highway 🤓 #memories
Creating highlights / annotations from Safari on iOS with nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0 🤙🏻
Thx for showing this nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe, I didn’t know this feature (but I don’t use Safari as my default browser tho).
How? 👀 Can you share a screencast demo with this? I don't have (or can find) this feature on my iOS device.
Didn't expect to be Denmark so low on this list regarding employee costs...
Same question here!
There is some bookmarklet here for Lantern https://git.fiatjaf.com/lantern (see readms) but its for bookmarking only. But I guess this could also work for creating highlights too
Yes! I do Zwift competitions / races in the winter.
Outbox is harder than it should be just because devs make their first versions with a hardcoded relay list expecting that later they will just "add outbox".
Nah... you won't. You fucked up. Now you need to rewrite everything because your architecture cannot handle it. It's as simple as that.
Outbox requires many layers of indirections: Before loading the feed, you need to load the NIP-65 event, and before loading the NIP-65 event you need to figure out the user's home relay to get the most up-to-date NIP-65 event from. You will need to setup those layers from the beginning.
More importantly: your relay pool will change from post to post. You will need to quickly disconnect and connect to relays as the use slides through their feed.
To see all replies of a thread, you will connect to all of the inbox relays of each participant in that thread. That's the only way to see everything.
The same pool must keep Bunker connections alive at all times and randomly connect to Nostur Wallet Connect relays to send zaps.
If you are crazy enough to implement multiple NIPs, like Amethyst and Nostur do, each NIP will have their own ways of defining which list should be used. You will need different bootstrapping relays for each NIP.
Our nostr libraries are terrible. They are almost all still based in the old thinking of a fixed relay pool. Even the modern AI stuff from nostr:nprofile1qqsqgc0uhmxycvm5gwvn944c7yfxnnxm0nyh8tt62zhrvtd3xkj8fhgprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30hyvdwq still uses fixed relay lists. That will drive your code into a direction that will be very hard if not impossible to fix later.
We can fix this. But it is hard to fix when every client also operates a main relay to centralize things on. Things get built around that relay and people forget to decentralize. It's sad. But this error is so common that it's not even fun anymore.
Every client needs to help users setup their relay lists. Every client MUST use the user's relay lists that other clients already helped him/her setup. Ignoring the user settings from a different client will only make your code unfixable overtime.
The happy path is evil. And if you go down into that direction, it will consume your soul.
How can users be incentived to setup their own relay list? It’s really complicated when they don’t have any meaning yet of what relays are. So it’s not only about incentives but also the ability to learn something new in a digital context of sending letters through post offices. Or knowing what pidgeon you have to use to deliver a message.
And this is a cool PoC
5a3290295d4d8b28b696d4d13fe3fa9294b67f672b730dc676953697b96f6ac4 by nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9
Correct:
nevent1qvzqqqqqqypzqun2rcnpe3j8ge6ws2z789gm8wcnn056wu734n6fmjrgmwrp58q3qyv8wumn8ghj7enfd36x2u3wdehhxar
And this is a cool PoC
5a3290295d4d8b28b696d4d13fe3fa9294b67f672b730dc676953697b96f6ac4 by nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9
GM
I've updated the profile picture and banner URL in the event kind 0 metadata for nostr:npub1phpdev2d38u5hzs4jrsh360mevh0rjctu9669quy97wu23u8sqdqpfha0j which now points to Blossom served images. Which clients does support to fallback to other Blossom servers if that domain is not available (or the file is not available anymore) to serve these pictures specific from kind 0 events just like how it's done with referenced blobs in content fields of events?
#devstr #nostrdev
/cc nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl
Thoughts?
How to become your own ISP.
This is very educational talk with a lot of resources how the current internet networking works.
I was expecting a short docu about the AI bubble, but it turned out to be a brief explainer how the monetary system is creating this bubble (inflation, money printing, QE).
Test 2 🤓
Test 🤓
Shosho is a mobile streaming app built on nostr. Who has tried?
nostr:npub1r0d8u8mnj6769500nypnm28a9hpk9qg8jr0ehe30tygr3wuhcnvs4rfsft nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
Download for android on https://zapstore.dev nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8, or TestFlight on iOS https://testflight.apple.com/join/Cg4Ng6dq
I’ve tested it 2-3 times
NOW HIRING: Developer Advocate
We're looking for someone to own the developer experience for Pubky's open source software system.
Pubky developers are clearly going to be an insatiable group, each wanting to leverage the superpowers that Pubky unlocks with tools like public-key domains and semantic social graphs.
We need great docs, great communications, great hackathons, and so much more.
Apply here: https://bitcoinerjobs.com/job/1410370-pubky-developer-advocate-synonym
My first thought: you are looking for a recruiter
Let your userbase vote on the items on the backlog what they would like to see finished first?
15 years ago I remember I was using the tool UserVoice for this kind of curation.
Any nostrich in the neighborhood of Freiburg coming week? 🇩🇪
https://cdn.azzamo.net/14703258acd6ebd3ee6f56fe3bbc92bcd7c60cd51529696bbe6acb36e1d7f55e.webp
They go into a black hole because Nostr is too small today and we're living with these public relays anyone can write. That situation cannot work if Nostr gets bigger, there will be too much spam. Many relays will be forced to close themselves only to users that meet a certain criteria (payment, relationship, content quality, PoW, etc), then once you have that it becomes in the interest of these relays to exclude people who aren't behaving well, therefore reporting them to the relays they use becomes a meaningful act.
https://pyramid.fiatjaf.com/ has a reports page where presumably I or other users can check if some bad actor got accidentally invite and remove them, for example (not that it has ever happened).
Anyway, the crucial part is that what can be bad behavior for me may not be for you, so my relay may only accept notes full of love and kindness, but yours may accept notes full of rage and sarcasm, and both are ok -- that brings us to the next step: if a user only wants to see love and kindness they should be able to configure their stuff to only see replies that come from my relay in some situations, for example.
How all of this works in practice I cannot say for sure, but I see zero centralization pressure in any of these steps.
So the ecosystem has to grow (adoption needs to go up) AND we need spam attacks to have the incentive to innovate away from those big public relays