Goofed Home

@Kye There were two APconfs, 2019 and 2020. There have been quite a number of events since, (Berlin Fediverse Day, Fediform, etc) but yes, I do think it's true that the fediverse shouldn't underestimate the amount of energy is in the ATmosphere right now

@Kye@tech.lgbt

if people does things on ap, "woah cool"

if you do stuff in ap that deviates from what mastodon does (shit like invisible mentions or wafrn tags), people will start talking shit about you

Well, what is happening to our office suits?

Clickbait

@Kye I bet if someone keeps putting "neo" in front of libertarian they'll finally end up with a new term they can define and nobody will take it over for sure this time

@benpate Sure: https://github.com/prosembler/nitro-porter

My biggest wish for any project is to build in their own tools for recalculating derived data — post counts, point totals, last post in a topic, etc.

Most apps assume you've never used any other platform or that their calculated data could be wrong. It's a huge time sink to "fix" data handling for them in an export.

To add support to Nitro Porter directly, there's a guide in the docs: https://nitroporter.org/develop.html

It’s that time of the year when we get to take a closer look at the new features and improvements of the next major release of KDE’s Plasma desktop environment, KDE Plasma 6.7, due out in June 2026.

Some of the biggest changes in KDE Plasma 6.7 include the ability to type characters that aren’t on your physical keyboard, a switch on the Plasma Panel to instantly go from light mode to dark mode, a global push-to-talk feature, and a full-featured print queue viewer app.

KDE Plasma 6.7 also introduces a dedicated setup UI for configuring shared printers on Windows networks, a new rounded style for selection highlights in Breeze-themed apps like Dolphin, Okular, and KMail, and support for installing custom sound themes from downloaded files.

On the kernel security list we’ve seen a huge bump of reports. We were between 2 and 3 per week maybe two years ago, then reached probably 10 a week over the last year with the only difference being only my butt slop, and now since the beginning of the year we’re around 5-10 per day depending on the days (fridays and tuesdays seem the worst). Now most of these reports are correct, to the point that we had to bring in more maintainers to help us.

Something I’m predicting is that at least it will change the approach to security fixes: [ … ] software that used to follow the “release-then-go-back-to-cave” model will have to change to start dealing with maintenance for real, or to just stop being proposed to the world as the ultimate-tool-for-this-and-that because every piece of software becomes a target.

[ … ]

Overall I think we’re going to see a much higher quality of software, ironically around the same level than before 2000 when the net became usable by everyone to download fixes. When the software had to be pressed to CDs or written to millions of floppies, it had to survive an amazing quantity of tests that are mostly neglected nowadays since updates are easy to distribute. But before this happens, we have to experience a huge mess that might last for a few years to come! Interesting times…

I checked my Pixelfed messages today and see this. I’ve literally no idea what the first half means, so I asked my daughter to translate the acronyms. No idea what “no disrespect” is conveying.

I never really thought of pixelfed as a place for spam or scammers. If the intent is genuine, then I’m even more perplexed by how they are choosing communicating. I’m not going to respond because it feels off, so yeah…

Perhaps I’m just showing my age?

Yep. ☺️

Basically how every 90s chat room session started.

I remember L being for location.

Cache-Control and Vary

Thanks to everyone who replied! Unfortunately HTTP caching is not our strong suit in the ActivityPub world; HTTP Signature header(s) are a real public cache buster. But you can do at least some good caching per user. tags.pub provides ETag, and sends If-None-Match and If-Modified-Since, but doesn't do Last-Modified well yet.

The problem with Signature: and Signature-Input:

If the server wants to say, "this content is different for different users", you use the Vary header. For OAuth, you'd use Vary: Authorization, say. And the cache knows to separate data for different users. Same OAuth token, you can reuse the cached data.

We include our ID in the Signature (or Signature-Input) header. But we also include a timestamp there, so every single request has a different signature (by design).

@julian hmmm. With a reverse chron collection you can do pretty well with `totalItems` and the first item on the first page.

If there were net items added or deleted, `totalItems` will be different.

If the same number of items were added and deleted, the most recent item will be different.

So you can check synch with a couple of hits.