5th rebase in a row and my patch has no conflict 🐧🐕🦺
Discussion
what changes are you making?
right now, just "disable updating relays with events they already have". pretty clean
to cut down on bandwidth? how does it know which events the relay already has?
amethyst tries to act like a nostr blastr on every relay its on. it appears to continually send delete events for events that are already deleted as part of this. so i disabled the entire blastr part (i think) so now its logs are clean from the perpetual retries it was doing
based! will Vitor merge in your changes?
he's seen it, but, it's a very simple deletion of the offending code, i don't know what a better fix might be
should this really depend on one person?
should every app fork for every possible change?
any open software you use, if you don't have a fork of it somewhere, not a good sign 😎
the question is, is it a useful fork
I'm still trying to fork Jumble... I hope I can come up with a custom feed algo that someone besides myself would want to use!
yeah. the hard question is not about using all these retarded open spam-ridden relays
the real question is, making it so that people can run relays that actually use auth.
i don't think many people realise that is a really hard problem because of all the other clients.
that don't respect auth. or care. or the replicators of data that just slam every relay with reqs to update. or the very idea that "hey, wait, do we actually want a fucking global?"
I think auth will catch on eventually. the problem is too many people are stuck in the mindset of paying to post, when it should be pay to read
i think it should be both.
what the actual is zaps about anyway? i mean, you know. that's money, right? amirite?
paid posts sounds a lot like advertising to me
paid to show?
i don't mean that. i mean pay to store it on a proverbial relay
yeah, that's the kind of paid I'm talking about. if the posts are high quality, they will be hosted for free, but people will pay to auth and read from the relays
quality is subjective, and can't be discovered until after it's seen
unless you put some limit on what can be STORED on a relay how do you evaluate what anyone wants to see, and then ... you know.. pay someone to store it?
i say, no. you have to charge to store it. first. other relays can decide to copy that data, it can be freely accessed from teh first relay, so, whatever. but i am vehemently against popularity being any kind of means of deciding the cost of storage.
why? because storage has a fucking cost.
you make popularity a premium that means no price to post?
then you, normal, unpopular person, are shit outta luck, i mean what the fuck. come on, this is not ok
also, i want to vomit in the general direction of anyone who thinks that popular content should be free.
no content should be free. but at the same time, you can't control who copies it.
so, yeah, if you want to copy what other people post, fine. but if you think that you can run relays at zero cost. what the fuck is wrong with you?
just fucking go back to free facebook you fucking retard
mossad and cia will love you