• he him

night of the living bathroom

art tag is #dedusdraws


atomicthumbs
@atomicthumbs

the most brain-poisonous part of modern social media is that it's ridiculously difficult for posts to be popular without being "viral." a couple generations of sites down the line and maybe we'll be back to a network of blogs, connected but not woven together so tightly it's stressful and drives us all mad


atomicthumbs
@atomicthumbs

you could make a communications system like this. postsocial media. just do it as simply as possible: a single client/server for each user. a centralized directory. a user can serve any number of pages, and subscribing is done manually.

serve feeds like you would if you just hosted a blog yourself, but with authentication done by the directory. actions like faves and comments are done by one user making an API request to another user's instance of the software. have the directory introduce people instances to each other; authenticated interactions between users can be done with public key cryptography after that.

and make it so users can't share posts. you can only subscribe to others, like an RSS feed or gallery site. you can link to people or posts but any spreading of ideas has to be done manually and with intention.

for posting, imagine something like a cross between cohost and a static site generator. WYSIWYG, with a theme directory and user-editable templates, infinite presentation customizability, within one's own blog and posts.

a perfect place for small networks of friends to keep up with each other. lightweight, easy to host. not so wracked by convulsions of discourse or baseless callouts, and not dependent upon a centralized authority to maintain your connection; if the directory went down, you could still see your friends' blogs and keep in touch. build user instances to operate in a degraded but functional mode with no directory present, for independent/private clusters or network survival.

some of Mastodon, some of Cohost, some of the old ways.

call it Campfire. a thing you can build yourself to sit around, finding comfort with friends. a refuge from the cold, dark night.


You must log in to comment.

in reply to @atomicthumbs's post:

in reply to @atomicthumbs's post:

The problem is always finding the network of friends one wants. All of this stuff serves chiefly as a form of introduction between users, either implicitly (if you like one of my posts that your friend reposted maybe we should also be friends) or explicitly, as fuel for an algorithm of some sort. The places that eschew sharing and virality only really work for those with an established community.

Maybe, somehow, you could put that stuff in a sort of Virality Thunderdome people could enter and leave at will. That might allow people to enjoy the energy of discourse and find their community without having it constantly torn away by that same restless tide.

any amount of frictionless post sharing means one becomes part of the medium, moved with the tides. as soon as there is a single button to expose someone else's post to all followers who opt into such things, the negative impacts of modern social media are present.

this would be different.

actually some technical thoughts because i do want to have a go at building this (pretty much as-described) now that i've thought about it a bit more

  • multi-user instances? presumably not everyone i want to talk to is a hobby sysadmin who owns a vps / domain / public ipv4 / etc
  • is a directory necessary? if it's just for authentication and key exchange those can be done without centralization

ok i did some research on what you need to do for reliable peer to peer in current year and wow i really do not want to write / adapt a RFC 8445 library right now

unfortunately that's needed to satisfy both "self-hostable with no technical knowledge" (necessary for one user one instance) and "directory server only needs to transmit peering information" (necessary for running the directory server not being ass expensive). and i don't think any NAT traversal approach here works in the total absence of a signaling server so that's not a good sign for reliability either

as i understand it bittorrent deals with this problem by letting the directory server actually be "everyone in the swarm who has a public ipv4 / port forward" so it's possible a similar approach is viable here. i'll have to think about it though

(and no tim berners-lee's new thing doesn't do any better)

I've had an idea like this for years, but more simplified. No central server, just everyone runs their own one-person "instance", but your own blog generates a feed, that other people can follow, and you can follow others, and you'd thus have a timeline view more or less like Twitter or Cohost do.

Replies/shares/etc. go over the feed, which naturally results in interactions only working between mutuals. So you can reply to a post, but the poster would only see it if they're also following you, because otherwise their feed would never pick it up.

I suppose the weakness there is that other people following you can still see interactions you make with other blogs regardless, but I think the impact would still be significantly minimized without losing the discoverability effects David mentioned.

Part of the reason I never got around to doing it besides "I don't do serious coding for free" though is ... this is just how the old blogosphere worked. People did all this stuff organically over RSS, there just wasn't always explicit UX built around it (some blog services even did have things like following or reply tracking). Remember the huge controversy over linking/quoting other sites? It's all been done, it's just making a blog.