Yeah, that’s one of those tropes I hate pretty much everywhere, but (old) Star Trek is great enough to look past it.

They are skilled and professional. But how incompetently was the playbook written, if pretty much everyone can come up with something previously not derived spontaneously, if it’s that easy?

Great points.

Regular solar cells with better efficiency are already are thing, even in a compact travel format or as a novelty part of some electric cars. Those are cheap to produce, but still aren’t practical at all, unless we’re talking about something like a 2m² solar panel to charge a phone in a somewhat reasonable time on a very sunny day in an off-grid situation.

Using transparent solar cells additionally to regular ones in buildings instead of windows is pretty much the only reasonable application I can think of right now, but with a visible transmittance of 20% that’s kinda farfetched as well.

Das stimmt bei richtiger Verwendung schlichtweg nicht und es nützt niemandem, wenn man falsche Informationen herausposaunt. Wie auch im Artikel zu lesen, fand die timing attack auf üblichem Wege, gerade fürs deutsche Rechtssystem aber äußerst kontrovers statt:

Zur finalen Identifikation verpflichtete das Amtsgericht Frankfurt am Main schließlich den Provider Telefónica, unter allen o2-Kundinnen und -Kunden herauszufinden, wer von ihnen sich zu einem der identifizierten Tor-Knoten verband.

Bei einer Timing Attack werden, wie der Name schon sagt, Zugriffszeiten und möglichst viele (Meta-)Daten zu bestimmten Paketen statistisch abgeglichen. So kann man auch ohne direkten Zugriff auf die Daten bei ausreichender Datenlage feststellen, wer mit wem kommuniziert.

Hier wurde schlichtweg jeder o2 Kunde in Deutschland erstmal pauschal überwacht, ob er nicht mit einem bestimmten Server Kontakt aufnimmt. Um dem entgegenzuwirken, kann man natürlich erst einmal über einen (no log) VPN Provider gehen, um gar nicht erst zugeordnet werden zu können.

Yup. A variation of the quote (basically capitalists instead of American businessmen) is commonly attributed to Lenin instead of Khrushchev. But that, too, can’t be verified and is said to be fake.

Instead of waiting for a zombie fungus to evolve into something that can infect humans, they decided to cut out the middleman and made cyborg mushrooms.

Buying a domain. There might be some free services that, similar to DuckDNS in the beginning, work reliably for now. But IMHO they are not worth the potential headaches.

DuckDNS pretty often has problems and fails to propagate properly. It’s not very good, especially with frequent IP changes.

Random guy with no affiliation to crypto and only a vague understanding of monero from another instance here, who saw the post on /all.

Most people stumbling over posts like this probably see yet another shady cryptocurrency and aren’t interested or even actively dislike it, resulting in downvotes. Calling people “grudgeful bitfags” and “overly-sensitive leftist fediverse dwellers” probably doesn’t help all that much either, neither do comments that attribute a general disinterest to a “very successful psyop by the CIA to make crypto look like a scam”.

Damn, that’s wild. Cheers for sharing!

I have an understanding of the underlying concepts. I’m mostly interested in the war driving. War driving, at least in my understanding, implies that someone, a state agency in this case, physically went to the very specific location of the suspect, penetrated their (wireless) network and therefore executed a successful traffic correlation attack.

I’m interested in how they got their suspects narrowed down that drastically in the first place. Traffic correlation attacks, at least in my experience, usually happen in a WAN context, not LAN, for example with the help of ISPs.

Sounds interesting, got any links for further reading on that?

I can’t quite connect the dots between wifi/internet traffic spikes when IRC is so light on traffic that it’s basically background noise and war driving.

Nice message, but the thought of the existence of a competitive scene of contractors specializing in mounting TVs is hilarious. Also, that mounting plate is crooked af.

deleted by creator

I wrote a simple, locally running Webapp some time ago, that targets the Lemmy Import-/Export-API and supports transferring only specific userdata between accounts, as demonstrated in this corresponding Wiki Entry.

The import functionality in Lemmy is additive in nature, meaning anything you import gets added on top of existing settings instead of replacing it.

Does the same thing as these manual instructions for this usecase, may be helpful to some.

Ehhh.

Yeah, compared to a few years ago, it’s very much improved and a lot of games, especially those on Steam, run pretty good and in rare cases even better than on their native platform, Windows.

But the pretty much broken state of VR support combined with some annoying bugs that are very hard to troubleshoot even for advanced users, the decision by most AAA and even some smaller studios to actively block Linux clients in multiplayer games via anti-cheat measures and the usual Linux fuckery of HDR, VRR (which hopefully will get better now that Wayland is getting there) and some NVIDIA fuckery (which is also getting better) leads to the following conclusions for me:

1. Linux Gaming is improving.
2. If all you play are some indie titles and/or single-player titles, you may be good.
3. If you want to play in VR, most popular multiplayer titles and rely on features such as HDR and VRR, you’ll still need to dual boot into Windows.

I’m very much looking forward to the day when I can fully banish Windows, at least from my private machines. I’m very tolerant towards debugging and living on the bleeding edge, if that is needed. But I don’t see the need for Windows for PC gaming to go away anytime soon for most users and, frankly, writing love letters to Linux Gaming without mentioning even some hurdles can, has and will take new Linux users by surprise and turn them off. Communicating transparently, so the user can make their own informed decisions, is a better strategy.

I’d appreciate it very much!

Great suggestion to secure the backups themselfes, but I’m more concerned about the impact an attacker on my network might have on the external network and vice versa.

That’d be the gold standard. Unfortunately, the external network utilizes infrastructure that doesn’t support specifying firewall rules on the existing separate VLAN, so all rules would have to be applied on the Pi itself or on yet another device between, which is something I’d like to avoid. Great general advice, though!