The closest I can think of to a service that you can rely on to be around for that long would be the cloud storage ones, like Microsoft OneDrive, Google Drive, etc
Can you confidently say that about any image host?
Oh the tag is invalid? How so
Ah I think it may be because I added this repo:
Interestingly, the tagging works when viewing the post on Iris and Amethyst, but not when viewing it from Damus or Snort.
Awesome to see that Nozzle, Amethyst, and Nostros are all in the F-Droid app store now
Or maybe go the absolutist route and have no global feed at all. Just who you follow, and you can discover new accounts from reposts of your current follows.
Well it can be designed so that only users you don’t follow show up in the “top posts” of discover, so that it helps give a chance to accounts that aren’t followed by a ton of people already. Good point!
Hot and bothered?
Right, the idea is that posts will still get likes from the people already following them, and so this discover tab would let you see liked posts that you otherwise wouldn’t, because you don’t follow that person.
Awesome! Nostrum.pro has a good example of this “top posts of the day” concept here: https://nostrum.pro/search/#threads:1d
Even without the spam/porn, a firehose global feed is just too much meyhem to be useful. In my opinion, the best default setup is:
1. A view for just posts from your follows
2. A view for posts + replies from your follows
3. A “discover” view that shows you the most liked posts of the day, or something to that effect
TLDR: The best way for the user-facing part of the client to avoid spam is to only show posts from your follows and a leaderboard for global.
Incredible map of Medieval trade networks in the 11th and 12th century
Full background and source: https://imgur.com/MsXaOdV
I’m still experimenting. There are lots of ok ways to try do this, however few will consistently hit 95% plus - without adding 20+ relays (or more in future).
I’m currently streaming events from 80+ relays, so I can tag which events have been seen by which relays (without actively asking at present).
The current approach is to lookup who a pubkey follows, then get the most recent N events by them, and then process against which relays would be needed to get coverage across the following event set.
It’s got some recursion, so processing speed or pre-processing are considerations vs good enough.
My other approach is to multiplex and perhaps dynamically do this for clients. https://nostrgraph.net/relay
I’ll share updates on Nostr. It’s a little hard to publish a working algorithm since it’s data dependent.
Awesome, looking forward to seeing how this goes
If this is on iOS Safari, i found that turning off content blockers fixes it.
Interesting idea…i’ll tinker with that later today and see what I can come up with
Could there perhaps be a way to batch these events so it only sends a certain number of rss feeds updates per interval?