Notices by Himbo Techbro (r000t@ligma.pro), page 29

@coolboymew
That will just melt

@coin gap as a verb refers to the creation of a gap (as a noun); Gap as a noun is used to refer to a performance difference between two players of the same role ("jg gap"), especially one that substantially contributed to the game's outcome.

fedoff means dude was too mad to use his space bar. he meant to say "fed off". fed means ahead, has a lot of gold (and therefore items, and therefore stats), especially from kills.

@coin lmk if you need translations

what's weird is that I can't find single-word replacements for most of them, without rewriting the entire sentence. it's shorthand at this point.

Golly, I wonder why you had to make a new account.

It was dude's duo I got fed off of btw.

"Are you running up the electric bill making Steampunk Stallmen again?"

@coolboymew >switter
accidental fedi namedrop lmao

a US government representative: "It looks like you used bogus answers for the security question?"

me: "uh oh..."

flashback to yesterday: "I'll put some gamer words in here because they're hashing these, right?"

@Moon @coolboymew @essie Pilot G2 master race. Gel dries super fast.

@coolboymew
USE MORE GUNS AND THEN USE YOUR PYTHONS BROTHER

@CumskinFoidPuncher69420 @idiot

@idiot
Google makes glasses with a built-in camera and head-up display: OMG MY PRIVACY! I WILL TAKE THESE AWAY FROM SOMEONE AND SMASH THEM ON THE GROUND IF I SEE THEM. I WANT THESE BANNED FROM EVERY BAR AND LIBRARY AND RESTAURANT.

Apple makes glasses with multiple built-in cameras and head-up displays: Only $3,500? What a steal! This is going to revolutionize the way we do everything! Get used to it, chuds!

@coin There is a reason I'm not sharing the actual complaint or what they said in response to my reply. Ironically, it's to protect their privacy.

I saw some of my younger self in the complaint. This was (by my interpretation, which could btw be totally wrong) someone who was in a chat room among other people going "man someone should really flood him with GDPR complaints" and etc., and this is someone who said "Well.... he won't be able to find me, and won't be able to fuck with me so... I'll just do it."

This was clearly their first time swinging at someone like that, and that *particular* form of swinging at people (procedural fuckery), once refined, is actually p based imo. That's why my response was very matter-of-fact and I went out of my way to *not* dunk on them.

Their response, in short, was "oh, I didn't know any of that, I'll think on it and get back to you"

as:Public received its first (and only) GDPR complaint in early February, and I published my reply followers-only. In the interest of transparency, and because there is no longer a strategic purpose to holding it back, here it is:

------
I am fairly confident that the GDPR does not apply to my personal project in the United States. This is mostly because the United States is not a member of the European Union, and I do not do business in the EU.

But let's say it was. The Regulation would still not apply to any personal data that the data subject themselves deliberately made public. Obvious examples of this would include social media posts with the "Public"/"Everyone" scope. This even applies to special classes of "sensitive" data, when they are "manifestly made public by the data subject" under Article 9(2)(e). Please also keep in mind that if the Regulation was meant to cover public social media posts, then the user's instance would, in theory, be unable to disseminate that information to other instances, or even to other people on the same instance, under Article 5(1)(f), Article 32(2), and Articles 44 through 46. Even in such a case, the user would have consented to the "processing" of the data by their instance, which would include the "disclosure by transmission, dissemination or otherwise making available" (Article 4(2)) of each individual public post. This explicit consent would be both at account creation (for profile information, etc.) and at the time each public post is published.

It is also unreasonable to expect that this consent would only apply to dissemination or transmission to specific people or servers/instances, in this context. On a social media website running Mastodon, for example, posts with the "Public" and "Unlisted" scopes can be "boosted" by their original recipients, or anybody who knows the URL of the post. This immediately causes the "booster's" server to disseminate or transmit the information to any number of further third-parties for processing. This is normal and expected behavior of Mastodon and most other social media platforms; Making users aware of this would be the responsibility of the processor/controller that the user initially provided the data (the post content) to.

As a side note, the only other data potentially covered by the Regulation would be visitor IP addresses and similar information that is stored in the httpd's access log. General provision 49 excludes the processing of personal data "to the extent strictly necessary and proportionate for the purposes of ensuring network and information security," which httpd logs are generally considered to qualify as.

Even if the data itself was covered under the GDPR, the Regulation still does not apply to this website. There is no "offering of goods and services" to EU residents, which is required for the Regulation to apply to a controller or processor not established in the Union under Article 3(2)(a), and general provision 23. Provision 23 also specifies that the "mere accessibility" of the website is "insufficient to ascertain such intention" to explicitly offer goods and services to EU residents.

Further, this website and the software it runs on is a personal project. General provision 18 excludes from the Regulation any processing of data "by a natural person in the course of a purely personal or household activity" that is not commercial. I'm allowed to have hobbies, too.

Finally, violations of the GDPR by firms in the United States are typically remedied by fines or other sanctions to their counterparts registered in one or more EU countries. Again, this website is a personal project, and there is no firm, here or in the EU, to impose sanctions against.

If someone living in the EU wanted to give it a shot, I'd say their best first step would be to lodge a formal complaint with a supervisory authority such as the European Data Protection Supervisor, as laid out in Article 77. Their complaint form is located at https://edps.europa.eu/complaints-wizard_en

As a practical matter, the as:Public software powering the website will, at some point, be released as open source software. Each user of the software would be responsible for their own compliance with any applicable laws and regulations. For most, I doubt the GDPR would be one of them.

I hope this settles the matter.

--r000t

@coin I just used it and it took 924ms to pull a result. This is probably because Postgres is *not* on the same machine as the Display (the frontend), and is two VPN links away.

(The Display is run on a cheap VPS, the Recorder and Postgres are on my home computer, the Collectors are on various machines donated by friends, but I haven't orchestrated them yet)

@coin I feel like that's a trick question given that I haven't run the Collector in over a month.

Remember kids, you can't spell as:Public without :P

It's the ten year anniversary of the Snowden leaks.

You forgot all about those, didn't you? Too busy distracted by the identity politics? Maybe that was the point.

@coolboymew https://en.wikipedia.org/wiki/Conservation_of_energy

@coolboymew /b/rotip, UV flashlights charge those literally instantly

@matrix Modern smoke alarms really should be a voice prompt. Harder to ignore than a single chirp.

Then again, modern units also have 10 year built-in batteries.