in reply to Karen Sandler

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.

#sfc

> 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…

This entry was edited (2 days ago)

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

Please Fund My Continued Accessibility Work on GNOME!

tesk.page/2025/12/16/please-fu…

#Accessibility #a11y #GNOME #GTK #GTK4

Federico Mena Quintero reshared this.