taizou @lion@computerfairi.es
Joined Jun 2017
taizou
boosted
I so, so, so don't want to drive any new car that can do this:
A federal appeals court refused to bring back a class action lawsuit alleging four auto manufacturers had violated Washington state’s privacy laws by using vehicles’ on-board infotainment systems to record and intercept customers’ private text messages and mobile phone call logs.
The court ruled that the practice does not meet the threshold for an illegal privacy violation under state law, handing a big win to automakers Honda, Toyota, Volkswagen and General Motors, which are defendants in five related class action suits focused on the issue.
The plaintiffs had appealed a prior judge’s dismissal. But the appeals court ruled Tuesday that the interception and recording of mobile phone activity did not meet the Washington Privacy Act’s standard that a plaintiff must prove that “his or her business, his or her person, or his or her reputation” has been threatened.
A suit filed against Honda in 2021, argu[ed] that beginning in at least 2014 infotainment systems in the company’s vehicles began downloading and storing a copy of all text messages on smartphones when they were connected to the system.
An Annapolis, Maryland-based company, Berla Corporation, provides the technology to some car manufacturers but does not offer it to the general public, the lawsuit said. Once messages are downloaded, Berla’s software makes it impossible for vehicle owners to access their communications and call logs but does provide law enforcement with access, the lawsuit said.
Many car manufacturers are selling car owners’ data to advertisers as a revenue boosting tactic, according to earlier reporting by Recorded Future News. Automakers are exponentially increasing the number of sensors they place in their cars every year with little regulation of the practice.
https://therecord.media/class-action-lawsuit-cars-text-messages-privacy
Found another good console design. It's a bear
Model number is H8 but I can't find it for sale outside China atm
https://detail.1688.com/offer/719538095089.html
taizou
boosted
taizou
boosted
Dogfood Bowl
Cooking, 30cm4mm to roll up
A dish to put pet food in. Use it for both solid and liquid food.
------------------------
オワン
クッキング 30cm4mm
ドウブツ センヨウノ ゴハンノ サラ カタイゴハンモ スープモ ドッチモ イレラレルヨウダ
I also found that "file per table" was actually ON but for that particular table it doesn't create a file for it, even if I dump and reimport the table? hello???
once again I'm going to fucking bed
Tried a few possible solutions for reclaiming the space without recreating the whole DB. None of them worked. Piss
taizou
boosted
taizou
boosted
the dust has settled, i got my stuff (mostly) set up, now it's time to... go to space?? Wednesday, November 8, 4:00 PM PST, fellow ear-haver Lizstar and i will be taking a trip to Saturn. what treasures will we find there? will i remember my helmet? is there a burger joint on the way? https://twitch.tv/rachelretro
taizou
boosted
taizou
boosted
Look at this cat https://www.youtube.com/watch?v=wIzx2lc6Wfc
We did it gamers. Deleted all the spam text. And how much space has that gained me? fuck all!!!!! because InnoDB will never give you space back once it's used it, if you have the "file per table" setting turned off (which is the default) it just dumps everything into that fucking ibdata file which can never get any smaller. The only thing you can do from here apparently is to dump all the DBs, wipe the whole thing and reimport them. I'm going to fucking bed
well my internet went down but i'm tethering off my phone to fucking finish this
I deleted all those orphaned slots/content entries and ran the script. the script actually found the orphaned text this time but threw an error when trying to delete it. so I ran another sql query to delete the text
THAT failed cos it ran out of space while trying to write a temp file so I'm now doing them 100 at a time
OK so what I figured out is that revisions are linked to content by the "slots" table, and the "slots" table suspiciously has 2888 entries referencing nonexistent revision ids, which is the exact same number of archived revisions that were purged
So I THINK I should be safe to delete those slots and Then delete the content entries corresponding to those slots and Then delete the text entries corresponding to the content entries
Sorry for posting through this btw
I Think what happened was the first script purged the references to the revisions in the "archive" table, meanwhile the second script is looking for references in the "content" table which was not actually touched by the first script
so uhhhhh I guess I can try and identify orphaned content entries myself and delete them and then run the second script and hope I don't fuck everything up
How did I even get here this has nothing to fucking do with Docker
so i ran a mediawiki script to purge the deleted revisions, which worked
but that script then runs another script to purge orphaned text records (which are the thing that is actually taking up the space) and that... did nothing
cool cool thanks
Joined Jun 2017
