@jon yeah, i’m pretty sure flickr could confirm them the date of upload if they want to go there, if they don’t trust flickr and neither the wayback machine, then they’ll get the boot from a judge. But it can be a pretty intense process for you, if they cannot hear that they might be wrong before going that far.
Automated IP infringement can be a real PITA, it’s never smart enough and it’s been embolden by platforms like youtube giving them too much power.
Quand je vois certains dire "Mais il ne faut pas bloquer Threads, pensez à ces pauvres utilisateurs sur Facebook/Insta/Threads !"
C'est un peu comme dire "Mais il faut faire du commerce avec l'Iran ! Regardez ces pauvres Iraniens !"
Alors fondamentalement oui, ces pauvres iraniens.
Mais ça n'excuse pas de faire du commerce avec ceux qui les enferment.
On peut avoir pitié pour un peuple sans pour autant accepter leur oppresseurs.
@captain_niglo@sebsauvage ils ne peuvent pas plus collecter tes données que n’importe quelle autre instance mastodon (et j’ai l’impression que beaucoup de gens oublient cette possibilité), les pubs ne sortirons certainement pas de threads, pour moi, tous les problèmes cités (sauf la modération, qui peut être une cause de blocage) sont ceux de leurs utilisateurs, pas les nôtres, en se fédérant, on donne à ces utilisateurs la possibilité de regagner en liberté, sans se compromettre nous même.
@sebsauvage@Flop_Ysh mais il faut absolument supposer aujourd’hui que le fédiverse est aspiré par tout un tas d’entreprises et de services de renseignements, ce n’est pas un espace privé, n’importe qui qui crée une instance récolte par défaut énormément de contenus. Il faut sans doute utiliser l’api pour reconstituer les graphs, mais je suis quasi certain que des gens le font déjà.
L’arrivé de Méta devrait clairement être une opportunité de rappeler ça aux gens.
@S1lencioz@captain_niglo@sebsauvage ben non, je trouve pas l’exemple parfait, tant que la fédération de threads avec le fédiverse n’a pas un effet néfaste (qu’on ne m’a toujours pas expliqué, au lieu de me rappeler les méfaits de meta que je connais déjà), et que le blocage n’est pas une solution a ces problèmes (idem, c’est pas clair), alors je ne vois pas de raison de le faire, et encore moins de l’imposer à tous, comme certains le souhaitent.
@S1lencioz@captain_niglo@sebsauvage tu parle d’emprisonnement, comme si l’arrivé de méta changeait quoi que ce soit à ton utilisation de mastodon, si c’est le cas il faut m’expliquer en quoi tu sera moins libre quand ils seront fédéré, par ce que je ne vois pas.
Si c’est pour tes données perso que tu crains, alors méta n’y change rien, le fédiverse les distribue déjà gratuitement à qui les veux.
@sebsauvage@S1lencioz@captain_niglo désolé, mais croire que tous les admins des 15k+ instances de mastodon font ça pour faire un gentil réseau social, me semble naïf, il n’y a aucune raison de penser que toute entreprise ou agence de renseignement voulant nos données n’ont pas déjà monté leurs propre instance avec utilisateurs réels ou fictifs juste pour avoir une BDD a explorer.
Il y a pleins de gens très sympa ici, mais c’est open bar pour les autres aussi.
On ne sait pas si Méta ne le faisait pas avant, ils pouvaient tout à faite le faire sans construire une application a distribuer à leurs utilisateurs, et d’autres le font déjà, c’est une certitude.
Le blocage n’est juste pas une réponse effective au EEE, ça change quoi si on coupe en premier? Ils auront juste encore moins de raisons de rester compatible.
@folkerschamel@davidism as your project grows bigger, it really helps with avoiding inconsistencies that could almost work for long enough that you don't detect bugs until it becomes really hard to fix them.
Type dynamism is really nice when you get started, you can experiment fast, but once the project stops cleanly fitting in your head, you need type declaration to help you.
You know what, chances are that X is someone who meticulously prepares their talk and busts their ass rehearsing it over and over and over. Recognise and appreciate their effort, and its results.
Apparently even though the online poster session for the ALAN light pollution conference isn't for 2 weeks, I have to get my poster uploaded by tomorrow.
Which means I get to spend ALL DAY frantically putting together a poster on satellite pollution and stewing about how much I HATE Starlink. I am going to need to smash something very badly when I'm done with this poster...
@sundogplanets Don't worry, i'm sure AI will fix that problem. Or maybe you'll just have to move your telescope to Mars, i hear it's going to be pretty cheap to go pretty soon.
@osc well, ideological or not, this is tribe behavior to me, meta is identified as the enemy, so the thing we are running from, so when they get close, this is war. This requires a very simplified vision of what Meta is, we know all there is to know about it, it's bad, and we have the recipes, yes, meta is a bad company, so that's all there is to know about it.
But even accepting it as the enemy, even going to war with it, requires understanding it and preparing the playbook.
@HistoPol@osc I know Meta did terrible, terrible things, even arguably helping at least one genocide. Yes, it’s a harmful company.
That doesn’t say anything about the arm it can do to the Fediverse, with intents or not (that doesn’t matter), and how blocking the thread app helps.
It’s a very knee-jerk reaction, for understandable reasons, but things are not so simple indeed, and we need to understand the actual threats to the fediverse, if we want to have a chance at preventing them.
@HistoPol@osc if anything, the arrival of Meta/Threads should be a great opportunity to explain to people that no the fediverse is not a private space, it might be more or less "safe", because moderation prevents most attack in this place, but it doesn’t keep the information in, any company, gov entity or even individual can create for modest costs, an instance that will archive everything happening in the fediverse, and be able to search that DB.
@HistoPol@osc this doesn’t even begin to address how using mastodon has any way changed regarding your PII since Threads joined, nor how blocking them will change anything.
Because this fails to address how all the data you post on mastodon is already public, and what more is gaining (from you, not from its users) by joining the fedi with an app.
If mastodon users are not-infosec-savy, they are already into trouble, they were the instant they joined mastodon.
@HistoPol@osc yeah, the question is more fuzzy to me about how easy it is to currently fetch/maintain a global social graph of the fediverse, i think you have to either talk to each server’s API, being careful about hitting rate limits, or scraping the instance webpages, though i’m sure a motivated actor could certainly build a relatively up to date version with smart refresh rates and distributed workers.
It is certainly something to keep in mind at least for activists.
But there is no reason to think blocking them is actually going to achieve anything to "protect" us from them, not until there are clearer understanding of what bad behaviors to expect from them, and how federating with them would enable them.
For now, all the examples of abuse from meta i seen suggested, were based on meta threatening to de-federate us, so de-federating them in the first place is just getting there right away.
What is your opinion on PRIMARY KEYs for database tables that are append-only (i.e. for logging) and have no natural primary key and are not referenced?
@louis funny how nobody provided a rational for the winning option. Feels very much like a mantra "all tables should have a PK with autoincrement", that cannot be questioned.
@louis well, what would you select on? If it's not your PK, then not having it makes no difference, and you can still have indices (on timestamp for example, or anything you'll commonly search/order by, but careful with write heavy tables) to filter on (and update/delete), or for a log, full text search might be an interesting thing to enable. PK makes sense for relational data, here you don't seem to treat it as such, and i don't see what you lose for not having it.
@louis in fact that’s why i think the winning option makes the least sense of all, as you are never going to want log row 128141578, but you might want all the log rows between 2023-06-25T00:25:20 and 2023-06-25T00:30:00 or something, and having an index on that, (probably cheap to maintain, especially if you never delete ?).
While a PK would mean that every insert waits for a lock on the table to be able to get the next value of the series, which can be a bottleneck.
@louis no worries, i guess i wasn’t clear 😆 i think PK-less table can make sense to a bit more than tables where you never update or delete, as long as your criteria for selecting/updating/deleting do not require a PK, (so impossible to know if you match one or multiple rows, but that’s not a problem for the use case), then it’s fine.
I see PK as providing unicity and indexing, if you don’t need the unicity, bust an index on the fields you need to search for efficiently is cheaper.
Don’t kid yourself. “Artificial intelligence“ is just Big Tech’s way of saying “hey, it’s not our fault. It’s the machine’s!“ In point of fact, every malign use of “AI“ is really just some human-composed algorithm doing something that maximizes profit or control at the expense of people. We must not let these companies off the hook. They’re in charge. Not the machine. Pay attention to the man behind the curtain.
