Are you calling the server list on joinmastodon.org "the federation"? Because it's not; it's literally just a list. Nothing about the list tells you about any actual federation between instances. Without a doubt there are instances on that list that are federated with ones not on that list and vice versa. It's not even the only list out there.
This would be a good thing, though I think it's trickier than it appears:
Lots of comments already telling you to stay home so I don't think I need to. What I will say is if you don't want to contribute to the growing number of variants, you'll stay home. Variants largely arise from mutations in the virus during replication. Humans are virus-replication machines. If you're infected you could be carrying a new variant right now and the only way to stop it is to let it die inside you. Your body's immune system will already be in full swing and be in the best position to deal with it as opposed to an uninfected person.
Don't contribute to the endemicity of COVID.
There's nothing wrong with being right all the time, but relationships need more than just the exchange of facts. If all people know you for is the guy who is right all the time (or needs to be right all the time), then maybe you're neglecting the other aspects of those relationships. There needs to be other things people remember you for.
This is good for Linux users. Valve has been fantastic for supporting games on Linux since the Steam Deck and Blizz has never had proper Linux support. Now Linux users can ditch Lutris, Bottles, or WINE if they want to just simplify and use Steam, which does have a native Linux build.
From my understanding, the game is about killing each other lol
Yea, this will always be the problem when trying to create a story around this format of gameplay. You definitely have to ignore the fact that lore enemies can team up because the comp needs it.
The optimistic tone comes across in the character writing, world design, and music. Little in the game is dour or depressing. Instead the focus is on the details that make the locations or characters unique and interesting. There's a lot of language and cultural representation.
Also, barring the secondary deathmatch game made, OW is technically about doing non-kill objectives, it just so happens that killing your opponents is the best way to complete the objectives.
It's funny because on the scoreboard, traditional "Kills" are labelled "Eliminations", but they still keep tradition for multikills i.e. the announcer will say double kill and not something double elim
Kbin does that in terms of function as in kbin has its own microblogging element to the experience, but it doesn't do anything to bring the existing kbin and mastodon universes together.
Mastodon can do this. Mastodon interprets Lemmy communities as users, Lemmy threads as boosted posts with user mentions, and Lemmy comments as replies. If you search on Mastodon for a Lemmy community using the Mastodon format e.g. @community@domain instead of !community@domain you'll find the community and posts.
Isn't this a strange article title? The whole point of it is to show T cells don't actually get "burned out" at all. And imo it's not like the real reason is uninteresting.
Why dress the article in the exact thing it's refuting?
I'm not agreeing with the above, but it's nuanced. Content curation is a sliding scale that can create an echo chamber if one becomes too insular. On the internet especially where discourse can be inflammatory, avoiding some topics can shut you off from entire ideas that may otherwise be benign.
IMO create the experience you want, but build resilience and test your limits often. It's healthier for yourself and the internet as a community.
The sign-in experience is where you're going to get a lot of friction. Your users are going to need your server address. They'll have to log in to devices with username/password including TVs unless they have signed in once already somewhere else on the network like a desktop. Then you can set up an Easy PIN code or use Quick Connect, but those are hidden behind the user settings menu.
This is extremely valuable, thanks for this!
As a general question, why did you decide to use a single postgres container for multiple services instead of multiple, stack specific containers? When I first started working with containers I considered your scheme for the sake of minimalism, but didn't want a single container to bring down multiple unrelated services. I also had the resources to accomodate the redundancy.
Who made this comic?