What is Nostr?
a /
npub1jak…5a7c
2025-01-09 18:56:14
in reply to nevent1q…trd0

a on Nostr: feld nprofile1q…f9aux Sun i think there was a rule where the bot would only boost ...

feld (nprofile…xyvy) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqwn8c84fe6hs6uav7n5vd6w0fuz4qtzqdt8cfksdr6t6r39rga2nqxf9aux (nprofile…9aux) Sun (nprofile…h6f2) i think there was a rule where the bot would only boost stuff from people following it, and you could manually accept follows as a proxy for approving member requests. but this meant you couldn’t just follow the bot without “joining” the implicit group

then lemmy took this idea and made it way more complicated for little to no benefit, while at the same time claiming their way was the One True Way to do groups (to the point that they have trouble handling guppe groups or any other Group that doesnt do their wack Announce Create Page stuff)

i’d like to think that maybe something better could come out of the groups task force that recently spun up but i don’t particularly have much faith bc even if a decent spec is written up, the implementers will ignore it or do it wrong

there’s just no baseline to this shitpile, you can’t even reliably get a plain text message from A to B without reverse engineering the hidden requirements B has placed on all incoming messages. ive been awake for 4 hours and already seen two separate cases of people complaining “why did my dm not show up when i tested federation between x and y” which is a hell of a thing when this spec has been out for 7 years. and this is assuming you manage to clear the http signature cavage draft hurdle beforehand

idk what to really make of it but with respect to the broadcast use case it should not be this complicated

the one counter argument imo is that maybe fedi is for people and not for broadcast stuff. but then that means there should be something else for broadcast stuff (like rss/atom/whatever)
Author Public Key
npub1jaklnjpdrr4gl53nnama5fzm82lr637pum2ry2m6mqgrd5thxglqqc5a7c