What is Hackers' Pub?

Deno 2.3.3 is out 🎊
⭐ deno serve any directory
⭐ fetch over Unix sockets
⭐ new OTel events: boot_failure and uncaught_exception
⭐ dark mode on HTML coverage report

https://github.com/denoland/deno/releases/tag/v2.3.3

Deno 2.3.3 is out 🎊
⭐ deno serve any directory
⭐ fetch over Unix sockets
⭐ new OTel events: boot_failure and uncaught_exception
⭐ dark mode on HTML coverage report

https://github.com/denoland/deno/releases/tag/v2.3.3

Anyone here have experience using @vitest with @deno_landDeno, or setting up a unit test suite that works on #Deno, #Node.js, and #Bun?

#Vitest #JavaScript #TypeScript

Convert from Webpack to Vite (#34450)

Co-authored-by: Renaud Chaput <renchap@gmail.com> by ChaosExAnima has been merged! https://github.com/mastodon/mastodon/commit/c4f47adb49663f24ee80d9174ab24431a8c165c0

Introducing virtual package in MoonBit https://lobste.rs/s/cfiux3 #plt
https://www.moonbitlang.com/blog/virtual-package

Introducing Pyrefly: A new type checker and IDE experience for Python https://lobste.rs/s/czvto8 #plt #python #rust
https://engineering.fb.com/2025/05/15/developer-tools/introducing-pyrefly-a-new-type-checker-and-ide-experience-for-python/

Meta introduced Pyrefly, a new type checker and IDE experience for Python.

해커스펍 정모하면 사진기사 하고 싶음

If a module defines a custom exception type and throws that exception within the module, it absolutely must export that exception type as well. I'd think this is basic, but it seems a surprising number of packages declare exception types without exporting them.

Good news! We've officially added #Cloudflare #Workers support to the #Fedify roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

#CloudflareWorkers

Or at least, I wish they'd create a Bluesky account and turn on Bridgy Fed.

I wish all the library projects I use had official fediverse accounts so I could follow them.

해커스펍 정모하면 사진기사 하고 싶음

이제 https://github.com/marv1nnnnn/llm-min.txt 가 쪼개준다. yeah~

If a module defines a custom exception type and throws that exception within the module, it absolutely must export that exception type as well. I'd think this is basic, but it seems a surprising number of packages declare exception types without exporting them.

If a module defines a custom exception type and throws that exception within the module, it absolutely must export that exception type as well. I'd think this is basic, but it seems a surprising number of packages declare exception types without exporting them.

If a module defines a custom exception type and throws that exception within the module, it absolutely must export that exception type as well. I'd think this is basic, but it seems a surprising number of packages declare exception types without exporting them.

@reiver@reiver ⊼ (Charles) Your reply makes me realize that we need a new property in ActivityPub, like isNotSerious or isJoke that I can mark on posts.

By the way, in case you didn't notice, the previous sentence is not serious.

@reiver@reiver ⊼ (Charles) Your reply makes me realize that we need a new property in ActivityPub, like isNotSerious or isJoke that I can mark on posts.

By the way, in case you didn't notice, the previous sentence is not serious.

What's up with Fresh? 🍋

https://deno.com/blog/an-update-on-fresh

Linux 6.15 is right around the corner, which means it's time for another progress report! We have been pretty busy behind the scenes and we have some exciting developments to share with you all!

As always, we want to thank everyone who support us as none of this would be possible without your generous support.

https://asahilinux.org/2025/05/progress-report-6-15/

I'm not happy with how Mastodon abbreviates Mastodon to mstdn. For me it looks like Microsoft Technical Developer Network or something

Here's the full workshop handout plus annotated slides from "Building software on top of Large Language Models", a three hour tutorial I presented yesterday at PyCon US #PyConUS https://simonwillison.net/2025/May/15/building-on-llms/

FEPs, SLEPs, APEs, AIPs, PEEPs, CEPs, SKIPs, SPECs, TIPs, CFEPs, NEPs, JEPs, BIPs, DEPs, DEPs, KEPs, JEPs, WEPs, IPEPs...

A lot of projects name proposals after PEPs rather than RFCs.

What are they? Where did PEPs come from? Here's @fluflThe FLUFL on the origin!

https://hugovk.dev/blog/2025/peps-and-co/
#Python #PEP #RFC #etymology #history #blog

@mikebrobertsMike Roberts While the W3C specs exist as a reference, I wouldn't recommend starting there—they're underspecified and don't provide enough practical guidance for implementation.

Instead, I'd suggest these more practical resources:

1. Fedify's Creating your own federated microblog tutorial:

   • Provides a hands-on, step-by-step implementation
   • Covers both the theory and practice in an accessible way
   • Shows how to handle common ActivityPub patterns

2. For a better conceptual overview:

   • Sebastian Jambor's excellent Understanding ActivityPub series
   • Darius Kazemi's A highly opinionated guide to learning about ActivityPub

3. The SocialHub forum has many discussions about implementation practices and challenges faced by developers.

4. The FEP (Fediverse Enhancement Proposals) process documents community-developed extensions and conventions that go beyond the official spec.

The biggest challenge with ActivityPub isn't understanding the core concepts, but navigating all the de facto standards and practices that have evolved beyond the specs. Starting with practical tutorials rather than specs will give you a much clearer path forward.

@mikebrobertsMike Roberts While the W3C specs exist as a reference, I wouldn't recommend starting there—they're underspecified and don't provide enough practical guidance for implementation.

Instead, I'd suggest these more practical resources:

1. Fedify's Creating your own federated microblog tutorial:

   • Provides a hands-on, step-by-step implementation
   • Covers both the theory and practice in an accessible way
   • Shows how to handle common ActivityPub patterns

2. For a better conceptual overview:

   • Sebastian Jambor's excellent Understanding ActivityPub series
   • Darius Kazemi's A highly opinionated guide to learning about ActivityPub

3. The SocialHub forum has many discussions about implementation practices and challenges faced by developers.

4. The FEP (Fediverse Enhancement Proposals) process documents community-developed extensions and conventions that go beyond the official spec.

The biggest challenge with ActivityPub isn't understanding the core concepts, but navigating all the de facto standards and practices that have evolved beyond the specs. Starting with practical tutorials rather than specs will give you a much clearer path forward.

How to Build a Smartwatch: Picking a Chip

Link: https://ericmigi.com/blog/how-to-build-a-smartwatch-picking-a-chip/
Discussion: https://news.ycombinator.com/item?id=43981680

Haskell is used by startups and large corporations, because it’s one of the best and easiest programming languages for high-performance multi-core processors with convenience and efficiency.

진짜? easiest라고? https://discourse.haskell.org/t/emphasize-why-haskell-on-haskell-org-landing-page/12036

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

#fedidev

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

#fedidev

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

#fedidev

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

#fedidev

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

#fedidev

Show HN: HelixDB – Open-source vector-graph database for AI applications (Rust)

Link: https://github.com/HelixDB/helix-db/
Discussion: https://news.ycombinator.com/item?id=43975423

The new upcoming federation feature in forgejo will allow to follow user-activities accross the fediverse 🙂

#Federation #Forgejo #fediverse

#Firefox is on #GitHub now: https://github.com/mozilla-firefox/firefox

Over the weekend, I wrote an overview of Biome's type architecture, including our motivation and a discussion of the constraints that led to this architecture: https://arendjr.nl/blog/2025/05/biome-type-architecture/

Reply to this post to comment!

#OpenSource #WebDev #Tooling #JavaScript #TypeScript #Rust #RustLang

Re: https://github.com/TryGhost/ActivityPub/issues/570#issuecomment-2873773122

@julian I believe you can use only its signature generation/verification functions without depending on Fedify's other features right now, e.g.:

import {
  createProof, // Create OIP
  createSignature, // Create LDS
  signRequest, // Create HS
  verifyObject, // Verify OIP
  verifyRequest, // Verify HS
  verifySignature, // Verify LDS
} from "@fedify/fedify/sig";

Also, Fedify is available on npm, and is used with Node.js or Bun!

Finally got to build this. Quick UI toggles to see all possible permutations of a post.

Previously was trying out Storybook.js but it's a bit too much for my needs (too many files, too many clicks).

CSS view transitions are pretty cool. More permutations need to be added later. And it's fun building this.

#PhanpySocialDev

Just wrote the Why Fedify? section in the #Fedify docs.

Every mathematical model of reality starts by introducing redundancy and ends by removing it.

I'm looking for a Markdown formatter, and I'm quite particular about my Markdown style. I don't want it to be formatted in a generic Markdown style. For instance, I prefer a style that adheres to rules such as:

• 80 characters at most per line, except for code blocks and URLs.
• Prefer reference links over inline links.
• Prefer setext headings over ATX headings.
• Two new lines before opening an H1/H2 heading.
• One space before and two spaces after a bullet.
• Wrap file paths in asterisks.
• Wrap inline code in backticks.
• Wrap code blocks in quadruple tildes (~~~~), and specify the language with a single space after the opening tildes (e.g., ~~~~ bash).

Are there any Markdown formatters that allow for such detailed customization of these elements? Or would I have to build one myself?

I'm looking for a Markdown formatter, and I'm quite particular about my Markdown style. I don't want it to be formatted in a generic Markdown style. For instance, I prefer a style that adheres to rules such as:

• 80 characters at most per line, except for code blocks and URLs.
• Prefer reference links over inline links.
• Prefer setext headings over ATX headings.
• Two new lines before opening an H1/H2 heading.
• One space before and two spaces after a bullet.
• Wrap file paths in asterisks.
• Wrap inline code in backticks.
• Wrap code blocks in quadruple tildes (~~~~), and specify the language with a single space after the opening tildes (e.g., ~~~~ bash).

Are there any Markdown formatters that allow for such detailed customization of these elements? Or would I have to build one myself?

This is how monopoly looks… Remember, not a single book author, artist, or FLOSS developer has ever been paid. They just used all of your data to train AI and are now making billions in profits while you struggle to buy eggs. This is why monopoly is so bad. #ai #microsoft #openai

I wish #Zed had profiles like Visual Studio Code. The interference between extensions is annoying. For example, Biome and Deno both try to do formatting.

If you’re a developer writing a GTK app and you want it to be accessible, you might want to check out the following links:

https://developer.gnome.org/documentation/guidelines/accessibility/coding-guidelines.html

https://docs.gtk.org/gtk4/section-accessibility.html

Okay, I've just deployed a bleeding edge #Fedify, which implements both RFC 9421 and double-knocking, to Hackers' Pub. If you'd like to test your implementations against a real server, please give it a try! (If you want to create an account, let me know—I can invite you.)

#fedidev #ActivityPub

I got 19/20 on the ActivityPub Quiz!

Just for fun... try this #ActivityPub quiz to test your knowledge of the protocol.

https://apquiz.stevebate.dev/

I Want to Love Linux. It Doesn’t Love Me Back https://lobste.rs/s/biswto #a11y #linux
https://fireborn.mataroa.blog/blog/i-want-to-love-linux-it-doesnt-love-me-back-post-1-built-for-control-but-not-for-people/