Since I guess everything is political these days, I’ll identify as extremely liberal but without a home in US politics.
Mainly, there’s so much misinformation out there that people in society have trouble even organizing into coherent political groupings. So I’d rather not talk about politics but instead focus on information and education. Nothing else matters until the bedrock of fact is buttressed.
But… people are always going to be wrong on the internet, as the saying goes.
So: Old man yells at clouds is a famous joke from The Simpsons, and it probably fairly describes what we do when venting on social media.
Just speaking into the void, since I figure it’s an exercise in futility to conduct discussions on these platforms.
Yes! I often thought some of the lesser known songs on Some Nights had a distinctive Queen-for-a-new-generation vibe to them.
I’ve heard (but not confirmed) that some lemmy domains are having issues with firewalls blocking them, maybe as DDOS avoidance features, so your instance is unable to reach out and see if the user exists.
I’ve heard that from multiple people and forum posts at this point.
Think of Lemmy as being just a different Mastodon client that happens to display things to their users with a different skin.
You interact with content on a Lemmy instance the same way as you interact with content on a different Mastodon instance.
(Technically they’re both ActivityPub clients, for the more correct terminology)
There do seem to be some kinks to iron out between the clients, though. The ! thing might be one where they disagree on how to handle it.
Result: interesting, my reply from a Mastodon instance showed up, but on the web interface I don’t see my username.
Maybe a little rough edge to look into.
@ValueSubtracted
If you’re interested in a little more behind the scenes info on how this works, (and since I want to make a test post to see how it shows up in Lemmy):
Since there’s no central clearinghouse for content in the distributed Fediverse, each instance broadcasts its users’ new posts, but only to other instances that need to see that content, generally because they host at least one user interested in it.
So you’ll see times when your instance won’t have received any older content before its first user followed the remote account. After that, the remote instance knows to start sending content to your instance, to that user really, but then your instance knows about the content.
In other words, your instance begins its subscription to the remote account by having any user begin to follow it.