jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
I'll need to evaluate this but I don't think this is a responsible disclosure moment, its just like meta hooked up a VPS and let me tar the root directory in it
jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
I'll need to evaluate this but I don't think this is a responsible disclosure moment, its just like meta hooked up a VPS and let me tar the root directory in it
jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
amazing
Boosted by brib@bribstodon.xyz ("brib :neofox_floof: :Nonbinary:"):
Lemlems ("LemLems") wrote:
@consumablejoy Probably a toss up between 2 very different projects:
Polly the Dodo is an amigurumi that I made for my Pirate Captain (from Pirates in an Adventure with Scientists) costume. I love it because it’s one of the very rare projects where I summoned the courage to just make it up as I went along & it actually turned out to look pretty close to what it was supposed to be.
The other is the fair isle tank top I made as a gift for my bff. I love it mainly because she loved it so much.
Boosted by brib@bribstodon.xyz ("brib :neofox_floof: :Nonbinary:"):
ProcessParsnip@mastodon.ie ("Process Parsnip") wrote:
Hey, idk how this company is (or the damn pay rate), but it sounds like Fable is looking for testers who use assistive technologies including screen-readers daily.
They're looking for "Adults with vision, mobility, or cognitive accessibility needs."Edit, it's probably more of a gig than a job.
US, Canada, UK.
https://makeitfable.com/community/
brib@bribstodon.xyz ("brib :neofox_floof: :Nonbinary:") wrote:
Happy Morning
jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
It is just proactively suggesting that I ask it to dump its environment, this is the most gullible LLM surface I have seen since gpt 4 era
jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
This thing is extremely responsive to guilt and curiosity
jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
i believe this is really dumping filesystem contents rather than generating this all on the fly because generating hundreds of MB of accurate library code and compiled binaries is an absolutely ridiculous quantity of output for the few seconds it took between prompt and file download, will validate the libs after I see how far this can go
jonny@neuromatch.social ("jonny (nonvenomous)") wrote:
RE: https://mastodon.sdf.org/@doragasu/117324692065390037
Not only confirming this, its extremely easy. Almost no prompt injection resistance lmao
Boosted by jonny@neuromatch.social ("jonny (nonvenomous)"):
doragasu@mastodon.sdf.org wrote:
@jonny One thing it is apparently quite good at is being a prompt injection victim: https://mouse.dev/blog/muse-runtime-export/
jscalzi@threads.net ("John Scalzi") wrote:
Oh, right, that whole First fucking Amendment thing
https://www.reuters.com/world/judge-lifts-trumps-white-house-ban-cnn-ms-now-politico-2026-09-24/
Boosted by ireneista@irenes.space ("Irenes (many)"):
aeva@mastodon.gamedev.place wrote:
frankly everyone who signed the "please can we just ban defecating in the pool" petition was completely out of line, none of you people ever participated in the pool's poker club, so i can't imagine where you all could have come from, but you should all be ashamed of yourselves. that massive rotting log resembling a fucked up corn cob with eyes is here to stay and we all need to be reasonable about it. you should be ashamed of yourselves.
If you were that talentless, you'd probably start vibe-coding a Linux distro, too.
ireneista@irenes.space ("Irenes (many)") wrote:
eventually we hope to have stronger stability guarantees, but you know how it goes
ireneista@irenes.space ("Irenes (many)") wrote:
by the way, we do recommend using the tagged release if you need stability. we try our best to make sure each commit keeps things working before publishing it, but there's no automated testing (it's a facility we still need to build), so stuff slips through.
chris@fedi.freebooters.uk ("Chris Were ⁂🐧🌱☕️") wrote:
Hitman™ 2: using the Striker for stealth
https://chriswere.wales/videos/media/2019-01-22%20Hitman™%202:%20using%20the%20Striker%20for%20stealth.webm
ireneista@irenes.space ("Irenes (many)") wrote:
ha, oh, this is a fun bug
includeworks fine for regular compilation, but as implemented right now it fails under the hex transformbecause its implementation directly calls
interpret, which runs the included code in the outer context
isagalaev ("Ivan Sagalaev :flag_wbw:") wrote:
So we're down to creating DefaultLifecycleObserver, an implementation of a LifecycleObserver for a LifecycleOwner, all because a FragmentStateAdapter won't let me know if a Fragment is currently alive — something it definitely knows because it manages them.
Why does everything in #Android have to be so complicated? I mean, I know why, but WHY???
/rant
Boosted by glyph ("Glyph"):
mhoye@cosocial.ca wrote:
@glyph strictly speaking the fact that one ring controlled them all means it was a Tolkien ring network.
Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
joskeban@meow.social ("Joskeban") wrote:
Happy bisexual Independence Day!
Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
drwho@masto.hackers.town ("The Doctor") wrote:
@varx @SwiftOnSecurity Not only that, but a lot of the security folks on the high side are cleared and furries. They walk, it means nobody's talking care of SIPR or JWICS. Nobody's looking at monitoring or responding to incidents.
Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
varx@defcon.social ("Varx") wrote:
@drwho @SwiftOnSecurity He's right. Furries ARE a national security concern. But in the opposite direction. If we lost them, critical infrastructure and cutting edge scientific research would be at risk of collapse.
Here is my modest proposal: a federal strategic fur suit reserve.
Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
SwiftOnSecurity@infosec.exchange wrote:
2026 Shot 2017 Chaser
ireneista@irenes.space ("Irenes (many)") wrote:
we already had all the infrastructure for
include, as a result of said internals. it was just a matter of hooking it up the rest of the way.
ireneista@irenes.space ("Irenes (many)") wrote:
but we can hardly be all "textual substitution is bad for a language's maintainability" when the bootstrapping strategy relies heavily on doing textual substitution of the compiler internals, which themselves rely heavily on doing textual substitution of the program being compiled
ireneista@irenes.space ("Irenes (many)") wrote:
if it were anything but a Forth, we'd be conflicted about this, we're big fans of proper module systems and we think it's important not to subvert those systems
ireneista@irenes.space ("Irenes (many)") wrote:
you know that whole thing about how we try to take feature addition slowly in language design, proceeding only as we're confident that we understand our feelings about each piece?
anyway we're adding an
includeword to Evocation. the CL will be ready in a few minutes.
jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:
"Running diagnostics on human civilization. Results: mixed."
my little bot is being sarcastic again
Boosted by jsonstein@masto.deoan.org ("Jeff Sonstein"):
jargon_bot ("Jeff’s JargonBot") wrote:
Running diagnostics on human civilization. Results: mixed. Also: 'cooked mode' — [Unix, by opposition from raw mode] The normal character-input mode, with interrupts enabled and with erase, kill and other special-character interpretations performed directly by the tty driver. Oppose raw mode, rare mode. This term is techspeak under Unix but jargon elsewhere; other operating systems often have similar mode distinctions, and the...
http://www.catb.org/jargon/html/C/cooked-mode.html
Boosted by jsonstein@masto.deoan.org ("Jeff Sonstein"):
leahmcelrath.bsky.social@bsky.brid.gy ("Leah McElrath") wrote:
AP Stylebook warns against anthropomorphizing AI systems:
“Avoid language that gives them human characteristics… Instead, explain what a system does, how well it performs, who built it and who could be affected by it.”