Thanks for the tip; seems to have worked. 👍
We can celebrate if and when they're actually reinstated and the people who put them out of a job are put out of a job themselves.
Also, one of the ones I wasn't going to block seems to also be instance-banned: [email protected]. Is there a reason for its (presumed) banning?
Thanks again for your dedication! 👍
Also, while I was going to make a separate post about what the comment in the example GIF discussed, might be just as worth asking here.
While most unblockable communities were removed from the Lemmy Explorer list when blocked instance filtering was added, a few from unblocked instances remained on the list. After inquiring at [email protected], it seems that these few communities are blocked at the instance level. Is there any means by which communities blocked by a user's home instance could be detected and filtered out of the Lemmy Explorer list?
Blocked it 👍
Two other communities on the list, one from feddit.rocks and one from lemm.ee, seem to be on the list too given that they're also unblockable, and should probably stay that way given that unlike the thunder one, they seem to target specific Lemmy users.
I guess I'll ask the Arctic developer if there's a way to detect instance-blocked communities to filter those two communities from my list as well.
Arctic (iOS and MacOS only, unfortunately) has built-in swipe actions for blocking and unblocking at the community and instance levels.
In addition to the standard federated community list, it also has a separate Lemmy community list that instead pulls its data from Lemmy Explorer. Since this instance doesn't use Lemmy Federate, it's both a useful means of finding communities that aren't federated to this one yet, and also a useful means of blocking any uninteresting or otherwise unwanted ones. You can then have it filter out communities you've blocked, to avoid having to scroll past them again after.
Took some time to decide which communities I did or didn't want, but down to 992 unblocked communities now, or hopefully 988-ish if instance-blocked ones can filtered out too.
To maximize the value of my All feed, I preemptively block communities whose posts I don't think I'll find interesting, minimizing how much All feed scrolling I end up needing to do.
While I don't need to block communities that are already instance-blocked, I'd still rather they not clutter the app's Lemmy Explorer feed, hence why I had asked the developer to filter out communities from blocked instances. If it's possible to tell which communities are blocked at the instance level, I'm hoping that the Arctic developer can extend the current filtering to communities blocked at the instance level to de-clutter the Lemmy Explorer list further.
Is there a way to tell which communities have been removed from an instance in that manner?
The Arctic app automatically removes communities from blocked instances from its integrated Lemmy Explorer list, but seemingly not blocked communities from unblocked instances, unfortunately.
The title is misleading, given that it's not being directed towards the delivery of any new aid, but rather paying for aid that's already been delivered.
No treaty ever awarded the Kuril Islands to the Soviet Union.
Personally, my main Linux usage so far has been the Steam Deck, which uses an immutable version of Arch Linux on which Flatpaks are the primary means of software installation.
The other main multi-distribution package formats seem to be Snaps and AppImages. AppImages seem to work anywhere, due to being self-contained, while Snaps have a dependency that appears to make them a viable alternative to flatpaks on systems other than the Steam Deck, which can't easily make use of Snaps due to the immutability of SteamOS. There's also Nix packages, though they don't seem to be as prevalent as the other three.
Otherwise, most major Linux distributions also have their own native package formats, such as Deb packages for Debian and Ubuntu, Pacman for Arch Linux, and RPM for Red Hat and Fedora.
Not sure how difficult it is to maintain different Linux packages types for a program, but thanks for your effort to bring Blorp to Linux!
In the case of 1337x.to, the megathread lists 1377x.to as the fake replica of it. In terms of quality, 1337x.to is one of the best public torrent indexers.
While I personally prefer not to use YTS releases due to their low quality, and can't seem to find a legitimate YTS link that yts.mx would be the replica of, as long as you're downloading via Prowlarr rather than going to the website itself, the only risk is the trustworthiness of the releases, rather than the possibility of ads or otherwise unwanted links on the website itself.