Andy Sylvester's Web
• Andy
Updated my install of rss.chat (rsschat.andysylvester.com) to the latest server code to pick up a security patch, everything seems to be running smoothly. It is open to all!
Karn Wong
• Unknown
Now you can use GPU to crunch spatial data!
https://sedona.apache.org/latest/blog/2026/06/26/sedonadb-04-gpu-accelerated-spatial-joins/
ใช้ GPU ปั่น spatial data ได้แล้ว จากที่เมื่อก่อนทำได้แค่ optimize ไม่ก็ เพิ่ม CPU / RAM
https://sedona.apache.org/latest/blog/2026/06/26/sedonadb-04-gpu-accelerated-spatial-joins/
That was a huge MISS for Chris Martinez (rare for him but this one really is bad). This movie is one star out of five.
Watched UnMarry [2025] 🎬🍿
Synopsis: In the middle of annulment cases and custody battles, Celine and Ivan meet at the law office of a lawyer and YouTube host of “Walang Butas Ang Batas”. What begins as a chance encounter grows into a friendship that helps them navigate heartbreak, family, and the possibility of starting over.
Newsonaut
• Mark Rogers
Take on Rules
• Jeremy Friesen
Many of the questions about RSS.chat center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even.
Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed.
I don't know if it accomplishes anything but to me it feels like retribution of a sort.
There is a fork of rss.chat in the wild that supports basic federation between instances enabling cross community conversations for pre-defined approved instances. Check it here
You might also be interested in this :)
RSC (Really Simple Conversations) is a social feed where everything is distributed via RSS: posts, as well as replies, entire conversations, and corrections published afterward. Three independent sites can thus participate in the same feed without a common API, without a shared account, and without having to adopt a new protocol: if your site already publishes a feed, it’s already a node in the network.
Island in the Net
• Khürt Williams
One Roll is a monthly film photography series. Each month I load a single roll of 35mm film into the Minolta XD-11, shoot it across whatever presents itself, and mail…
A note to people who run WordCamp conferences. Get your feed act together. There should be a feed for each conference, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program.
It's what we used to call a coral reef. A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to serve them.
This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this in a comment in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is extensible. It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd.
What CrashLoopBackOff, Pending, ImagePullBackOff, and OOMKilled actually mean in kubectl get pods. And the commands that take you from symptom to cause to fix.
A Pod isn't running anywhere until something decides which Node it belongs on. Filtering, scoring, taints, and affinity. The mechanics of kube-scheduler, and why Pending is a scheduling failure, not a mystery.
