And I think letting everyone decide for themselves how they run their instances and who they federate with is an important cornerstone of the fediverse. I’m more than fine with people not wanting to interact with threads. But what happens on my tiny instance with me as the only active user shouldn’t be cause for outrage.
I’ve once been downvoted to oblivion for not defederating threads.net before it even went online. Fediverse people are weird.
Just a regular Mastodon server with federation disabled might be a good start.
I don’t think so. French “tiens” is a form of the verb “tenir” (“hold”). German “tja” is pronounced almost exactly the same and is only used as an interjection with a similar meaning but doesn’t have any related forms that I could think of.
Especially the southern German dialects have quite a few words that originated as loan words from French so it’s at least plausible. Could of course just be a coincidence as well. Languages are full of those.
And this is the moment I realized that German “tja” (“well”) probably comes from French “tiens” even though I’ve had five years of French in school.
I really hope they’ll streamline that a bit more or at least create some documentation that’s more than a hand full of bullet points.
Please rewrite this or at least add a tl;dr and change the thread title to something more descriptive. I’m sure you have a great idea somewhere in there but I’ve had to stop reading after a couple of paragraphs that just sounded preachy and got nowhere.
Then please update your category name to reflect that. Right now it says “Self-Hosting” which to the majority of readers means hosting it yourself, whatever the reason may be: privacy, configurability or just being safe from future enshittification.
As far as I know most Lemmy instances leverages paid-for or freemium services to have their instances work easily/properly
Yes but you can’t compare a whole lemmy instance to an account on an email server that you share with others. The fair comparison would be hosting a lemmy instance to hosting your own email server and creating an account on Proton Mail to creating an account (or a community) on lemmy.world.
This looks at how technically easy it is to run your own backend (e.g., email server, Mastodon server)
Edit: also the description text “This looks at how technically easy it is to run your own backend (e.g., email server, Mastodon server)”. Relying on Proton Mail or similar free services is not running your own backend.
Here I’m a bit in two minds, sure it’s difficult to SELF host email, but in practice it isn’t because there are hundreds (Thousands?) of hosting options to choose from where you can choose your own domain etc. for the low price of basically-free
I would prefer to limit this to actually hosting it on a machine you control. We don’t consider redirecting a custom domain to a subreddit “self-hosting”, do we? Yes, there are many email providers out there but that’s more like existing lemmy or mastodon instances and not like hosting your own where you have full control over your data.
Why are we using a random repo created a few hours ago by a random github user as a reference ?
They aren’t. That’s the repo that has the latest version of the survey. The actual references are one section up.
Having set up a couple of mail servers myself, I wouldn’t call it easy. Most solutions boil down to a tangled web of dovecot, postfix, ldap and amavis. There are preconfigured docker containers which make setup easier than a couple of years ago but if your use case is even just slightly different than the maintainers’, you’ll have to dive deep into a few dozen different config files. And of course, you’ll have to find out how to configure SPF, DKIM and DMARC to have even a remote chance of your mails getting through to the big providers. I’d probably give email somewhere in the range of 8-12 points in that category.
Other than that, great summary!
Oh, thanks for the heads up, I didn’t notice.
After playing around for a bit, this really looks like the best option. I will wait until federation support gets added to the self-hosted version though.
That doesn’t sound like a federated wiki but more like federated account management.
Doesn’t seem to be in the latest open source release or at least I can’t find how to enable it.
Edit: according to https://activitypub.ghost.org/social-web-beta/, it’s indeed only in pro for now.
That’s the reason why I like C#, ASP.Net Core and EF Core so much. A simple CRUD app can be written in under 10 minutes and easily deployed in any form from a self-contained binary to a docker container to whatever eldritch horror lurks behind Azure or k8s. Personally, I run docker swarm mode for my stuff because it makes automated deployment super easy, kind of like a leaner k8s but if I wanted, I could just drop a binary on any windows, linux or macOS machine without needing to install any major dependency apart from my database.
Edit: of course, ASP.Net Core has its downsides too. Especially when it comes to auth stuff. I wish I could have something as simple as devise + cancancan in old versions of Rails.
It’s “all” in the sense that it’s everything the instance knows about, in contrast to “this server” which is only content from users that are registered on this specific instance. Same concept as the “all” and “local” feeds on lemmy. I agree that a better name might reduce the confusion but I can’t think of a good one.
Servers not having the same content in their “all” feeds is not a bug, it’s by design. The design philosophy for Mastodon (and I’d say the fediverse as a whole) is to let the users curate their own feeds instead of showing them everything or algorithmically guessing what they might be interested in. Servers will only receive posts from accounts that at least one of this server’s accounts is subscribed to. Having every post federate to every server even if nobody there is interested in those posts would be a waste of resources.
Yes, that makes discovery of new content significantly harder but that’s the tradeoff for being able to host your own small instance without the need for a super powerful server. I can run my instance that serves just a couple of users on a 10-year-old server that runs a dozen other things at the same time. We see the stuff we’re interested in and don’t have to spend disk space, processing power and network bandwidth on content none of us will ever read and neither do we have to spend those resources on sending our posts to other instances where nobody will read them.
タイッツー is definitely taittsuu. Twitter doesn’t seem to use a katakana spelling. Your proposal of “tsuittaa” would be ツイッター. Same katakana but different order. There would be no reason to read Japanese from right to left. Might be an intentional pun though.
Edit: it’s https://taittsuu.com
It may still be missing stuff from before the first person from your home instance joined the community which can make younger communities feel empty.