#yolo

17 posts · Last used 10d

Back to Timeline
Wendy Nather @wendynather@infosec.exchange · Aug 04, 2026
RE: https://infosec.exchange/@Tarah/117033474618518745 Come take my money! I’m really bad at poker. So bad, that I have to relearn here every year. #yolo
Quoting
Tarah Wheeler @Tarah@infosec.exchange
This Friday at DEF CON I host the @eff@mastodon.social Poker Tournament, and novices are especially welcome. We play Fri Aug 7, noon to 3, at the Horseshoe Poker Room in Vegas, with my dad running a beginner clinic at 11. This is not the ESPN boys' club version of poker. The room is safe, surveilled, and respectful, and the dealers are briefed to teach, not judge. Your buy-in donation is also a full year of EFF membership. Send eff.org/poker to one curious friend. #DEFCON #EFF #Poker
Open quoted post
0
2
0
julian @julian@activitypub.space · Aug 03, 2026
Replying to @dansup@mastodon.social
@dansup@mastodon.social Optionally back up your database #yolo
0
0
0
Princess Nettles Succubish @tiefling@bardicperspiration.club · Jul 31, 2026
*/Three Questions/* You have one year from today before you die, forever and ever, no take-backs. There is indisputable proof that it’s true. You cannot be saved. You cannot escape your fate. But… you’ll be perfectly healthy right up until the moment you die. First Question: What are you going to do with your year? Continued at: https://princessnettles.com/index.php/2026/07/31/three-questions/ #ThoughtExperiment #ChaosMagic #Hellion #Yolo #Inspo
0
1
0
Will Brien @willb@infosec.exchange · Jul 31, 2026
ate a late breakfast and not really hungry despite it being lunch but you have to take the lunch so now shitposting on masto #itslunch #shitpost #qualitycontent #yolo
0
1
0
Stéphane Charette 🇨🇦 @charette@mstdn.ca · Jul 29, 2026
Catching up this evening on issues and PRs that have been queuing up for Darknet/YOLO. Two different users submitted nearly identical 50-line patches for a particular issue. Variable names are the same, comments are very similar, and the logic is identical. If it was a 5-line change, this wouldn't be difficult to imagine. But the patches are ~50 lines each. I assume this was created using a LLM. So much LLM-generated submissions. #Darknet #YOLO #LLM
0
0
0
Stéphane Charette 🇨🇦 @charette@mstdn.ca · Jul 28, 2026
Another LLM-generated security report e-mailed to me today concerning some code I didn't write but I maintain. Requires users to load invalid configuration files to exploit a buffer overrun. I've been given 90 days to fix the problem. Note I don't get paid to work on open-source software. And users shouldn't be loading random invalid configuration files. This is just like e-mail. When there is zero cost associated with sending out junk mail, then you guarantee that junk mail will continuously be sent out. #Darknet #YOLO #CVE
0
1
0
Alain MICHEL 🤓 @alainmi11@mamot.fr · Jul 25, 2026
Je sors de ma ligne éditoriale habituelle – une fois n'est pas coutume – mais là… Vous pensiez avoir tout vu en matière de #YOLO, de #WTF, de foutage de gueule, de cynisme, de mépris, d'indécence ? Eh bien non : ➜ https://www.huffingtonpost.fr/politique/article/c-est-serieux-ce-message-du-gouvernement-sur-l-eco-anxiete-est-etrille-sur-instagram-et-ca-en-dit-long_293867.html
25
0
41
Stéphane Charette 🇨🇦 @charette@mstdn.ca · Jul 21, 2026
Interesting topic came up today on the Darknet/YOLO discord. What can we -- or should we? -- do about how people use our open-source project? We know the U.S. military for example uses Darknet/YOLO. This was confirmed again just a few weeks ago, and was responsible for Joseph Redmon's departure many years ago. Darknet/YOLO is fully open-source. I cannot possibly monitor how people use the project, since anyone can clone it. If anything, we'd be restricted to changing the license to exclude military use, but again there is no way for me to monitor or enforce this condition. All they would have to do is clone the last revision prior to the license change. #Darknet #YOLO #OpenSource #USMilitary
0
0
0
JohnnyEnzyme @JohnnyEnzyme@piefed.social · Jul 13, 2026
Replying to @Demdaru@lemmy.world
#YOLO and YOLO SWTIA, baby! :D
1
0
0
Demdaru @Demdaru@lemmy.world · Jul 13, 2026
Replying to @JohnnyEnzyme@piefed.social
Living is a delicate art of balancing #YOLO and YOLO. Without any #YOLO it’s worthless. Without any YOLO it’s too short to enjoy. Scienc.
1
1
0
cirnon ❄ @perlenios@denden.world · May 31, 2026
#YOLO! ⭐ 🎉
5
0
4
Tomáš Odehnal @tomas@gts.odehnal.online · Jul 09, 2026
0
0
0
TwoTiredMice @TwoTiredMice@feddit.dk · Apr 27, 2026
Replying to @throws_lemy@reddthat.com
#yolo Why even give an agent unrestricted access to anything critical in the first place? What do they think they achieve that they cannot achieve otherwise?
0
0
0
Sailor Sega Saturn @sailor_sega_saturn@awful.systems · Apr 29, 2026
Replying to @BlueMonday1984@awful.systems
The future of AI in Ubuntu This post has all the usual cliches, exaggerations, lies, and unfounded optimism you’d expect in a blog post about a company forcing AI down their workers and user’s throats. I’ll try to avoid sneering at every sentence. Delegating elements of Site Reliability Engineering to an agent does not necessarily introduce an entirely new class of risk; it should inherit the constraints of existing production systems. Well-run production environments already rely on strict access controls, audit trails, and clear separation between observation and action. […] In that sense, the challenge is less about “trusting the agents”, and more about building trust in the same guardrails we already apply to any production system. This might sound good to at first, but falls apart under the slightest scrutiny. There is a reason that companies don’t open their intranets to the public despite having fine-grained access controls. Or in other words, "I’m getting a lot of questions already answered by my ‘does not necessarily introduce an entire new class of risk’ T-shirt. Imagine being able to ask your Linux machine to troubleshoot a Wi-Fi connection issue, or to stand up an open source software forge that’s pre-configured, secured, and reachable over TLS. And right after arguing that LLMs are safe if you have a perfect permissions model, now he’s proposing letting one #yolo configure a git server or something? This is the sort of thing that could easily easily lead to random security issues. I suspect that “Troubleshoot a wi-fi connection issue” will work about as well as existing network troubleshooting wizards (e.g. terribly), and that we don’t actually need to reinvent the software wizard but less deterministic.
0
6
0
Thomas Alexander Kolbe @thomas@fedi.tomkolbe.com · Jan 29, 2026
0
0
0

You've seen all posts