Pfosten

On the other hand, the GDPR’s concept of “personal data” is extremely broad, much more so than the US concept of PII. Personal data is any information relating to an identifiable person. Pseudonymous info is still personal under this definition. Online usernames or social media handles are identifiers, and any linked info (e.g. posts, comments, likes) is personal data as well.

So Lemmy and other Fediverse stuff is well within the GDPR’s material scope.

However, the GDPR’s “right to erasure /to be forgotten” is more nuanced. It doesn’t quite always apply (though usually does). OP very likely has the right to request deletion from individual instances.

Posts have been published through federation. The GDPR anticipates this (I think in Art 17(2)): if personal data has been made public by the data controller, and erasure is requested, then the data controller is obliged to take reasonable steps to notify other controllers of this.

The ActivityPub protocol has built-in support for sending out such deletion notifications, and last time I checked Lemmy implements this. Of course the receiving instance might not honor this, but that’s outside of the responsibility of the initial data controller.

While I’m not entirely convinced that everything here is 100% compliant, federation is less of a compliance issue than it might seem.

Die Website ist relevant genug um einen kurzen Wikipedia-Artikel zu haben: https://de.wikipedia.org/wiki/Caschys_Blog Aber ja, man muss den Blog nicht gut finden.

Original der Meldung findest du etwa hier: https://workspaceupdates.googleblog.com/2023/07/adding-line-numbers-to-google-docs.html

The cookie consent rules appeared 2009, and consent was made more strict in 2018 with the GDPR.

EU bodies such as the WP29 data protection board had been writing since at least 2014 on the need of reform because the cookie consent rules are onerous in practice. Everyone wants reform.

So there was (is?) an effort to replace the ePrivacy Directive with a shining new ePrivacy Regulation that would also harmonize it with the GDPR. At the time, it was hoped it could come into force together with the GDPR in 2018. This regulation would have allowed the use of some cookies without consent, even when not strictly necessary.

But the proposed regulation is disliked by both the data protection side and the industry side, because it changes the existing balance. It was heavily lobbied against by Google and others, and never got ready enough for a vote (report from 2017, and in 2021 the NYT reported on internal documents where Google boasted that it successfully slowed down any progress). Every year someone in the EU tries to pick it up again, but always there’s something more important and it gets dropped again. I guess the effort this article reports on will falter as well.

Some silver linings though:

• Because responsibility for enforcement for cookie consent currently differs from GDPR stuff, clever data protection authorities like Belgium and France have been able to issue fines against big tech companies without having to involve their extremely industry-friendly Irish colleagues.
• Subsequent lobbying has not been able to prevent improvements on other aspects, e.g. Digital Markets Act and Digital Services Act, the latter of which also forbids Dark Patterns. However, these Acts primarily affect very large companies, not the average website.

The text does technically give the reason on the first page:

It is not a regular language and hence cannot be parsed by regular expressions.

Here, “regular language” is a technical term, and the statement is correct.

The text goes on to discuss Perl regexes, which I think are able to parse at least all languages in LL(*). I’m fairly sure that is sufficient to recognize XML, but am not quite certain about HTML5. The WHATWG standard doesn’t define HTML5 syntax with a grammar, but with a stateful parsing procedure which defies normal placement in the Chomsky hierarchy.

This, of course, is the real reason: even if such a regex is technically possible with some regex engines, creating it is extremely exhausting and each time you look into the spec to understand an edge case you suffer 1D6 SAN damage.

Exos ist Seagate’s Enterprise-Segment. Generell sehr gut (und möglicherweise bessere Total Cost of Ownership), aber:

• Die Specs von genauen Modellen vergleichen, nicht von Modellreihen. Es gibt viele Exos-Modelle mit Unterschieden bei Leistungsaufnahme, Garantien, Lautstärke, … letzteres ist für einen Rack-Server im Enterprise-Bereich übrigens egal, für ein NAS im Wohnzimmer jedoch wichtig.

• Nicht versehentlich die Modelle mit SAS statt SATA kaufen.

• Bei Exos gibt’s keinen inklusiven Datenrettungs-Service, falls das ein Verkaufsargument ist.

• Manche Platten werden ohne volle Garantie verkauft.

Für mich ist leider Lautstärke relevant sodass ich keine Exos verbaue. Ansonsten würde ich das bedenkenlos tun.

HGST Ultrastar sind legendär, aber ich bin nicht up to date was deren Qualität seit der Übernahme durch WD angeht.

C++ does have the problem that references are not objects, which introduces many subtle issues. For example, you cannot use a type like std::vector<int&>, so that templated code will often have to invoke std::remove_reference<T> and so on. Rust opts for a more consistent data model, but then introduces auto-deref (and the Deref trait) to get about the same usability C++ has with references and operator->. Note that C++ will implicitly chain operator-> calls until a plain pointer is reached, whereas Rust will stop dereferencing once a type with a matching method/field is found. Having deep knowledge of both languages, I’m not convinced that C++ features “straightforward consistency” here…

Well, it’s about Peter Thiel, who also founded the Palantir surveillance technology company. As a source for his involvement with Brave, Wikipedia cites this TechCrunch article, which mentions funding from Thiel’s “Founders Fund”.

I’d rather criticize Brave for other reasons though, like being led by Brendan Eich or supporting crypto.

That’s not the correct criterion. There are multiple German laws that require imprint-style disclosures.

Some of them are indeed specific to commercial activities.

But the Impressumspflicht typically means §5 TMG which requires an Impressum for

geschäftsmäßige, in der Regel gegen Entgelt angebotene Telemedien

Rough English translation:

Telemedia offered in a business-like manner, typically for remuneration

Critically, “geschäftsmäßig” does not mean “commercial” or “profit-oriented”. In particular, nonprofit organizations also act geschäftsmäßig.

IANAL, but it doesn’t sound like your service wouldn’t be geschäftsmäßig.

All of this is irrelevant anyway because you very likely have to publish a privacy notice per Art 13 or Art 14 GDPR. This must include the identity and contact details of the data controller (i.e., you). The German data protection authorities expect that the identity includes your real name and a ladungsfähige Anschrift (address where you can be served), so pretty much exactly what would be included in an Impressum anyway.

This article is ahistoric and unnecessarily conspirational.

Signal and its predecessors like TextSecure have been run by different companies/organizations:

• Whisper Systems
• Open Whisper Systems
• Signal Technology Foundation (and its subsidiary Signal Messenger LLC)

Open Whisper Systems received about 3M USD total from the US government via the Open Technology Fund for the purpose of technology development … during 2013 to 2016. Source: archive of the OTF website: https://web.archive.org/web/20221015073552/https://www.opentech.fund/results/supported-projects/open-whisper-systems/

The Signal Foundation (founded 2018) was started by an 105M USD interest free loan from Brian Acton, known for co-founding WhatsApp and selling it to Facebook (now Meta).

So important key insights:

• It doesn’t seem like the Signal Foundation received US government funding. (Though I haven’t checked financial statements.)
• The US government funding seems to be a thing of the fairly distant past (2016). The article makes it sound like the funding was just pulled this year.
• The US government funding was small compared to Signal’s current annual budget. It was not small at the time, but now Signal regularly makes more from licensing its technology than it regularly received from the US government. According to ProPublica, Signals financial statements for 2022 indicate revenue of about 26M USD

Domains mit Unicode/Sonderzeichen sind doof.

Aus Gründen der Sicherheit und Kompatibilität werden Domain-Namen mit nicht-ASCII Zeichen tatsächlich via Punycode notiert, der echte Domain-Name ist dann xn--irgendwas. Zum Beispiel,

dömäin.example
=
xn--dmin-moa0i.example

Das sieht einfach doof aus wenn der Browser letzteres anzeigt, egal ob dein Link jetzt schöne Sonderzeichen haben könnte.

Das Browser das machen ist extrem wichtig zur Vermeidung von “Homograph”-Angriffen, bei der Phisher eine Domain registrieren die so ähnlich aussieht wie irgendwas bekanntes, aber in Wirklichkeit Sonderzeichen benutzt. Wann Browser Unicode oder Punycode anzeigen unterscheidet sich nach verschiedenen Heuristiken. Der einzige zuverlässige Ansatz für Domains die immer gleich angezeigt werden ist ASCII.