Pika

It’s because people already Mass reported it so they disabled the ability for it

is it a “can” or a “must”? I don’t mind if it’s optional but yea it defo shouldn’t be required

Good. This needs to be done. So many officials are just “resigning” as a sign of mutual respect as that is what is considered the norm, but honestly they should just wait it out (and if fired fight it out if there is legal recourse like this to do so), there’s zero reason to keel over and let federal services get demolished out of moral obligations.

This doesn’t bode well.

The last time this happened was when Anonymous hacked PSN and took them down for a month after they went after Geohotz(cant remember the spelling) for jailbreaking/reverse engineering the ps3.

Radio silence like before as well. I hope they weren’t breached again.

might be in relates to issue link here

It was a good read, personally speaking I think it probably would have just been better off to block gotosocial(if that’s possible since if seems stuff gets blocked when you check it) until proper robot support was provided I found it weird that they paused the entire system.

Being said, if I understand that issue correctly, I fall under the stand that it is gotosocial that is misbehaving. They are poisoning data sets that are required for any type of federation to occur(node info, v1 and v2 statistics), under the guise that they said program is not respecting the robots file. Instead arguing that it’s preventing crawlers, where it’s clear that more than just crawlers are being hit.

imo this looks bad, it defo puts a bad taste in my mouth regarding the project. I’m not saying an operator shouldn’t have to listen to a robots.txt, but when you implement a system that negatively hits third party, the response shouldn’t be the equivalent of sucks to suck that’s a you problem, your implementation should either respond zero or null, any other value and you are just being abusive and hostile as a program

You are correct, my concern with it isn’t retrieving the data however, its the possibility that if the person involved had the means to, they could have a table of check-sums of files of interest. This system could be used to confirm or deny a file of interest is present on the device.

For the everyday person this is a non-issue, but from a privacy POV you should not be able to get any information in regards to what a file is.

Rainbow tables for password cracking works off a similar system, they take a bunch of commonly used passwords, hash them and compare them to leaked databases. If the hash matches an account you have the password. Most password handlers get around this by salting it, and hashing it repeatedly X amount of times, but I doubt that apple would do that for a checksum(and regardless they would know X and how it was made).

Again though I acknowledge that it’s a paranoia level concern, but I still am firm that a true encryption solution should not be able to get any type of info out of it that may help the third party.

It’s important to note here that even if you turn on this option, Apple does not support full end-to-end encryption, there are still multiple factors that they keep under standard data protection which means they still have the encryption keys. They keep this under the guise of deduplication so they can save on storage costs but some examples of this are:

• the apps+file formats you have installed
• your phone’s make model and serial number
• most metadata that defines what an item represents such as date time modification time
• all file checksums (this is scary imo)

They explain how everything with their encryption works here

this list is more concepts then actual enshittification. No YouTube, no reference to Google searches less helpful results. No reference to ad overload plaguing more services. No reference to crappy TOS’s with artibution clauses. It’s just using an excuse to say AI bad and rehash concepts learned back in 2015 with the drive to drop cable.