Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.
Landing one of my most ambitious PRs to date — switching vixen's VFS RPC from TCP to SHM (who loves 3-letter-acronyms). I was in suspense the whole time that the macOS sandbox would get in the way and... nope! Works fine 😌
(This is Rust⇄Swift IPC btw, using facet + postcard under the hood)
on that note i have been taking inventory of various things in plain text then progressively converting it to turtle. keyboards i own, concerts i've been to, stuff like that -- pretty bounded within a single document, a good exercise to mapping relations and ontological practices. we'll see what falls out
From now on, forecasts are richer, clearer, and a bit smarter, without losing the familiar, readable style.
You will now see more complete current conditions at a glance: feels-like temperature, humidity, pressure, visibility, UV index, and wind gusts, all grouped in a dedicated Details section. Sunrise and sunset times for the current day are also included.
The wind line is back in focus, clearly highlighted for current conditions, and gusts are shown separately using 💨 emoji so they are easy to spot and not confused with average wind.
Pressure is no longer just a number: FediMeteo now shows a real pressure trend over the last few hours, telling you if it is rising, falling, or staying stable.
A new Warnings section has been added. When relevant, the bot will automatically flag things like:
extreme feels-like temperatures, hot or cold
high UV levels
poor air quality
thunderstorms
heavy rain likely
strong winds or gusts
Hourly forecasts remain at 12 hours, but now include pressure too, which makes short-term weather changes easier to read and anticipate.
Everything is fully localised. Labels like “feels like”, section titles, and weather descriptions are consistent across languages, and all weather conditions are now covered everywhere.
In short: same FediMeteo you are used to, but with more context, clearer signals, and fewer surprises.
These changes will start appearing with the next forecast update.
From now on, forecasts are richer, clearer, and a bit smarter, without losing the familiar, readable style.
You will now see more complete current conditions at a glance: feels-like temperature, humidity, pressure, visibility, UV index, and wind gusts, all grouped in a dedicated Details section. Sunrise and sunset times for the current day are also included.
The wind line is back in focus, clearly highlighted for current conditions, and gusts are shown separately using 💨 emoji so they are easy to spot and not confused with average wind.
Pressure is no longer just a number: FediMeteo now shows a real pressure trend over the last few hours, telling you if it is rising, falling, or staying stable.
A new Warnings section has been added. When relevant, the bot will automatically flag things like:
extreme feels-like temperatures, hot or cold
high UV levels
poor air quality
thunderstorms
heavy rain likely
strong winds or gusts
Hourly forecasts remain at 12 hours, but now include pressure too, which makes short-term weather changes easier to read and anticipate.
Everything is fully localised. Labels like “feels like”, section titles, and weather descriptions are consistent across languages, and all weather conditions are now covered everywhere.
In short: same FediMeteo you are used to, but with more context, clearer signals, and fewer surprises.
These changes will start appearing with the next forecast update.
Even though the video discusses France and the EU looking to reduce their risk by decoupling from big US tech companies, I think Americans should probably consider doing the same.
I have deeply mixed feelings about #ActivityPub's adoption of JSON-LD, as someone who's spent way too long dealing with it while building #Fedify.
Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.
But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.
Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.
To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.
Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.
Alright well this is very much a WIP but it's already more info than I've found on this subject anywhere else on the web: the fandom discord to IRC migration page is live!
Britský premiér Keir Starmer na schůzce s labouristickými poslanci odmítl výzvy k rezignaci. Dočkal se potlesku a podpory velké části zákonodárců, píší média.
It feels like a real sweet spot that I'm notable enough to have my name appear multiple times in a Wikipedia search but not notable enough to appear at all in an Epstein files search.
We've updated our welcome screen in v1.116 with some fresh artwork by @odpomery.bsky.social@bsky.brid.gy
Includes different versions for light and dark themes!
Are people archiving the prompts they use when AI assisted coding? If AI is the new level of abstraction shouldn't we archive the prompts rather than the code itself?
It feels like I'm storing my a.out files on github and throwing out the C code after it compiles.