realTimo @realTimo@mastodon.social
Joined Aug 2018
realTimo
boosted
Client: "Okta or GTFO"
Okta: "Android, iOS, or GTFO"
Me: "Fine. I'll flash a test device"
Okta: "Google account or GTFO"
Me: "Fine. I'll make a burner"
Google: "SMS or GTFO"
Me: "Fine. Here is my #"
Google: "No VoIP. Trackable cell # or GTFO"
How is this normal?!
realTimo
boosted
So I don’t use Chrome but I have Ungoogled Chromium (https://codeberg.org/Eloston/ungoogled-chromium) as certain things only work under Chrom(ium) and I only just realised Google requires a Google account to install extensions.
Wow.
Hint: You can bypass this restriction using this the Ungoogled Extension Installer: https://github.com/UnnoTed/Ungoogled-Chromium-Extension-Installer
The lengths we have to go to in order to protect our privacy from basic everyday things is ridiculous. We need fundamental change. Surveillance capitalism needs to die.
realTimo
boosted
@qoheniac Jupp, genau so. Die offizielle App des RKI verwendet noch eine proprietäre Bibliothek **in der App,** um mit Google's Exposure API zu kommunizieren (daher kann F-Droid die App nicht bauen: nicht nur wegen der Lizenz, sondern auch wegen fehlendem Quellcode). Der Fork verwendet stattdessen gleich die komplett freie Exposure-API von Marvin **direkt in der App** – braucht somit also weder Google Services, noch microG. Und kann von F-Droid gebaut werden.
Fediverse to the rescue!
I am admin on a bunch of servers. They're set up similarly for the most part, but have their individualities here and there.
While of course I document what I do and why, I do wonder: What is the canonical way to communicate one's config in an accessible way, also for not-pro's-but-savvy people.
Is it putting /etc under VCS and host a wiki alongside? Is there a smarter way?
Seems like doom #emacs is #office365 for #vim users.
I kinda like it. 
Guys, I need some help, I have a synology NAS that seems bricked, probably interrupted during an upgrade.
The status LED flashes constantly. The only thing the NAS does is acquire an IPv4 via DHCP (wiresharked that) which makes me think it's not entirely dead. However, nmap does not show a single open port.
Other peoples' issues on the web all seem to be fundamentally different.
Any idea? Boosts welcome!
realTimo
boosted
@ulrichkelber Ihnen ist klar, dass wir jetzt natürlich alle wissen wollen, über welche Software :D
realTimo
boosted
the predictable thing about linux's predictable network interface names is that I can predict I'll have no idea what it'll be
Ugh, gotta use #microsoft #teams, instead of #floss. First attempt in #firefox fails because video calls are only supported in #chrome.
That was after I had given up to configure #umatrix to work with #office365 and just allowed everything, including tons of third party frames.
Regardless of the browser, the teams web page prompts you to install a linux client, which turns out to be - surprise - electron based.
Now I wonder what's worse: Using chromium for teams or using that electron shit.
@realTimo ...and it's back up. We can stop running around in circles.
realTimo
boosted
I cannot find a single non- #CloudFlare site to upload a #torrent file to without being forced through a #Google #CAPTCHA
Show filesystem usage:
On regular systems: df -h
On Ubuntu: df -h | grep -v snap
realTimo
boosted
@realTimo @tuxom @wion
As far as I know this attitude to flag "difficult" content came up in the heydays of quitter.se with its main admin Hannes clearly opting for banning unpleasant and politically inconvenient views not of his taste. It generated a huge debate on censorship back then, with the usual rebuttal that "being free to speak doesn't entail being free to be heard".
Technically and legally, Hannes and others had a point though. As their servers were based in Sweden, and Sweden has certain laws prohibiting the public posting of content like Nazi propaganda, the provider/admin of such a server would have been legally liable for the content appearing on the Public Timeline of his server.
Enters federation.
Imagine you were on that GNU Social instance in Sweden (even if it prohibits Nazi stuff just for legal reasons) and subscribe to somebody on a server that is located in a different country in which the posting of Nazi stuff is legal (the U.S., e.g.). Like consenting to access adult sites, you may still subscribe to this account posting Nazi stuff. The Nazi stuff enters your Home Timeline (and by that the Whole Known Network of the instance). Problem now is that not just a repeat but also a (critical) reply could now heave the original Nazi post (via conversation) into the Public Timeline of the Swedish instance, thereby violating the Swedish laws and put the provider of the Swedish instance at legal risks. That was the technical (or legal) reason quitter started blocking instances and accounts.
Which was perfectly fine. In a sense. (To protect the provider of an instance from legal liabilities). But it had two impacts:
1) You were restricted in to whom you could reply to. Thus the sensible ban of Nazi stuff got mixed with the nonsensical intrusion in your freedom to even critically reply to such stuff. Restricting federation entailed restricting freedom of speech.
2) In the end, the Fediverse would divide into mutually sealed off sub-diverses of instances that interact with each others and closing off those they don't.
Then the blocking was expanded to content that was deemed "inadequate", that is, of different political or "cultural" positions. SJW and safe space attitude creeped into the criteria of moderating the instance. Instances became topical instances. The admin's saying was: "It is my house, it is my rules." (Thereby deciding that an instance is a house, not a conversation.)
In this blend of legally justifable and subjectively felt necessary blocking the idea of CWs only added its own flavour. Given a now established "culture" of banning content, hypersensitivites and the wish for "safe spaces" put pressure on admins to introduce means that the Public Timeline was "safe" to watch for anybody. Controversial content needed to be flagged in order not to expose people to stuff they deemed insensitive or even traumatic.
This seems to have been the way with GNU Social and Ostatus. I don't know how Mastodon and Pleroma and their protocols add to or deviate from these difficulties. Perhaps their protocols now allow interacting with problematic content without heaving it into the Whole Known Network and then Public Timelines of an instance that cannot allow for such to appear.
Anyway, muting and blocking of accounts by accounts is available, and the rest evades my understanding.
As far as I know this attitude to flag "difficult" content came up in the heydays of quitter.se with its main admin Hannes clearly opting for banning unpleasant and politically inconvenient views not of his taste. It generated a huge debate on censorship back then, with the usual rebuttal that "being free to speak doesn't entail being free to be heard".
Technically and legally, Hannes and others had a point though. As their servers were based in Sweden, and Sweden has certain laws prohibiting the public posting of content like Nazi propaganda, the provider/admin of such a server would have been legally liable for the content appearing on the Public Timeline of his server.
Enters federation.
Imagine you were on that GNU Social instance in Sweden (even if it prohibits Nazi stuff just for legal reasons) and subscribe to somebody on a server that is located in a different country in which the posting of Nazi stuff is legal (the U.S., e.g.). Like consenting to access adult sites, you may still subscribe to this account posting Nazi stuff. The Nazi stuff enters your Home Timeline (and by that the Whole Known Network of the instance). Problem now is that not just a repeat but also a (critical) reply could now heave the original Nazi post (via conversation) into the Public Timeline of the Swedish instance, thereby violating the Swedish laws and put the provider of the Swedish instance at legal risks. That was the technical (or legal) reason quitter started blocking instances and accounts.
Which was perfectly fine. In a sense. (To protect the provider of an instance from legal liabilities). But it had two impacts:
1) You were restricted in to whom you could reply to. Thus the sensible ban of Nazi stuff got mixed with the nonsensical intrusion in your freedom to even critically reply to such stuff. Restricting federation entailed restricting freedom of speech.
2) In the end, the Fediverse would divide into mutually sealed off sub-diverses of instances that interact with each others and closing off those they don't.
Then the blocking was expanded to content that was deemed "inadequate", that is, of different political or "cultural" positions. SJW and safe space attitude creeped into the criteria of moderating the instance. Instances became topical instances. The admin's saying was: "It is my house, it is my rules." (Thereby deciding that an instance is a house, not a conversation.)
In this blend of legally justifable and subjectively felt necessary blocking the idea of CWs only added its own flavour. Given a now established "culture" of banning content, hypersensitivites and the wish for "safe spaces" put pressure on admins to introduce means that the Public Timeline was "safe" to watch for anybody. Controversial content needed to be flagged in order not to expose people to stuff they deemed insensitive or even traumatic.
This seems to have been the way with GNU Social and Ostatus. I don't know how Mastodon and Pleroma and their protocols add to or deviate from these difficulties. Perhaps their protocols now allow interacting with problematic content without heaving it into the Whole Known Network and then Public Timelines of an instance that cannot allow for such to appear.
Anyway, muting and blocking of accounts by accounts is available, and the rest evades my understanding.
realTimo
boosted
Tech enthusiast: "I want smart lights, smart tv, everything, and connect them all to my digital assisstant!"
Tech worker: *looks wistfully into distance* "I should get a small place in a little town, with a garden, make my own furniture."
realTimo
boosted
Nicht ganz meine Definition von "nett"... 😬
"Nett: Die Noise-Cancelling-Intensität lässt sich nun in 11 Stufen von 0 bis 10 einstellen. (...) Drei Stufen lassen sich direkt am Gerät mit einem Knopf auf der linken Seite durchschalten; voreingestellt sind die Stufen 0, 5 und 10. Andere Werte lassen sich in der "Bose Music"-App für Android und iOS festlegen. Für den Betrieb der App muss man einen Bose-Account erstellen und außerdem den Standortzugriff erlauben."
Fediverse, I need your help.
I use #neomutt as my mail client. I get calendar events via email. I want to use a graphical calendar.
Does anyone know a graphical (CalDav capable) calendar that can import ics files from command line args?
korganizer seems to be the only option so far, but complains about a missing filename when reading from stdin and silently fails when reading from a named file.
@linuzifer Erinnerst du dich an die Grünenpolitikerin, die auf Twitter über Globuli sinnierte?
Geht krasser.
https://hpd.de/artikel/kritik-an-ministerpraesidentin-wegen-homoeopathie-schirmherrschaft-16807
@fsfe That moment when you want to get an idea of the EU's take on copyright by peeking into the live debate - but then you realize, you probably don't even need to.
Joined Aug 2018
Server run by the main developers of the project 
It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!