The first Dahlia of the year!
#Gardening #Bloomscrolling #Dahlia
I used to be a C++ programmer like you, then I took an -> in the nullptr.
@meta 's human.
Long-time #SRE and #Infosec person and #WoSo fan. New father. I've already had my 15 minutes of internet fame discovering the first published remote root vulnerability in Mac OS X.
The thoughts here are mine, not my employer's. My thoughts and theirs are increasingly divergent.
The first Dahlia of the year!
#Gardening #Bloomscrolling #Dahlia
@chetwisniewski I've particularly taking a shining to Guerilla Grandma
Rainy day rose 🌹
Enshittification comes for open source:
Slack is kicking two large open source groups, Cloud Native Computing Foundation and Kubernetes, off of their donated enterprise tier, giving them one week notice to migrate multiple years of data to a new platform before it's all deleted: https://www.cncf.io/blog/2025/06/16/cncf-slack-workspace-changes-coming-on-friday-june-20/
Instead of learning from this experience and not trusting the good will of profit-motivated closed source companies, it looks like both projects will be moving to ... Discord. Because "people know it." Will we never learn?
(Dropped Cory because he's probably getting tons of spam from this. Sorry!)
Washington joins NY, CA, MN, OR, and CO in passing Right to Repair. Together, these six states represent nearly a quarter of the US population.
That means manufacturers can’t treat this like a fringe issue anymore. Repair access is now a national standard.
@nuintari The data structures used in servers for bytes of things to serve are frequently many orders of magnitude larger for... reasons.
@nuintari 13 * 20 = 260? Did I miss something in the original post?
And yes, I'm sure the 39M resident is something liked fixed_cost + n * record_cost + m * query_cost + logging_and_other_variable_stuff. How those numbers work out is the interesting thing I'm curious about.
Time for a regular reminder: you don’t write code that’s portable across architectures and operating systems because you necessarily care about those platforms, you write it to minimise your accidental dependencies on implementation details. The platforms that you care about will change over time. Either you will care about different ones or the ones that you care about evolve. If you don’t build good abstractions in from the start, retrofitting them later is much harder.
@nuintari
260 records = 39 MB. I wonder how that scales with more or less records or requests. Now I'm curious where the memory is going.
Okay, it's time for the big #ntp and #ptp wrap-up post. My week-long timing project spiraled out of control and turned into a two month monster, complete with 7 (ish?) GPS timing devices, 14 different test NICs, and a dozen different test systems.
What'd I learn along the way? See https://scottstuff.net/posts/2025/06/10/timing-conclusions/ for the full list (and links to measurements and experimental results), but the top few are:
1. It's *absolutely* possible to get single-digit nanosecond time syncing with NTP between a pair of Linux systems with Chrony in a carefully-constructed test environment. Outside of a lab, 100-500 ns is probably more reasonable with NTP on a real network, and even that requires carefully selected NICs. But single-digit nanoseconds *are* possible. NTP isn't just for millisecond-scale time syncing.
2. Generally, PTP on the same hardware shows similar performance to NTP in a lab setting, with a bit less jitter. I'd expect it to scale *much* better in a real network, though. However, PTP mostly requires higher-end hardware (especially switches) and a bit more engineering work. Plus many older NICs just aren't very good at PTP (especially ConnectX-3s).
3. Intel's NICs, *especially* the E810 and to a lesser extent the i210 are very good at time accuracy. Unfortunately their X710 isn't as good, and the i226 is mixed. Mellanox is less accurate in my tests, with 200ns of skew, but still far better than Realtek and other consumer NICs.
4. GPS receivers aren't really *that* accurate. Even good receivers "wander" around 5-30 ns from second to second.
5. Antennas are critical. The cheap, flat window ones aren't a good choice for timing work. (Also, they're not actually supposed to be used in windows, they generally want a ground plane).
6. Your network probably has more paths with asymmetrical timing in it than you'd have expected. ECMP, LACP, and 2.5G/5G/10Gbase-T probably all negatively impact your ability to get extremely accurate time.
Anyway, it's been a fun journey. I had a good #time.
texted from a friend, authorship unknown
A pileated woodpecker friend came to visit.
@howler0502 It's a positive change that the #USWNT is now giving the depth in the roster the chance to play and gain experience.
@silvermoon82 https://www.home-assistant.io/installation/linux#install-home-assistant-container
That said, they are steering people harder into the HAOS installation these days.
fun facts:
mbas don't increase profit or returns, they just cut wages [1]
in fact, ceos tend to be more self serving than other people [2], and risk taking ceos correlates to childhood exposure to pollution [3]
'superfund ceos' tend to get promoted [4], even though unionised places perform better in stock market [5]
sources:
[1] https://www.nber.org/system/files/working_papers/w29874/w29874.pdf
[2] https://hbr.org/2016/12/mbas-are-more-self-serving-than-other-ceos
[3] https://www.iimb.ac.in/sites/default/files/inline-files/hazed-confused-prenatal-ceo-risk-taking.pdf
[4] https://papers.ssrn.com/sol3/papers.cfm?abstract_id=5270031
[5] https://www.sciencedirect.com/science/article/abs/pii/S0929119921001127
I am somewhat torn on bug-bounties, but we'll leave that for another day.
The combination of bug-bounties and AI generates a "make-money-fast" economic opportunity, at the cost of FOSS maintainers.
https://www.theregister.com/2025/05/07/curl_ai_bug_reports/
For the record: #VarnishCache does not pay out bug-bounties (even if we wanted to, we have no money) and this shit-show will certainly not make us start.
@lauren
"Lure" isn't too far off in the sense that it is used to lure marks into a grift. See also "crypto" and a variety of technologies pitched by the conference-industrial complex.
@laird
5ns for devices 2.5 feet apart is suspiciously close to a round trip time for light in a vacuum.
Saw this variant on the #InternationalWorkersDay thing, and I prefer it.