Notices by :verified_2:防空識別區𝒔𝒐𝒄𝟶 (adiz@soc0.outrnat.nl), page 40

@dcc@annihilation.social real libertarian@PurpCat@clubcyberia.co

@dcc@annihilation.social Just dumb libertarian logic that never makes sense. @PurpCat@clubcyberia.co

@PurpCat@clubcyberia.co Bro, just trust the "invisible hand"! @dcc@annihilation.social

@coolboymew@shitposter.club Ah, I see you are not a gentleman of culture.

@coolboymew@shitposter.club Needs pit hair tbh.

@coolboymew@shitposter.club Or, better yet, pit stubble.

Wrote about this 2 days ago. Appears today that this instance is now on the Oliphant "tier 0" block-list ("[r]equires 60-80% consensus on blocks to appear on this list"). For reference, soc0.outrnat.nl is, effectively, a single-use instance at the moment. I am virtually the sole inhabitant. Regardless, I maintain a robust terms of service which I hold myself to, I widely defederate from hostile or offensive instances, I'm a pretty open leftist, and I don't tolerate hateful rhetoric or harmful content here. I have regularly described the content curation objective here to prune the Fediverse into a comfortable, constructive, friendly environment.

Additionally, I know my inclusion on these block-lists is wholly inorganic, not only due to the laughable logic surrounding "algorithmic" block-lists (detailed in the quoted post), but, also, because I can trace the original blocks that started the ball rolling on this Fediverse butterfly-effect: pleroma.envs.net, cathode.church, and mastodon.art.

These 3 hostile instances blocked this instance almost immediately, and they did it by blocking the top-domain, not the sub-domain: outrnat.nl. Anyone who would have come across this instance and found the content objectionable or harmful would, one would think, organically block this instance's sub-domain: soc0.outrnat.nl; Right? Not the top-domain, which isn't a Fediverse instance. Instead, what I've seen is that the 3 bad actor instances listed above blocked the top-domain here in quick succession (it only takes 1 for others to immediately and blindly follow).

What happened then is others, also, quickly and blindly followed suit. I cannot find any instances blocking the soc0.outrnat.nl sub-domain, but there are now plenty blocking the top-domain, outrnat.nl. Why? Because they saw it blocked by an instance and followed along. What happens then? Others see it blocked by an instance and follow along. Like a feedback-loop this festers and grows. Then, these major, centralized, "algorithmic" block-lists decide that, "algorithmically", due to a certain "consensus" of block-happy instances they reference, an instance must merit inclusion on their "tier 0", "worst of the worst" list! This just further accelerates the feedback-loop, as others blindly adopt these centralized block-lists, because, surely, these major block-lists would have definitely vetted and investigated the instances they've included on their lists, right? They're trustworthy! Etc. etc..

#Fediblock is a fucking cancer.

RE: https://soc0.outrnat.nl/notes/9k1bohd10k

@kirby@lab.nyanide.com The thing is that I don't interact with "duh nazeeys and hate speach poesters". I, myself, am pretty block-happy with stuff like that, considering the virtual single-user-instance nature of this instance + the fact that I just don't want negativity and hateful trash on my timeline.

@dcc@annihilation.social On XOrg you get 0 functionality, by the way.

@dcc@annihilation.social Unlike KDE it apparently has full functionality for this 2-in-1 laptop on the Wayland session. On KDE you only 2/3rd functionality in Wayland, but virtual keyboard is missing because the required package is fucked.

Canonical effectively ruined Ubuntu desktop with Snapcraft and making Snaps mandatory/unavoidable. It's a painful process to "de-Snap" Ubuntu to the point that it's not even worth it.

So, the more research I do, the more this appears to be the case: Ubuntu with Gnome has full support for Lenovo "2-in-1" devices, including automatic screen rotation, virtual keyboard, and smart stylus support. I might be doing this, bros. I might be moving over to Ubuntu. :ubuntu:

RE: https://soc0.outrnat.nl/notes/9k35oewuja

Before I even fuck with Ubuntu I'm going to try and make Tumbleweed with KDE work here. I love Tumbleweed too much and I'm fully invested in it at this point. Referencing the Arch wiki (lol) while jamming out to this trying to solve my various issues. Darius---Feels Right ft. Dune https://www.youtube.com/watch?v=lo-P-3m0-cU #music

I got automatic screen rotation working by using Wayland instead of XOrg and installing iio-sensor-proxy and rebooting! 🎉:opensuse:

Now to figure out a virtual keyboard...

Holy shit: everything just works on Wayland (except a virtual keyboard because I guess this just doesn't exist for KDE for all intents and purposes despite being native to Gnome?). What is going on? Wayland is :based:⁉️ It just has tablet, touch-screen, and virtual keyboard support ("support" being the operative word for the virtual keyboard) out of the box? It's just there without me having to do anything other than boot into a Wayland session vs. an XOrg session?

Apparently there's like 1 single package for virtual keyboard on KDE called maliit and it hasn't been maintained in over a year and is broken. Embarrassing. Meanwhile, I am led to believe that if I simply just installed Gnome instead of KDE that everything would work.

I'm surrendering. I'm installing Gnome :gnomewhite: via YaST. Let's see how this works.

@dushman@den.raccoon.quest Where did you pull this from?

@pwm@crlf.ninja Oh, that piece of shit. @dushman@den.raccoon.quest

@pwm@crlf.ninja Absolutely wild. @dushman@den.raccoon.quest