Every news outlet should stand up a Mastondon instance for their reporters & staff.

It’ll be great to see [email protected] or whatever domain they want to use.

Built in verification. Every reporter for the Washington Post on a washpo domain. Every reporter for the New York Times on an NYTimes domain. Etc, etc.

Plus the “local” feed for each instance becomes a feed of all the posts from that institution mixed together — providing extra discovery.

@jensimmons one thousand percent! and account migration easily solves the whole "what about if/when they get a different job?" predicament.
@jake @jensimmons I like this, though I am a little worried that (1) a company wouldn't allow your redirect if they fire you (2) what if they contract to multiple places and/or want to pitch their substack from their "official" account?

@Jakeout @jake @jensimmons reputable places won't do that.

There are issues with a federated system that will be hiccups, compared with a seamless single silo, no argument there.

But it really is a pretty well thought out system I think. Built in flexibility on many fronts.

And as for accounts, people had multiple Twitter accounts, no different here

@pixelpusher220 @Jakeout @jake @jensimmons hm, twitter was somewhat reputable and now, not. Perhaps normalize posting on multiple instances at once?
@chipchirp @pixelpusher220 it'd be nice if the user journey of mastodon had some built in affordances for this, follow an account whose identity is "administered" by another account, potentially off-instance. This would enable backups for if an instance went away, too
@Jakeout @chipchirp @pixelpusher220 You may be interested in the new project Dorsey is pushing, bluesky. It seems to focus very much on account portability and permanence. Still on the drawing board though.

@piccolbo @Jakeout @chipchirp

Another private silo isn't the correct answer.

Federated, distributed is the solution. Literally what email is, but for social media

@piccolbo @chipchirp @pixelpusher220 @Jakeout Why not both, like email?
@bossandnova @piccolbo @chipchirp @Jakeout you can't be both federated/distributed and a private silo.

@chipchirp @bossandnova @piccolbo @Jakeout a blog is a website which is federated and distributed via the public/open HTTP protocol.

Whether you make your own website public or private is a separate consideration to my thinking.

@pixelpusher220 @bossandnova @piccolbo @Jakeout ok i think I understand, i am having a dopey start to my day and I suppose the gist of what id like to see is a variety of redundant archival systems available to users that should be no more sophisticated to the user than repeating what was shared and saving it away on a site they own or an account on another service. I dont want a little insance tyrant with all the hubris of the HOA busybody ruining accounts and causing people to lose stuff they posted ij the past, (or worse, an insecure dork who thinks drip means carrying a sink around, and that free speech is about suspending anyone who says boo about him)

Bah im almost out of coffee creamer, today is feeling like a half day….

@chipchirp @pixelpusher220 @bossandnova @piccolbo @Jakeout This is why I started using an app that takes text and markdown input and then pushes it out to whatever services I designate, including my own local archive. It doesn't handle comment threads, but it saves me a record of any content that originates with me.
@piccolbo @chipchirp @pixelpusher220 @bossandnova @Jakeout Drafts, which is only available for Apple operating systems. I am unsure if there is an Android equivalent.
@knottedthreads
I see and then you have an integration with a Mastodon app?
@piccolbo Not an app, but just via the web. Drafts works via "actions" that work through service APIs. For Mastodon, one specifies the instance URL and one's username in the script, and then the first time one mounts the action, it authorizes in the same way that any Mastodon app authorizes. Drafts then stores the given credentials and sends content to the same account whenever the action is run.