Email or username:

Password:

Forgot your password?
Top-level
L. Rhodes

That maybe seems a little complicated from a UX perspective, but I think it could be made relatively seamless. There could be a standard post form, and the service/subdomain you're using changes depending on what options you invoke. Clicking "add image," for example, switches you over to photo.foo.bar. But the option to add image only shows up on your form if you connected to the photo service. Which would be a relatively straightfoward toggle in your account settings — if foo.bar offers photo.

3 comments
L. Rhodes

What's the appeal? For one thing, you'd be able to connect to all of these services from the same account, rather than setting up accounts on multiple instances running different services, or compromising on an instance that kiiinda does most of what you want.

But it would also let followers pick and choose which streams they want in their timelines. Maybe they want to read your thoughts, but don't need to see your checkins. Maybe they just want to see the links you post. Or the photos.

L. Rhodes

The most interesting way to go about it, I think, would be to prioritize breaking forms of interaction down to very basic forms. Most social media services are highly hybridized — post text, photos, videos, polls, checkins, etc., all in one place! Since this would be a modular server structure, the services don't have to be hybridized. Each could focus on being really singularly good at letting people do the one thing the service is most about.

L. Rhodes

Anyway, the idea is out there now, and I'm utterly incapable of actually making it, so if anyone wants to run with the idea, you have my blessing, no Nazis, no TERFs. Banyan would be an apt name for it. Or maybe Kludge.

Go Up