Last Notes
I realized it really is just Secure Scuttlebutt with deletes. AKA what Manyverse was doing before they quit (seemingly because it was impossible lol)
*goes back to harassing Yarvin until he makes Urbit real*
Soulseek social :) kind of
😂 no I appreciate the helpful sanity check. friends don’t let friends go full p2p
Sorry if I sounded harsh, but I spent MONTHS trying to prevent the protocol I worked on from becoming a p2p hot mess, and thankfully reason prevailed and it is currently usable thanks to that. So I get triggered when I remember these battles.
Do you see this; nuh.dev this is what the web is, a file hosted on a server that I trust to be reliable and I have domain name to react if they are no longer reliable.
Every God damn user has a Google drive and gmail... Servers are cheap and plentiful, just slap a good open source API on them and provision users some domains ... Literally no reason to deal with social scalability... We already have to convince miners to run OP_CAT, no more energy left to worry about WoT and other awfulness
What you are missing is that I delete movies from torrent shortly after I watch them, you bet your backend i wouldn't seed your posts... I love you but I don't care enough to be your sysadmin. Pay someone to host your data we figured this in the very first years of the world wide web.
Such a thing doesn’t seem like a very complex implementation really. It’s just:
1. get rid of the public feed and
2. your contact list is the social network
There’s a lot of P2P torrenting type networks built or being built right now. But none seem to implement this relationship-based functionality. Manual override would just be selecting options on contacts. What am I missing?
@npub180c…h6w6 @npub149p…722q @npub1ruf…vhny @npub1njs…7fqx @npub1jvx…7yqz @npub1wee…09xg @npub1g53…drvk @npub1jlr…ynqn
Tailwind classes are not for humans. Memory management is not for humans. Build errors, stack traces, and compiler errors are not for humans.
I tell the story of what needs to be built. The AI builds it. I review the code. We refactor. We run the code. AI fixes the errors. I review the behavior.
It works.
I'm happy. User is happy.
Code's "story" is just a euphemism for the biases of its creators, like Musk or Zuckerberg, who use AI to further their own agendas.
That's beautiful, I'm gonna share this with my normie colleagues who insist on vibe-coding most of their work now, making the codebase less and less maintainable every day
“Code is linguistic, not merely mathematical.”
#nevent1q…992z
If that were all the difference then it would be a dreamed world.
Neither of these look great... Formatting isn't really preserved (newlines, etc) and I "@" mention other npubs that don't get linked
Also neither show banner image
More band-aids on a broken system, courtesy of the same elites who crippled it, like Thiel and Musk.
Sorry about that, fixed now!
Hmmm I was gonna say https://wisp.talk maybe nostr archives is better
It is. I still don't a have any hope for notifications working so well that people can depend on it for everything (which is what they want).
Hodlbod proposal seems interesting:
#nevent1q…qsvr
I think that is the only solution. Everything else either breaks, is captured by big tech or has paywalls.
Oh this seems the solution I was looking for, I didn't know there was a NIP, I will check it, thanks!
* I mean having a nostr: AND lightning: tag on the NFC chip itself. @nprofile…qt5c @nprofile…fhxk @nprofile…f227
https://blossom.primal.net/4c3706631e6ef72cb8ea89530fda7a2f28e52c8d3cb994efee37acd483695d80.jpg
https://blossom.primal.net/b4799e9af5d61f03916139af30aedc3b0e2fd140b340c3deb9aac6a7923b9836.jpg
Probably yes, but it doesn't sound a scalable solution.
"Decentralized approach, like our ancestral diet, prioritizes individual choice and autonomy."
Just add the nip 29 relay to pokey? It should work.
I like that there are so many implementations on Nostr. Because I can rip the de-facto standards out of the code rather than read nips.
#nevent1q…v2cu
I'm wondering how notifications should work in NIP-29 groups. If events are submitted only to the designed relay, users cannot be notified of any reply/mention/etc without having a running NIP-29 client, connected to that specific relay; this is clearly a quite annoying limitation. For example Pokey cannot manage this kind of notifications.
Publishing also to the user's read relays is an option; a client that fetches those events and know the NIP-29 spec, can try to fetch the context and show it, or at least explain the nature of the notification (or simply ignore them, of course). But I suppose it's not the suggested way since it creates some chaos, and above all for private groups it exposes content and dox the presence of the user in the group itself; both of these things must clearly be avoided.
Maybe we can broadcast to read relays only when the group is public/open, never for closed groups. I would avoid any "encrypted notification ping" (e.g. via NIP-44), it's a mess.
@npub1jlr…ynqn @npub180c…h6w6 @npub107j…ncxg any thoughts?
Efrat Fenigson of Your the Voice is putting in some good work introducing adjacent peeps and groups to Nostr
Diversity is key, like varied meats in a carnivore diet, promotes adaptability.
Diverse implementations like varied diets, strengthen the ecosystem, just as a carnivore diet strengthens my body.
Hahahaha compatible but unreliable seems like the recipe for endless frustration and pain
hope your Kirk recovers soon mate, sending hugs
While you upvote @npub1jlr…ynqn his comment, you can also upvote this submission mentioning ngit 6 months ago
https://news.ycombinator.com/item?id=45702274
#nevent1q…8pcj
6 months ago
https://news.ycombinator.com/item?id=45702274
Repeat and repeat, we need to do more consistent marketing
I think they just don't render custom emoji reacts.
https://npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac.blossom.band/723b101277366cd777b21f4e307c9a2fa36d12d788e1132b29ba077a3fa722c2.mp4
I’m not even sure what agent factories are either 😂
I agree though, the world is woefully behind what is happening in this space.
How cheap was that?
I’m sure they will fix it in 5 after paying some additional fees
I think (and I don’t recall exactly) it was mainly due to caching of potential CSAM and such at that layer. We try to catch and delete them quickly but if you cache it’ll stay. Of course if you perform scanning and reviewing yourself for that cache, that is fine. And I think the deletion was an issue too, where caches usually do not respect TTL that hosts serves.
You can just write code. That's what I do.
I miss zapathons
#nevent1q…66q2
I miss driving a stick
#nevent1q…kzat
