It's funny how when there are as many cops as protesters, everything is violence, tear gas, and billy clubs. But when there's a thousand times more protesters than cops, nothing violent happens at all.
Hm.
clew
#Soil, ecology, low-input #MarketGardening, women's history, material history, math, programming, literature of the long nineteenth, #waltz, #polka, leavened bread. Mostly around the Salish Sea.
Moved over from octodon.social as that delightful venue closed.
Profile image looks grayscale but is a color photo; a gull on a gray day here is just that gray. Header, for contrast, is an edible-flower harvest, punnets of brilliant oranges and purply-blues and pinks, on a scrubbed washpack table.
clew boosted:
That's a great idea! A separate listing site like that sounds like a good idea for more populated areas
Where I live (not so many people), we have a social and mutual aid group for covid conscious folks. We sometimes help each other with the home projects, or we recommend workers who we know are willing to mask
We also do hikes and seed swaps and loan testing equipment and post local events that are masking, and politely make official requests for them to have masking hours (surprisingly, 100% successful so far!)
We do a little bit of everything!
clew boosted:
Just thinking about better ways to penalize corporations that break the law.
Fines are trivial and never keep pace with reality. Instead, what if companies had to give back a chunk of shares to the government? Issuing new shares that dilute existing shareholder value, and making the govt part owners. Effectively, nationalize the company in degrees with every breach of trust.
Fines are trivial and never keep pace with reality. Instead, what if companies had to give back a chunk of shares to the government? Issuing new shares that dilute existing shareholder value, and making the govt part owners. Effectively, nationalize the company in degrees with every breach of trust.
clew boosted:
Angel City giving these out at the game tonight - as far as I know the other LA sports teams have all been silent.
clew boosted:
Give me recommendations: what are your favorite trashy sapphic romance stories available as an ebook?
I donât want to lug a bunch of books around on my upcoming trip, so Iâm looking for things I can read on my kobo. I would really like some that are pulp novel style - easy reading, scandalous, and gay, but I will also be open to just hot or silly and sweet.
clew boosted:
For No Kings Day, I've chosen to walk with the military burial flag of my father-in-law, who was a WWII veteran. I was there as upon this flag, William Edward Stiles Jr. received his final salute: three volleys from the rifles of the honor guard before it was folded and presented to my mother-in-law by two Navy men. Later, at his memorial, I was astonished to discover that a white man of his era had so many Black friends.
You see my father-in-law's fight against injustice did not end when he returned from the second World War. His fight continued in the civil rights movement negotiating for teachers unions in the shadow of Brown v. Board of Education America. Out of prejudice or fear of the Klu Klux Klan, few white people were willing to do what he did because it meant also representing Black teachers unions.
𧾠1/2
clew boosted:
clew boosted:
The thing that really bothers me is how it wasn't the inhumanity but rather the threat to our supply of cheap goods made possible by labor exploitation that got enough people angry enough to make Trump blink about the ICE raids.
clew boosted:
A couple people responded to my earlier post about the shoddy WSJ article (https://hachyderm.io/@molly0xfff/114683662588184161) to say âwell itâs true that Democrats arenât supporting the protests!â
At my best count, 75 elected Democrats (Congresspeople, governors) attended protests today. Another 27 encouraged people to go.
Thatâs just looking at todayâs protests, not Democrats talking about or attending protests more generally. It also doesnât count the many more state or local officials who showed up, candidates, etc.
clew boosted:
We are home. We are safe. Houston turnout was MASSIVE. Minimal security issues. Incredible food drive success!!
Pathetic counterprotest effort of 5. *womp-womp*
Our counters are still doing their thing, but the latest estimate is 26k-30k!!!!!
Staggering turnout. WE ARE IN HOUSTON, TEXAS, PEOPLE.
The People are Piiiiiiiisssssssssssed Off in the best way.
clew boosted:
Cool #Worcester Public Library (folding!) cargo trike (by Icicle) at #Boston Pride. They were distributing banned books but ran out fast in the big crowd! The underside of the lid is a blackboard!
clew boosted:
@xankarn We had 3 people total in our protest. I bet 300 people saw our messaging, and about half of them gave us thumbs up, honked and waved, or shouted encouragement. Only 5 people openly supported Trump, and I think I changed one of their minds when he came back and parked to debate me. This is in a small town in a red state in the deep south. We made a difference today, and it felt awesome! I hope others take encouragement from this. If you're sitting on the fence, go for it! SHOW UP! Even that tiny contribution can have a huge impact. You encourage and draw attention to those who are more vocal with your mere presence. This was my first protest ever, and I am so glad I went!
clew boosted:
Come see a copy in person in my current mini-exhibition on the 300th anniversary of the punched card.
https://mastodon.social/@publicdomainrev/114683436338702150
clew boosted:
Stood on a sidewalk with 4400 (!) people in a city of 8000 (not counting the surrounding rural area).
Extremely well organized event with very positive response from passing traffic.
*Correction: The count now reported by the local Indivisible web site is 2600, not 4400. The larger number was being passed through the crowd and may have been an early estimate or garbled. Still, a good turnout.
clew boosted:
Q: how do you think the unthinkable?
A: with an itheberg.
You're welcome, Fediverse.
clew boosted:
Wanted - A Computing Engineer at the start of your career, with a strong foundation in Linux and a desire to work on critical computing services for the research community? Join the CERN Linux Team to help operate, evolve and support Linux-based services used by thousands of scientists across the organisation and worldwide.
https://www.smartrecruiters.com/CERN/744000064680069-linux-engineer-it-cd-cli-2025-109-grae-
#opensourcejobs #cern #linuxjob #AlmaLinux #rhel #debian #rpm
clew boosted:
And once you cancel your NYT Games subscription, check out https://lexfriedman.com/games.
Disclaimer: Lex is an almost unbearably good person. He deserves your support.
clew boosted:
Teen Vogue continues to be a goddamn treasure and I will fight anyone who says otherwise.
https://www.teenvogue.com/story/how-to-be-an-activist-when-youre-unable-to-attend-protests
clew boosted:
Been working on https://github.com/oir/startle, which lets you quickly turn python functions or (data)classes into CLIs. If you like Fire, Typer, or HfArgumentParser but interested to check out an alternative, take a look! #python #opensource
clew boosted:
@shortridge While working tech support, I got a call on a Monday. Some VPNs which had been working on Friday were no longer working. After a little digging, we found the negotiation was failing due to a certificate validation failure.
The certificate validation was failing because the system couldnât check the certificate revocation list (CRL).
The system couldnât check the CRL because it was too big. The software doing the validation only allocated 512kB to store the CRL, and it was bigger than that. This is from a private certificate authority, though, and 512kB is a *LOT* of revoked certificates. Shouldnât be possible for this environment to hit within a human lifespan.
Turns out the CRL was nearly a megabyte! What gives? We check the certificate authority, and itâs revoking and reissuing every single certificate it has signed once per second.
The revocations say all the certificates (including the certificate authorityâs) are expired. We check the expiration date of the certificate authority, and itâs set to some time in 1910. What? It was around here I started to suspect what had happened.
The certificate authority isnât valid before some time in 2037. It was waking up every second, seeing the current date was after the expiration date and reissuing everything. But time is linear, so it doesnât make sense to reissue an expired certificate with an earlier not-valid-before date, so it reissued all the certs with the same dates and went to sleep. One second later, it woke up and did the whole process over again. But why the clearly invalid dates on the CA?
The CA operation log was packed with revocations and reissues, but I eventually found the reissues which changed the validity dates of the CAâs certificate. Sure enough, it reissued itself in 2037 and the expiration date was set to 2037 plus ten years, which fell victim to the 2038 limitation. But itâs not 2037, so why did the system think it was?
The OS running the CA was set to sync with NTP every 120 seconds, and it used a really bad NTP client which blindly set the time to whatever the NTP server gave it. No sanity checking, no drifting. Just get the time, set the time. OS logs showed most of the time, the clock adjustment was a fraction of a second. Then some time on Saturday, there was an adjustment of tens of thousands of seconds forward. The next adjustment was hundreds of thousands of seconds forward. Tens of millions of seconds forward. Eventually it hit billions of seconds backwards, taking the system clock back to 1904 or so. The NTP server was racing forward through the 32-bit timestamp space.
At some point, the NTP server handed out a date in 2037 which was after the CAâs expiration. It reissued itself as I described above, and a date math bug resulted in a cert which expired before it was valid. So now we have an explanation for the CRL being so huge. On to the NTP server!
Turns out they had an NTP âapplianceâ with a radio clock (i.e, a CDMA radio, GPS receiver, etc.). Whoever built it had done so in a really questionable way. It seems it had a faulty internal clock which was very fast. If it lost upstream time for a while, then reacquired it after the internal clock had accumulated a whole extra second, the server didnât let itself step backwards or extend the duration of a second. The math it used to correct its internal clock somehow resulted in dramatically shortening the duration of a second until it wrapped in 2038 and eventually ended up at the correct time.
Ultimately found three issues:
⢠An OS with an overly-simplistic NTP client
⢠A certificate authority with a bad date math system
⢠An NTP server with design issues and bad hardware
Edit: The popularity of this story has me thinking about it some more.
The 2038 problem happens because when the first bit of a 32-bit value is 1 and you use it as a signed integer, itâs interpreted as a negative number in 2âs complement representation. But C has no protection from treating the same value as signed in some contexts and unsigned in others. If you start with a signed 32-bit integer with the value -1, it is represented in memory as 0xFFFFFFFF. If you then use it as an unsigned integer, it becomes the value 4,294,967,296.
I bet the NTP box subtracted the internal clockâs seconds from the radio clockâs seconds as signed integers (getting -1 seconds), then treated it as an unsigned integer when figuring out how to adjust the tick rate. It suddenly thought the clock was four billion seconds behind, so it really has to sprint forward to catch up!
In my experience, the most baffling behavior is almost always caused by very small mistakes. This small mistake would explain the behavior.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst