Algo relays are neither inbox, not outbox. Amethyst doesn't have a place for them yet. They shouldn't be on any of your lists. They are designed for Custom Feeds in clients that you can set up a feed for just one relay, like Coracle
nostr:nevent1qqs024hed0snc0yj9usjamh02xr6m8ezt6azqq86apfjfv6akj8v72gpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36crqsqqqqqp333dv4
So like … what is an algo relay?
This is getting outa hand.
It's a relay that returns a custom feed based on the logged in user.
It seems to me that Amethyst needs a dual configuration option to accommodate the algorithm relay, and future relays of the same type. Maybe a toggle that presents either the algorithm configuration, or the standard configuration that we have now. This way you can keep the existing outbox model while also offering the option of utilizing the algorithm relays.
Or just a custom feed design so that users can add a single relay to the top nav list.
OK. So … how many possible WoT based services are there now? This honestly getting complicated…
Dozens or so... For now. I suspect we will easily see thousands of different implementations.
As an algo service provider … this will be challenging to keep up.
I can’t even imagine how hard it’s gonna be for end users to figure out.
It’ll get worse before it gets better.
Oddbean new post about login | logout