I've recently migrated to this personal / single-user #Mastodon instance and finally got around to writing about that "journey”, explaining how and why I did it.

https://shellsharks.com/own-my-social

It is but one more way in which I am pushing further into adoption of #indieweb #ownyourweb #ownyourdata #ownyoursocial ideas.

Honestly, the hardest part about the move was emotionally leaving infosec.exchange, I explain why in the post (https://shellsharks.com/own-my-social#thanks-to-infosecexchange). Thanks for everything @jerry 🧡!

Owning My Own Social

A walkthrough of how and why I stood up my own personal Mastodon instance.

shellsharks
@shellsharks nice write up I’m in the same boat you are just a few months behind
@shellsharks @jerry Thanks for documenting this for future generations of retired Sysadmins who don't want to put up with someone else "in the cloud" mismanaging their stuff

@shellsharks
Hi! Question: Now almost 2 years later, how do you feel about having your 'own social'? I heavily considered it, and since your post, Wordpress has made it much easier to have your blog be an ActivityPub server(?).

But I had 2 concerns: discoverability (you had existing connections) and GDPR concerns (since your own server might contain people's replies, media and data).

How has your experience been?

@whywhatsnext I still love it and through managed hosting it’s been a breeze to manage. Discoverability has really not been an issue still, but yeah, I did come over with a good amount of connections already. As for GDPR, there’s some different issues depending on whether you’re hosting a server for multiple people versus a single-person instance. I guess it also depends how you’re hosting the instance. There’s some GDPR-related stuff I’ve linked to here if interested https://shellsharks.com/mastodon.
Stars, Boosts & Toots

Evolving thoughts, tips and resources for Mastodon.

shellsharks