Fuck it, you made me laugh.

My point remains though, they can do whatever the fuck they want as long as they have the balls to disclose what they’re doing so people can make informed decisions.

So I can publish an App to the AppStore and deceive users and that’s ok because the lie can be uncovered by poking around the source code on GitHub or whatever? Are you serious?

Dude I’m not saying that Primal shouldn’t have their stupid blacklist, my point is that they only needed to disclose their client has said list. This is not about how nostr works or doesn’t.

I like that links open in app on Primal, because my aging iPhone 13 is unable to juggle two apps simultaneously so it almost always kills whatever app I was in when it switches to Safari, and that’s very annoying and Apple’s fault but in app browser is a nice workaround.

This is downplaying a questionable practice. Primal doesn’t make it clear anywhere it does arbitrary shadowbanning and that’s not immediately obvious from just using the client to prompt the user to switch clients.
Again a simple toggle on settings or disclaimer text would be enough to prevent the heat. They didn’t.

Just imagine if every client had their own forced filtering.
This is a slippery slope and you have Mastodon at the end of that road.

I have no problem subscribing to a crowd sourced blacklist to hide a certain kind of content.
I have every problem with the developer of an app making this choice for me in the shadows.
Primal could’ve avoided at least half of the heat if they had some option to opt-out of their, uh, “curation”.

Would you say it’s capable of lifting someone from a debilitating depression hellhole? Asking for a friend…

Centralization is not as efficient as you might think, even Google pushes competing products (there was a point in time where you could download 5 or so different, Google owned, chat apps in Android).

Perhaps 10 5-man teams would be a better bet.

It’s not about software maintenance, it’s about reliability. He has a good point, actually, but I don’t it’s possible to fix the bootstrap problem while bending over to ICANN.

I can see this getting fixed very easily by adding service discovery annotations into the metadata of meshnet nodes (think FIPS/Yggdrasil/CJDNS) since, worst case scenario, a naive solution could be that you just walk the whole network inquiring each node if it hosts nostr or not.

State machines are amazing, I still remember the first time I used one in Erlang. Good times.

Se dar o cu diminui o QI… quem come o cu aumenta o QI?