R@m.pupu.moe Possible #fediblock
And while we're pausing from questions, I'd be a bad Executive Director if I didn't mention that we still have $92,680 left in our match challenge! Until 1/15 (or until we've reached the $251,939 challenge amount), donations count twice.
I've been inundated with emails today, saying that there are only hours left to donate in 2025! I won't be so theatrical, but I will say it's a very good time to donate to #SFC. We'll use the funds as wisely as possible towards our mission of software freedom.
> Even it were possible, changing from a one-hour to a four-hour confirmation would have significant negative impacts on the Bitcoin ecosystem.
how? What negative impact? The Bitcoin blockchain is a payment rails, not a trading platform. On-chain trading does not have to happen; only final settlement. Layers have been built on top of it for a long time now because even 1 hour sucks for some use cases.
It's like pretending that when you trade stocks they're in your name. No they're not, unless you purchase them and they're direct registered. When you're on eTrade, Vanguard, etc trading stocks they're just changing values in a database inside that company. If you want to direct register your MSFT stocks that you're holding on eTrade it's going to take several days (near a week last I saw) for that to "settle" too.
Billionaires with $1 salaries
– and other legal tax dodges the ultrawealthy use to keep their riches
Billionaires can enjoy growing wealth entirely free of income tax and reporting
Mark Zuckerberg was the lowest-paid employee at Meta in 2024,
and he made US$1.
But he is not the only very rich person who has collected $1 for a year’s work.
Why would incredibly rich CEOs make only $1 a year when they could pay themselves millions?
The reason is taxes.
Income from work is the most heavily taxed type of income,
as it is subject to both income and payroll taxes.
A self-employed person who makes a modest income of $60,000 will pay over $13,000 of it in payroll and income taxes.
Meanwhile, high-income earners who earn a $400,000 salary can pay about 30% of their income in payroll and income taxes.
So the first step in avoiding taxes is avoiding salary,
and that is what our richest Americans often do.
salon.com/2025/12/28/billionai…
Billionaires can enjoy growing wealth entirely free of income tax and reporting.Ray Madoff (Salon.com)
> A self-employed person who makes a modest income of $60,000 will pay over $13,000 of it in payroll and income taxes.
oh this is easy, register a single-member LLC and pay yourself a salary of only $20,000. You only do the full payroll taxes on that $20k, and the remaining $40k you can take as equity disbursements
if you get a good accountant they'll coach you through this
Sensitive content
apparently someone or something is trying to screw with my server
Limiting tcp reset response from 521 to 213 packets/sec
Limiting tcp reset response from 482 to 215 packets/sec
Limiting tcp reset response from 1158 to 190 packets/sec
Limiting tcp reset response from 1354 to 184 packets/sec
Limiting tcp reset response from 664 to 213 packets/sec
Limiting tcp reset response from 890 to 210 packets/sec
Limiting tcp reset response from 643 to 213 packets/sec
Limiting tcp reset response from 278 to 195 packets/sec
Limiting tcp reset response from 501 to 204 packets/sec
Limiting tcp reset response from 659 to 212 packets/sec
Limiting tcp reset response from 1281 to 214 packets/sec
Limiting tcp reset response from 641 to 209 packets/sec
Limiting tcp reset response from 349 to 213 packets/sec
Limiting tcp reset response from 692 to 215 packets/sec
Limiting tcp reset response from 1597 to 189 packets/sec
Limiting tcp reset response from 1370 to 208 packets/sec
Limiting tcp reset response from 610 to 210 packets/sec
Limiting tcp reset response from 426 to 214 packets/sec
Limiting tcp reset response from 1011 to 209 packets/sec
Limiting tcp reset response from 609 to 207 packets/sec
Limiting tcp reset response from 354 to 200 packets/sec
Limiting tcp reset response from 228 to 216 packets/sec
Limiting tcp reset response from 353 to 203 packets/sec
Limiting tcp reset response from 1277 to 199 packets/sec
Limiting tcp reset response from 1311 to 205 packets/sec
Limiting tcp reset response from 799 to 210 packets/sec
Limiting tcp reset response from 423 to 203 packets/sec
Limiting tcp reset response from 392 to 206 packets/sec
Limiting tcp reset response from 334 to 198 packets/sec
Limiting tcp reset response from 678 to 185 packets/sec
Limiting tcp reset response from 2004 to 185 packets/sec
Limiting tcp reset response from 1069 to 214 packets/sec
Limiting tcp reset response from 1201 to 187 packets/sec
Limiting tcp reset response from 1124 to 207 packets/sec
Limiting tcp reset response from 275 to 195 packets/sec
Limiting tcp reset response from 299 to 214 packets/sec
Limiting tcp reset response from 793 to 188 packets/sec
Limiting tcp reset response from 1841 to 187 packets/sec
Limiting tcp reset response from 1647 to 202 packets/sec
Limiting tcp reset response from 818 to 197 packets/sec
Limiting tcp reset response from 1034 to 204 packets/sec
Limiting tcp reset response from 885 to 209 packets/sec
Limiting tcp reset response from 354 to 184 packets/sec
Limiting tcp reset response from 721 to 210 packets/sec
Limiting tcp reset response from 1479 to 184 packets/sec
Limiting tcp reset response from 560 to 194 packets/sec
Limiting tcp reset response from 541 to 190 packets/sec
Limiting tcp reset response from 762 to 186 packets/sec
Limiting tcp reset response from 335 to 204 packets/sec
Limiting tcp reset response from 448 to 186 packets/sec
Limiting tcp reset response from 686 to 196 packets/sec
Limiting tcp reset response from 588 to 212 packets/sec
Limiting tcp reset response from 1136 to 208 packets/sec
Limiting tcp reset response from 1066 to 190 packets/sec
Limiting tcp reset response from 353 to 206 packets/sec
Limiting tcp reset response from 502 to 211 packets/sec
Limiting tcp reset response from 416 to 190 packets/sec
Limiting tcp reset response from 614 to 214 packets/sec
Limiting tcp reset response from 912 to 200 packets/sec
Limiting tcp reset response from 968 to 186 packets/sec
Limiting tcp reset response from 1153 to 207 packets/sec
Limiting tcp reset response from 1312 to 191 packets/sec
Limiting tcp reset response from 484 to 196 packets/sec
Limiting tcp reset response from 605 to 186 packets/sec
Limiting tcp reset response from 583 to 215 packets/sec
Limiting tcp reset response from 258 to 214 packets/sec
In Norway, they’re building a new stave church, using only Viking-age tools and techniques. 1,000 people are involved, and it is expected to be complete by 2030.
visitnorway.com/typically-norw…
… built with a lot of passion, using Viking techniques!www.visitnorway.com
Please Fund My Continued Accessibility Work on GNOME!
tesk.page/2025/12/16/please-fu…
#Accessibility #a11y #GNOME #GTK #GTK4
I have been under distress lately due to personal circumstances that are outside my control. I cannot find a permanent job that allows me to function, I am not eligible for government benefits, my grant proposals to work on free and open-source proje…TheEvilSkeleton
Federico Mena Quintero reshared this.
Sensitive content
Are you a #GNOME volunteer? Tell us your 2025 highlights!
Do you know that some companies will match your volunteer hours with GNOME providing $10-$25 per hour to the GNOME Foundation? Some can offer up to $15k/year.
If you have volunteered for GNOME, this is a great way to help #GNOME additionally through your efforts.
Help us sustainably fund GNOME for the future!
"Music lives on TDK"
Kids, you wouldn't understand.
Yeah.
I knew the edits were recorded/visible, I just found it interesting to see one played back "live". Up until now, I've only seen it update slowly like replies etc come in.
I'd be interesting in knowing how it happens (does the client stay connected to my server and the server offers up edited updates when such a connection is maintained?).
reshared this
It's both sad and refreshing to see that "made by people" is now considered a wonderful and welcome surprise.
Public Rejoices as Porsche Releases Beautiful Ad Not Made Using AI share.google/RVC3BhA404ciJWZnR
Porsche made the incredibly bold decision of releasing an ad that seemingly isn't made with AI, and the internet rejoiced.Frank Landymore (Futurism)
to whoever stole my Zoom F4 recorder from #39c3 from the toilet rave / Maskenball: please, at least, give me the storage cards inside. they contain very valuable recordings. please.
contact me at sdcards@nik.mx.

Okay, I am thinking about doing Jamuary this year, but maybe with a twist? Would any of you mutuals be interested in creating a prompt for me?
This could be anything, with the stipulation YOU create it. A text prompt of any kind; a visual score; a drawing, painting or photograph; a set of instructions such as tempo, key, timbres, etc; a brief sound recording for me to react to or even incorporate; a mood board or collage; etc/et al.
So, does that interest anyone?
What is your #GNOME highlight from 2025?
#FOSS #LInux #Opensource
The migration to the strparse API introduced regressions in Digest authentication parsing where Optional Whitespace (OWS) after commas was not skipped, and escaped quotes in values were not correct...GitHub
We should talk about Werner Koch's response gpg.fail on the oss-security mailing list.
openwall.com/lists/oss-securit…
Yes, and actually the only serious bug from their list.
Koch either didn't watch the talk, he is in such defense of his own ego that he can't see how serious the bugs were, or he's tacitly admitting that PGP is not a serious recommendation.
Can you distinguish between these three explanations?
Could it be all of them are true?
ImpactWhile this may allow remote code execution (RCE), it definitively causes memory corruption.
Good research.
I think this sarcastic quip is what reveals Werner Koch's opinion about the security researchers and their work.
The rest of his email is measured (and partly responding to other mailing list participants rather than the disclosure directly).
ללהיטים הגדולים של כוורת להאזנה ברצף:https://www.youtube.com/watch?v=PHxYIcFyBVwמילים: דני סנדרסוןלחן: יצחק קלפטרהיא כל כך יפה זה צובט בלב שלך, אך בכאב עצום....YouTube
feld likes this.
Slop drives me crazy and it feels like 95+% of bug reports, but man, AI code analysis is getting really good. There are users out there reporting bugs that don't know ANYTHING about our stack, but are great AI drivers and producing some high quality issue reports.
This person (linked below) was experiencing Ghostty crashes and took it upon themselves to use AI to write a python script that can decode our crash files, match them up with our dsym files, and analyze the codebase for attempting to find the root cause, and extracted that into an Agent Skill.
They then came into Discord, warned us they don't know Zig at all, don't know macOS dev at all, don't know terminals at all, and that they used AI, but that they thought critically about the issues and believed they were real and asked if we'd accept them. I took a look at one, was impressed, and said send them all.
This fixed 4 real crashing cases that I was able to manually verify and write a fix for from someone who -- on paper -- had no fucking clue what they were talking about. And yet, they drove an AI with expert skill.
I want to call out that in addition to driving AI with expert skill, they navigated the terrain with expert skill as well. They didn't just toss slop up on our repo. They came to Discord as a human, reached out as a human, and talked to other humans about what they've done. They were careful and thoughtful about the process.
People like this give me hope for what is possible. But it really, really depends on high quality people like this. Most today -- to continue the analogy -- are unfortunately driving like a teenager who has only driven toy go-karts.
Examples: github.com/ghostty-org/ghostty…
Explore the GitHub Discussions forum for ghostty-org ghostty. Discuss code, ask questions & collaborate with the developer community.GitHub
reshared this
This is the first open source story I am hearing w/ a positive results from someone using LLMs to generate bug reports.
We have been struggling in LLVM w/ low quality LLM submissions. Curl completely banned them b/c it was so bad: mastodon.social/@LukaszOlejnik…
My biggest issue is how ridiculously verbose LLM submissions can be. Even ones that don't have obvious errors are soo long that if every submission was that long it would have significant impact on throughput.
Clearly someone using it thoughtfully can do excellent work but I am seeing very little evidence this is happening much.
Liam Erven
in reply to David Goldfield • • •Martin
in reply to Liam Erven • • •Liam Erven
in reply to Martin • • •Martin
in reply to Liam Erven • • •Reed Lindwurm
in reply to Liam Erven • • •