Avatar
monlovesmango
8c0da4862130283ff9e67d889df264177a508974e2feb96de139804ea66d6168
building on nostr

yes, it is. but global feed in its current form wont survive when we have user volume, would need to be curated somehow.

yeah, just reply to original post. for simple text posts I think just display the last edit and have an indicator that it has been edited. and then allow people to review original version.

hmm also looks like this has many "reply" events but no "root" event. but prob cus its supposed to be a reaction kind..?

or intention. def think its plausible that twitter was ok with some accounts getting targeted by spam bots.

wow didn't think of that. need to step up my adversarial thinking...

yep, pretty straightforward. connection details will be from NIP05 (since thats already stored on the nostr network) so you would have to host from your NIP05 domain.

for sure, they are just getting started. even my sister gasped at this when I showed it to her, and she doesnt follow political stuff.

also, how much you wanna bet they are collecting a list of people who closed their account over this? imo odds are high.

i'm building a self hosted server that will integrate with nostr to make posting images/videos streamlined rn. but well see how well it actually works in practice.

and I doubt us gov will allow USDT to be globally useful for much longer

serioiusly. most especially after the fact check gaslighting.

congratulations #[0] !!! can't believe how much you are able to accomplish, its truely insane. keep up the great work!

yeah this is what I think I will do as well.

for posting, i think i'll have a short form and a long form mode. long form will not display the post in full, you'll have to click to see the full thing. something like that.

imo in the future all nostr client will need to opt in to POW, which will make it more feasible for users to only use POW only relays.

spammers that post via non-POW clients will then get no visibility, and remove the incentive of spamming.

yes for sure. or even a separate feed or something. the main reason I lean towards relay filtering of POW rather than client filtering is that the client can't send requests for only POW events, it has to receive all events and then superficially filter for POW