Posts
175Following
399Followers
315
repeated
@neil
I am constantly impressed by how good Immich is. It's not perfect - there was a bug which killed the server under certain conditions a couple of months ago, but the community quicky came up with a mitigation, and the fix came in an update a few days later.
1
1
0
repeated
Drew Mayo
drew@eigenmagic.net
So while chatting with a colleague this week about putting base64 images into email, I jokingly said
“you know though, i wonder if i can craft an image which turns into readable LLM prompts when encoded as base64 🤔”
Well. Turns out I can
1
13
0
repeated
Mojo ♻️
mojo@aus.socialCalling Wilcox’s cartoon “unacceptable” misunderstands both satire and journalism. Political cartoons are meant to be provocative, compressed and confronting. They exaggerate power relationships to expose hypocrisy and danger, not to offer polite balance.
This cartoon does exactly that. It highlights unchecked US imperial behaviour and the hollow language of “freedom and security” used by institutions like NATO while aggression proceeds regardless. Discomfort is not a flaw, it is the point.
If a cartoon criticising military power is deemed unacceptable simply because it offends those aligned with that power, then the problem is not the cartoon. It is a shrinking tolerance for dissent and satire in public debate.
Wilcox is doing a great job.
#politicalcartoons #satire #pressfreedom #imperialism #media #theage
0
3
0
repeated
Erik McClure
cloudhop@equestria.socialShow content
Bose recently did an unambiguously good thing, by open-sourcing audio hardware they were originally going to brick: https://www.theverge.com/news/858501/bose-soundtouch-smart-speakers-open-source
However, I've seen some people say "don't praise Bose for this, they didn't do this until there was backlash".
SHUT UP. Shut the FUCK UP. I'm DONE living in a society where you get dragged through hell if you make a mistake, EVEN AFTER YOU CORRECT THE MISTAKE. I'm so fucking tired of hearing stupid excuses for this kind of puritanism like "they should've known better" NOBODY KNOWS BETTER UNTIL *AFTER THEY MAKE THE MISTAKE*. THAT'S HOW LEARNING *WORKS*.
And before you say "Companies aren't your friend" PUNISHING THEM FOR FIXING THEIR MISTAKES WON'T MAKE THEM DO THE RIGHT THING EITHER. If other people, or companies, see someone get punished for both messing up AND attempting to fix the mistake, they just won't bother at all!
People HAVE to be allowed to make mistakes. They HAVE to be given a chance to improve.
0
10
0
repeated
tante
tante@tldr.nettime.orgRE: https://phpc.social/@syntaxseed/115863080846737985
Exactly. I don't care too much about the "unicorns", I want small to medium companies that do one thing really well, everyone is fairly compensated and can go home early on Friday.
0
6
1
repeated
Cassandra is only carbon now
xgranade@wandering.shopYou want a civil discussion about AI? The best time for that would have been five years ago, when this shit first started taking off. It's a fuck of a lot harder to have that discussion now, after years upon years of bad faith bullshit and denials.
So yeah. Making some noise is where we're at.
You want that to stop? Then stop making things worse, stop sabotaging what political power F/OSS has left, and come to the table.
1
5
0
repeated
Dan Fixes Coin-Ops
ifixcoinops@retro.socialFrom the mid-90's to the mid-2000's videogames would scream their own name at you in the attract mode.
RESIDENT, EVIL 😡
THE HOUSE. 😮 OF THE DEAD 💀
Sega, Rally Championship! 👋☺👋
FATAL FRAME 2, CRRRIMSONBUTTERFLY 😨
Residentevil... 😡 FOURRRR!
I need a supercut video of lots of those title screens with the games screaming their names.
Fedi, please boost, does this already exist? Are you in fact the one who made it?
I'm asking not out of a desire for amusement but to help my daughter with her enunciation. Some of these voices had to carry across an arcade with all the games set to the same volume and so had to be Very Very Clear, but also with a Certain Flair
3
7
0
repeated
Michael Salbeck
isAutonomous@karlsruhe-social.deGuten Morgen ☕
Das freie GraphenOS macht Schlagzeilen:
Die spanische Polizei nennt es "Geister-Betriebssystem". Und:
" 'Jedes Mal, wenn wir ein Pixel sehen, denken wir, es könnte ein Drogendealer sein' "
"Abhörmaßnahmen wirkungslos"
"Staatliche Malware funktioniert nicht wie geplant"
"Da die katalanische Polizei aber laut eigenen Angaben ohnehin jeden Pixel-User für einen Dealer hält, ist es wahrscheinlich günstiger, selbst gleich GrapheneOS zu installieren."
;-)
0
2
0
repeated
Natasha 🇪🇺
Natasha_Jay@tech.lgbtNames for avid readers 📚 by language -
English: Bookworm
Danish: Reading horse (Lesehest)
French: Ink drinker (Buveur d'encre)
German: Read-rat (Leseratte)
Indonesian: Book flea (Kutu buku)
Romanian: Library mouse (Șoarece de bibliotecă)
Norwegian: Reading horse (Lesehest)
Serbian/Polish: Book moth (Knjiški moljac / Mól książkowy)
Finnish: Reading maggot (Lukutoukka)
Swedish: Read-louse (Läslus)
Vietnamese: Bookwormweevil (Mọt sách)
4
9
0
repeated
Søren Have
sorenhave.dk@bsky.brid.gy“I don’t know how to stop the bully [US gov’t] from beating people [oil states like Venezuela] up for their lunch money [oil energy] —but what if lunch [energy] was free, and no one was carrying lunch money?”
Great allegory by @billmckibben.bsky.social@bsky.brid.gy
billmckibben.substack.com/p/just-possi...
Just possibly it's the oil?
0
2
0
repeated
Thorsten Leemhuis (acct. 1/4)
kernellogger@hachyderm.ioWanna know what the #Linux core developers discussed recently on this years #kernel #maintainers summit?
Then check out the great @lwn coverage from the event now freely available:
https://lwn.net/Articles/1049982/
It includes:
* Toward a policy for machine-learning tools in kernel development – https://lwn.net/Articles/1049830/
* Best practices for linux-next – https://lwn.net/Articles/1050027/
* The state of the kernel #Rust experiment (aka the session where it was decided that the experimental stamp is coming off) – https://lwn.net/Articles/1050174/
* Better development tools for the kernel – https://lwn.net/Articles/1050177/
* Development-process discussions – https://lwn.net/Articles/1050179/
1
4
1
repeated
Thorsten Leemhuis (acct. 1/4)
kernellogger@hachyderm.ioWanna know what's in store for #Linux 6.19, which is expected on February 1, 2026?
Then check out these great @lwn articles that are not freely available:
* The beginning of the 6.19 merge window – https://lwn.net/Articles/1048869/
* The rest of the 6.19 merge window – https://lwn.net/Articles/1049424/
0
3
2
Toke Høiland-Jørgensen
tokeShow content
0
0
1
Toke Høiland-Jørgensen
tokeShow content
(To be slightly pedantic, *unsigned* integer wrapping is not strictly speaking undefined behaviour in C, only signed[0], but that doesn't mean it can't lead to surprising bugs...)
[0] https://www.gnu.org/software/autoconf/manual/autoconf-2.63/html_node/Integer-Overflow-Basics.html
0
0
1
repeated
Tangential thought:
A really funny thing is almost everything good about Rust comes down to when it was written. It has excellent LLVM integration because it was written right after LLVM happened. It has a good build system because the build system was written after pip and npm. It has great libraries because all the libraries were written between 2020 and 2024 and so they're all modern. Not sure where I'm going with this but it makes me wonder how Rust will age.
"How Rust will age". Heh.
3
1
0
Show content
https://github.com/tohojo/update-dns
I spent quite a bit of extra time on polish to make the code shorter and more readable as I learned more about various Rust constructs, but I have no idea if I succeeded in getting anywhere close to 'idiomatic Rust', if such a thing exists. So comments from more experienced Rustaceans are very welcome!
8/
1
0
2
repeated
Feedtunes
feedtunes@corteximplant.comShow content
With today being Christmas, here is your annual reminder to be nice to newbies in your spaces.
There is going to be a very sudden influx of people who are just getting into the spaces you occupy because they got a gift that acts as their gateway into that activity. Maybe you're into photography and someone just bought them their first ever camera body, or you're into music and someone bought them their first guitar, or you're an audiophile and someone bought them their first really nice headphones, or you're big into TTRPGs and someone just bought them their first ever core rulebook.
Whatever the specific activity and gift, these people are going to have no idea what they're doing, they're going to ask a lot of obvious questions, they're going to make a lot of rookie mistakes, and there's going to be a lot of them.
I cannot stress this enough: BE NICE TO THEM.
Few things will ruin someone's enjoyment of something faster than trying to join its community and getting such a rude first impression that their conclusion is "People who like this are kind of assholes. I don't think I want to do this if it's going to involve getting yelled at." Craigslist and eBay and FB Marketplace will be filled with mint condition gifts being resold to attest to this in the coming months.
You were there at the very first step once. Be the person for them that you wish you had back then. (Or if you were lucky enough, the person you did have who fostered your love of it!) Make this something they'll love just as much as you do, not something they'll want to sell and get away from as soon as possible.
Be the reason this Christmas starts a lifelong passion for them, not the reason they decide to abandon something that they would've loved because people made them feel bad for needing a helping hand.
0
14
0
Show content
But once you *do* wrap your head around it, you get a kind of phase change feeling: suddenly things go from being obtuse and frustrating to being straight forward, and you really start to feel the power of the type system work in your favour. Which is very cool, and really shows the power of the language!
Oh, and the "when it compiles, it works" thing is definitely real; I spent very little time debugging weird runtime errors once things were actually compiling!
7/
2
2
5
Show content
But in Rust, you can attach the error message to the error code! With a little help from the 'anyhow' crate this becomes really easy, and you can just return errors all the way up the call stack, and if you also return them from the main function, Rust will helpfully print an error message and exit non-zero.
(For libraries you'd want typed errors, but for a CLI app like I was building, this pattern of just bubbling up the error messages works really well. The context/with_context helpers from the anyhow crate help where the default errors are not too helpful).
6/
1
1
3