Giuseppe Aceto

@goetz@freiburg.social @jpmens@mastodon.social @gereon@chaos.social I appreciate the joke, but I find it quite enlightening, because it made me realize the following. Processing a single-file encoding of a database is not technically different from processing a compressed archive: the second is just a very specific use case for the first. It's just a matter of interface. Want it to be MORE Unix? implement both sqlite3 and zip as interfaces to an underlying single-file relational database manipulation library (applies to ALL file formats).

@mike@sauropods.win @mahmoudajawad@mastodon.online @clifff@shakedown.social @Gargron@mastodon.social also consider that in the Fediverse there is no Real Name Policy (pseudonymity is actually a huge healthy feature here). Thus allowing Meta to link identity, personal information, and public (but possibly pseudonymous) communications is a huge loss of function for the user of Threads. I hope that the user is well aware of this and gets something valuable in return (I fail to imagine what). 2/2

@mike@sauropods.win @mahmoudajawad@mastodon.online @clifff@shakedown.social @Gargron@mastodon.social Your straw man is that mastodon is not for private conversations. Nobody said the contrary (hence a straw man). The simple point that you are (intentionally?) confounding was clear in the toot you replied to: the *app* by Meta requires permissions for personal data collection from the user's phone. Doesn't matter what Meta's instance federates with: you give Meta your (public) communications AND your private identifying info. Hope this clarified the issue.

@goetz@freiburg.social @jpmens@mastodon.social @gereon@chaos.social no need to change your mind: I agree. Somebody else change our minds. But working from the command line, zip and sqlite3 can process the archive/database with similar level of abstraction. If you're talking about archives of archives, and archives within filesystems, and databases within archives, we're talking reCURSEon: different problem.