Hey, does anyone remember the hosting provider MaaStodon?

They seem to be called Fedi Monster nowadays, but vaguely remember they used to be around under old name for a long while?

Do people have any thoughts about them?

@dachary @rysiek @bob @gna

It depends how you approach email.

If you have your own domain, it's possible to change providers without your contacts having to change their address books.

But even having the option to change providers with an address change is still really good. There is no such option on Facebook or Twitter, where users are stuck on the same provider forever and have no way of leaving.

People used to change phone numbers all the time, and it was a pain but it worked.

Hi @Oytis , my experience is that most federated projects, especially social ones, were built with the mission of taking control of your information so normally they take privacy concerns very seriously. It could be said they're GDPR compliant by default. If they're not, an issue can be raised on their respective issue trackers and services can be taken online if they're not satisfactory.

If you're planning to provide a service, research the project before committing and find out how other service providers deal with GDPR. Every project deals differently with data so there's no one-size-fits-all solution, some legwork is reguired.
If you plan on self-hosting just for yourself, there's much less work required. You are your own data holder, you can do as you see fit unless you keep someone else's data.

A service hoster can take several steps to be fully compliant. There are some basic rules based on some experience I had over the years:

1) There's a distinction between essential and non-essential information. Error logs can be kept if they provide a useful service and aren't shared with anyone but yourself. Access logs are normally optional unless you care very much for continuous optimization.
Keeping non-essencial logs (i.e. track user's activity) can provide benefits for your service, but ensure you at least know how to delete them on request. I normally don't save apache/nginx access logs since they're not worth the effort.

2) Search for cookie information for a specific project, either by compiling a list of cookies by hand using browser extensions and following the pipeline from registration to first activity, or asking the developers on their main issue tracker for any essential and non-essential cookies, as well as their purpose. If developers can't answer it, jump ship. If there are non-essential cookies that can't be disabled, my main advice is to set up a cookie consent popup. There are some popup generators on the web, you can google them if you wish

3) Try to find out how user's data can be deleted, mainly if the user can delete their account in their preferences or if you can do it for them. They are not required by law to log in to delete their account.

4) Have a privacy policy link clearly visible in every page. A Privacy Policy should have at minimum the identification of the data holder (not real-life information, mind you) and a point of contact, normally an email, where someone can reach you to ask for their information to be deleted. A list of every essential and non-essential cookie would be great. Cookie consent popups are good but you can't fully rely on them

5) The law is usually lenient with best-effort cases, at least in Europe, but country laws might apply. You should not be worried if you do what you can to protect your user's data and ensure they always have a simple way to confirm who owns their their data, where it goes and how to request its deletion. You normally have some days to implement changes whenever you receive a GDPR notification.

6) Find the country your server is set up on and find a lawyer who specializes in data protection beforehand. You don't need to initiate contact but it's always good to know where to go if trolls try to sue you

Hope I helped clear some doubts and didn't bore you midway. I'm not a lawyer but I've handled some cases and had training regarding data protection.


I haven't tried these properly, all I can suggest is giving each a go and seeing if it fits your needs.

They should be compatible with similar hardware.

They are all under development so there's reasons to keep an eye on all three.

@futureisfoss @nextcloud

I get the impression it's a "work in progress"? You can set particular folders which are e2ee, so it's like an optional extra for file sharing.

This messaging service doesn't have e2ee.

@futureisfoss @nextcloud

I think the only e2ee on Nextcloud at the moment is for specific file folders?

@kaip @nextcloud

No, it's not XMPP.

There is an XMPP add-on for NextCloud, but it has no connection to the NextCloud Talk add-on.

It would be nice if Talk used XMPP but unfortunately it doesn't. 😔

You can also use @nextcloud to set up your own private messaging service:


The service has its own dedicated mobile app for Android and iOS too.

Major downside is it doesn't have any kind of federation (yet), so you can only talk to other people on your server.

If this sounds like something you'd want (for example an internal chat system for your friends, family or organisation), it might be worth looking at this.

@rysiek @maikek

Ah yeah that's a good point, keeping the blocks up to date is a pain too. Yes.

Nothing wrong with it as an idea! Themed instances are very common, having an instance themed around small orgs makes sense.

@rysiek @maikek

Is it that much extra work, if they use a managed hosting service?

It would be a drain on resources of about 6 euros a month though, that might be biggest barrier?

In case you missed it, you can create your own personal music and podcast streaming service through @nextcloud as detailed in this article:


It works with files on your server and podcast RSS feeds, with good mobile app support.

There are some limitations which I've gone through in the article, but overall growing your own alternative to Spotify is really fun! 🎧 🌱

@roq @feditips

Do you mean doing the techy stuff yourself instead of using a managed hosting service?

I've tried to skip those topics as there are already other sites doing that. (No one was covering managed hosting, that's why I started GYOS.)

The Related section on GYOS might be a good starting point? There are a number of projects trying to make it easier to install and maintain stuff yourself without using managed hosting:


@ScottMGS @logicalwillow

Yeah, you don't need to be techy if you use a managed hosting service, because it does the techy stuff for you. More info on the website at growyourown.services


That's a real shame about Beaker, I was wondering if it would become something more accessible to non-techies :(

What do you think about Manyverse? It says "no blockchain" on the website, but I've seen some claim Scuttlebutt does run on blockchain?

GYOS is aimed at non-technical people, so it focuses on managed hosting.

If you're slightly techy though, I'd highly recommend these projects. They let you add services to your VPS or home server through simple graphical interfaces:

Yunohost at @yunohost, more info at yunohost.org

Libreserver run by @bob, more info at libreserver.org

FreedomBox at @freedomboxfndn, more info at freedombox.org

Show thread

Lots of new people, nice to see you 🥳

If you haven't already, please check out the website at growyourown.services

The idea is to help people who aren't technical create their own online services through managed hosting, where the hosting company does the techy stuff behind the scenes.

Some particular highlights include a beginner's guide to starting your own Mastodon server:


...and starting your own Nextcloud server:


@gidi @leonidas

Yeah, there's no Friendica managed host as far as I know?

If you find one, please do let me know so I can include it on the website 👍

Show older

Single-user Mastodon instance for the Grow Your Own Services site