#kwanzaaThoughts

Day 5 - Nia (Purpose)

Its been 400 years since the start of the slave trade so people have had a very long time to vilify other people because of their skin color. Antiblackness has spread across the globe, and dark-skinned people are judged by others as soon as they are seen.
Changing that will take a long time.
I've been thinking of writing stories where that isn't the case. #Solarpunk stories. Finding a purpose can be something very small, but every little bit helps.

This entry was edited (1 day ago)
in reply to Rozzychan

#KwanzaaThoughts

Day 6 - Kuumba (Creativity)

New Years Eve is a time to party and forget your troubles before the start of the new year. In Kwanzaa, it is time for Karamu Ya Imani (Feast of Faith). The value, Kuumba, should be demonstrated by crafts, music, and fun with the purpose to leave our community more beautiful and beneficial than we inherited it.
In the spirit of Kuumba, for Today's affirmation I will tell a Nancy story. Special thanks to @FreakyFwoof who contributed music.

I did something this year that I would like to recommend to everyone for the new year. Call it a Fedi Resolution if you like.

Find someone whose work you like and become their champion. Not in a creepy way, but make a point of boosting them every time they post (or post about) their work. Recommend it to people you think would like it.

The Fediverse works if it works for the people who use it. If you see someone who does something you like, lend your voice to help make it work for them.

This entry was edited (18 hours ago)

That gpgfail comment about how they could have tanked bitcoin with a Twitter post faking a Satoshi signed message was a bit too optimistic. You're not going to cause panic unless you can move funds from his wallets. The skeptics would have quickly tried to verify with other PGP implementations and discovered the ruse

Honduras pol, elections, U.S. imperialism

Sensitive content

For a while, in my life, even numbered years were less preferable than odd numbered ones in that less bad stuff tended to happen in my life during odd numbered years. At some point, this changed. Now, they all just seem to suck equally, with a couple of exceptions. This year and 2019, so far, have been the two top worst for me in general terms, with 2019 edging out in a few fundamental respects.

I don't even bother being hopeful anymore. Come what may, and all that.

This entry was edited (12 hours ago)
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

reshared this

> 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)
in reply to Chuck Darwin

> 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

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.

in reply to Toni Barth

I played quite a bit Slay The Spire this year too, since I was able to pick up the SayTheSpire mod and add support for Downfall and fix some other things as well. The original dev also merged my changes, and its great to give something back to the community. I also played a bit Doki Doki Literature Club and Sequence Storm this year, as well as Final Fantasy VI and IX, which i'm also looking forward to playing more in the future. 15/X

Numbers and algorithms are so messed up for my brain.
I have a YouTube channel with 97K subscribers and if I publish a video that does below 1K it feels like a failure, even tho I get dozens of positive comments, I'm proud of the video, and I had fun during the time I spent making it.
Fuck numbers and algorithms, dude.
I need to go back to how I was pre-internet, just making things for my own pleasure, and being happy if only a handful of people like it
in reply to Castopod

The site pulls the data from the apps JSON in Podcast Index: github.com/Podcastindex-org/we…

It's weird, I know. When I can finish populating canipodcast.com's data, I'll switch to it as a data source.

Welp ... I was just informed through a Slack DM that I will no longer be working at the place I'm working at in two weeks' time. That is, evidently, how we handle that now. Not entirely unexpected as the writing on the wall was evident, but still not loving that approach for reasons I haven't quite worked out yet.
If anyone needs help with their #accessibility from someone with both native #screenReader experience and a coding background, keep me in mind I guess :)
Located in the eastern Netherlands, primarily interested in remote opportunities.
#fediHired #layoffs
This entry was edited (6 hours ago)

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