What is Hackers' Pub?

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.

0

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)

github.com/bearcove/vixen/pull

0
0
1

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

0

FediMeteo got a solid upgrade today 🌤️

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.


0

Pretend I know nothing about home design/home improvement (because I don't).

I want to wallpaper one of my office walls. Is there a specific brand of wallpaper I should look at?

For chronic pain reasons, I'll hire someone who knows what they're doing to actually put it up.

0

FediMeteo got a solid upgrade today 🌤️

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.


0
0
0
0
0
0
0
0
0
0
0
0
0
0

I have deeply mixed feelings about 's adoption of JSON-LD, as someone who's spent way too long dealing with it while building .

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.

2
26
1
0

You wan't to move from to and , but you really miss one or two core feature?

I'll work the next few weeks on some of those missing features to help you and your community to migrate ✨

So what do you miss the most?

0
0
0
0
0
0
0
0
0
0
0
0
0
0

Despite a policy shift away from renewables from the Trump administration, energy companies are still turning to the fast and cheap power of solar and wind energy to provide power. The thing that’s actually changing? Their messaging. spectrum.ieee.org/trump-renewa

0
0
0
0
0
0
0
0
0
1
0
0
0
1
0
0
0
0
0

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.

0
0
0
0
0

City of Alameda withdraws proposal to buy Teslas for police officers

The Morning Bun @hello@www.themorningbun.com

City Council and staff have read your emails and withdrawn the "Recommendation to Authorize [...] Purchase of Two Tesla Y Police Sport Utility Vehicles":

WITHDRAWN - Recommendation to Authorize the Purchase of Seventeen Hybrid Ford Interceptors from Towne Ford in an Amount-Not-to-Exceed $1,074,652.26, Including a 3% Contingency, with Aftermarket Equipment from Kerr Industries in an Amount-Not-to-Exceed $351,682.12, Including a 3% Contingency; and Purchase of Two Tesla Y Police Sport Utility Vehicles from Unplugged Performance, Including Aftermarket Equipment, in an Amount-Not-to-Exceed $143,628.27, Including a 3% Contingency. (Public Works 60141581) [Will not be heard on February 17, 2026]
revised agenda for Alameda City Council meeting on February 17, 2026

Typically when agenda items are withdrawn, that means that staff will continue to refine the topic and may bring it back in a revised form to a future City Council meeting. Replacing aging vehicles from the city fleet is inline with city policy and budgets, so this item will certainly come back — just hopefully with a more reliable and less toxic vendor for the proposed electric vehicles.

My understanding is that multiple council members requested that this item be withdrawn. One of their responses was shared with me by a Morning Bun reader. Here are Councilmember Tracy Jensen's well-articulated comments in an email last Friday:

Thank you for sharing your opposition to the purchase of Tesla EVs for Alameda's vehicle fleet.

I will not support the purchase of vehicles manufactured by a company with a demonstrable record of discrimination.  According to Diaz v. Tesla, Inc.  a jury found Tesla guilty of permitting "severe and pervasive racial harassment" in the workplace at Tesla's Alameda County manufacturing plant.  Workplace discrimination was also the basis for a 2024 EEOC lawsuit against Tesla, an action which was pulled back with the election of President Trump.

In addition to employment violations, recent action by California DMV alleges that Tesla uses deceptive marketing practices to increase profits. City procurement policies must support Alameda values of transparency, diversity and equity - principles which are not demonstrated by Tesla's business practices.

I have shared my concerns with city staff and requested that the recommendation to purchase the Tesla vehicles be removed from the February 17 City Council Agenda.

Thank you to all of the members of City Council who requested staff put more time into investigating the wide variety of EV options available from vendors inline with City of Alameda's expectations and values.

And thank you also to city staff, many of whom worked a full day on Saturday supporting a City Council strategic planning workshop, and are now back in the office on Monday revising this agenda and doing everything else that keeps Alameda running smoothly.

🙏
P.S. This "thank you also to city staff" includes the staff responsible for this original proposal. I read no ill-will in it. The point of the public process is to allow the city's elected officials, residents, and other stakeholders to provide further input into key decisions. I appreciate that public feedback has been received and will shape next steps.
🚚
P.P.S. Today the LA Times published an investigation into how Tesla is hogging California state incentives to electrify big rigs. They are likely to never deliver all the subsidized orders — but will in the meantime prevent other manufacturers from effectively selling their own EV semi-truck tractors. If you're looking for a productive place to put justified anger with Tesla-Musk-X-the-Everything-Stonk, consider emailing the California Air Resources Board at arbboard@arb.ca.gov and CC CleanTransportationIncentives@arb.ca.gov and info@californiahvip.org and cotb@arb.ca.gov
Read more →
0