@icedquinn@ringo i saw what you were going for, but sometimes, i wonder what would happen if you just had the computing power to run a neural network in real time to generate the output directly. might produce some fairly wild sounds.
@ChefsCatch@ned i live in a country that is probably as close as you can get to a "social-capitalist democracy"
the foundation is personal liberty and trade. on top of it, there are socialist elements.
it's not terrible but it's not great either. in some respect, i think the European/Nordic model holds us back a little. but it also prevents us from falling into the abyss. it's very much a compromise.
now i'm thinking about problems they had when trying to run worker's collectives in the early days of the Soviet Union.
what they discovered is that factory workers were keen to participate in top-level meetings at first, but they started getting bored with them, and eventually, only a small group would show up for the meetings.
those people became the management.
basically, a company structure emerged organically, despite best efforts to eliminate the hierarchy.
@alex okay, so that's an implementation detail. your usual HTTP client will return the redirected result i think, so it's effectively like having two addresses output the same thing. i said "it wouldn't hurt" but that was a figure of speech.
@alex relay.mostr.pub should probably return a NIP-02 contact list event (kind 3) that returns who users follow and lists wss://relay.mostr.pub as a relay.
mostr.pub doesn't appear to return anything when queried like:
{ "kinds": [3], "authors": [pubkey] }
this would also explain why mostr.pub users are listed as not following anybody in most clients.
i'm writing a tool that looks at your follows/followers and lists the top relays they use, and naturally, relay.mostr.pub is going to be missing from that list since it uses NIP-02 records.