To implement robust mitigations across Geomys, I did a survey of open source project compromises in 2024/2025.'nThree root causes dominate: phishing, control handoff, and unsafe GitHub Actions triggers.
Uncategorized
1
Posts
1
Posters
0
Views
-
To implement robust mitigations across Geomys, I did a survey of open source project compromises in 2024/2025.
Three root causes dominate: phishing, control handoff, and unsafe GitHub Actions triggers. All three can be systematically avoided.
-
undefined cybersecurity@poliverso.org shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
ADUC - Articolo - Stati Uniti d’Europa. Obiettivo mancato e prospettive disastrose
https://www.aduc.it/articolo/stati+uniti+europa+obiettivo+mancato+prospettive_40481.php
-
Brutalismbot (@brutalismbot.com)
https://bsky.app/profile/brutalismbot.com/post/3mc5qd75h6e2j
> Formerly the Met Breuer (now Sotheby’s HQ) in nyc r/brutalism
-
@phabrizio 1.60 € per almeno 5-minuti uomo di lavoro, tra farti il caffé, prendere il pagamento, ritirare e lavare la tazzina, pulire il tavolino o il bancone. Non so se l'iva sul caffé sia da alimentari (4%) o regolare (22%), ma nei due casi siamo tra i 15 e i 18 euro lordi all'ora, a grandi linee. ma devi ancora toglierci le spese dei materiali ed energia (che mi risulta siano la cosa che influisce di meno), l'affitto del locale, ecc. ecc.
il caffé al bar costa troppo poco
e quindi la soluzione è: prendilo solo una volta ogni tanto, ma quando lo prendi per carità prendici almeno anche una brioche!
-
Anyone has a recommendation for a phone cover vendor? Android, so no need for Fancy magnetic thingies.
I broke a few screens over the years dropping my phone and I'm thinking maybe I need it :)
-
@futurebird Also, I tell junior devs to think back to science class. Every change you make to code is an experiment; your hypothesis is that the new code will be somehow better than the old. But you can't put too many variables in an experiment, or you won't know which changes mattered and why.
So test often. Test after every line of code if you have to. It sounds annoying but it's much easier than the avalanche of bugs you get when running 1000 new lines the first time.
Go slow to go fast.
-
@futurebird i think Microsoft in the 90s set up this attitude towards computers that still lives today: “it’s your fault if it doesn’t work”.
I never had to use Windows — ever — and every time I would sit down to try, something glaringly bad would be right there interfering.
And I’ve been a dev and UX person for nearly 40 years.
-
Yes, that's exactly what I did! I already posted a couple of answers, but after looking at the whole thread I realized I didn't really understand the question. Yes, I think this is the answer to the question.
-
@futurebird oh I see, indeed this was with university students, I've never teached computer science to younger students so I'll read what others have suggested. But at any stage of learning, I completely agree that some fun being involved greatly greases the wheels :)
