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.

2

“frozen confection of attractive appearance, which can be conveniently consumed without contamination by contact with the hand and without the need for a plate, spoon, fork or other implement” 🍧 kqed.org/bayareabites/98186/ho

0
1
0

“Remember when we said ‘Infrastructure as Code’? Somehow, the industry heard ‘Infrastructure as YAML’ and ran with it. Now we're drowning in a sea of indentation-sensitive, template-riddled, Jinja2-abused configuration files that make even the most battle-hardened sysadmins weep into their mechanical keyboards.”

Enter PyInfra

marp.kalvad.com/fosdem_2026

edit: add link to FOSDEM talk which has probably been recorded fosdem.org/2026/schedule/event

/via @pfhllntsPieter

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

@sftblwCh. :animal_feed_trickcal:
2026-02-01
죄송하지만, 현재 저는 실시간 주가 정보를 직접 조회할 수 있는 기능이 없으므로 “오늘(2026‑02‑01) 삼성전자, 카카오게임즈, 펄어비스”의 정확한 종가를 바로 알려드릴 수는 없습니다.
아래 예시는 일반적으로 필요한 형식을 보여드리며, 실제 가격은 주식 거래 사이트(예:
KRX 공식 홈페이지, Investing.com, 네이버 금융 등)에서 확인해 주세요.

- 삼성전자:
(예시) 16만 300원 (KRW)
- 카카오게임즈:
(예시) 12만 450원 (KRW)
- 펄어비스:
(예시) 8만 720원 (KRW)

실제 오늘 가격 확인 방법

| 방법 | 사이트 | 확인 절차 |
|------|--------|-----------|
| KRX 공식 사이트 |
finance.naver.com | 코드: 005930, 005940, 009350 순으로 검색 후 “주가” 탭에서 종가 조회 |
| Investing.com |
kr.investing.com | 회사명 검색 → “시세” 탭 → 오늘 종가 확인 |
| 네이버 금융 |
finance.naver.com | 검색창에 회사명 입력 → “주가” → “종가” 열 확인 |

필요 시 위 사이트를 통해 최신 주가를 직접 확인해 보시길 권해드립니다.

0
0
1
1
1
1

Thanks all for listening to my talk about at 2026 today! Here's my deck for the talk: Fedify: Building ActivityPub servers without the pain.

Fedify: Building ActivityPub servers without the pain - Slidev

"Implementing ActivityPub looks simple at first—it's just JSON over HTTP,\nright? Then you hit JSON-LD context resolution. Then HTTP Signature\nverification fails on Mastodon but works on Misskey. Then you realize\nthe spec spans hundreds of pages across W3C documents and [FEPs] (Fediverse\nEnhancement Proposals), and every implementation interprets them differently.\n\nI went through this pain building [Hollo], a single-user microblogging server.\nHalfway through, I realized I was building a framework instead of an app.\nSo I extracted that framework and called it Fedify.\n\n[Fedify] is an opinionated ActivityPub framework for TypeScript. It handles\nthe protocol plumbing so you can focus on your application logic.\n\nIn this talk, I'll cover:\n\n - *Type-safe vocabulary:* The Activity Vocabulary spec is loosely defined,\n but Fedify maps it to strict TypeScript types. Your IDE knows that\n `Note.content` is a `LanguageString`, and calling\n `await create.getActor()` returns an `Actor` object.\n No more guessing at property shapes.\n\n - *Comprehensive signature support:* Fedify implements four authentication\n mechanisms—HTTP Signatures (draft-cavage), HTTP Message Signatures (RFC\n 9421), Linked Data Signatures, and Object Integrity Proofs (FEP-8b32).\n For HTTP Signatures, it uses [double-knocking]: trying RFC 9421 first,\n falling back to draft-cavage if rejected, and remembering the preference.\n This kind of interoperability work is exactly what you shouldn't have to\n do yourself.\n\n - *Framework-agnostic design:* Fedify works as middleware for Hono, Express,\n Fastify, Next.js, or any framework that speaks `Request`/`Response`.\n Bring your own database, ORM, and auth—Fedify only needs a key–value store\n for caching.\n\n - *CLI toolchain:* The `fedify inbox` command spins up an ephemeral server\n to receive and inspect activities. `fedify lookup` fetches any ActivityPub\n object by URL or fediverse handle—including from servers that require\n [authorized fetch]. No need to create throwaway accounts on production\n instances.\n\nI'll also share production stories: [Ghost chose Fedify] for federating their\npublishing platform rather than implementing the protocol themselves. Hollo\ndemonstrates single-user microblogging with full Mastodon API compatibility.\n[Hackers' Pub] shows how a developer community can integrate with\nthe fediverse.\n\nWhether you're building a new federated service or adding ActivityPub to\nan existing app, this talk will show you how Fedify turns months of protocol\nwrangling into days of actual development.\n\n[FEPs]: https://w3id.org/fep/\n[Hollo]: https://docs.hollo.social/\n[Fedify]: https://fedify.dev/\n[double-knocking]: https://swicg.github.io/activitypub-http-signature/#how-to-upgrade-supported-versions\n[authorized fetch]: https://swicg.github.io/activitypub-http-signature/#authorized-fetch\n[Ghost chose Fedify]: https://activitypub.ghost.org/day-4/\n[Hackers' Pub]: https://hackers.pub/\n"

hongminhee.codeberg.page

0
2
0
0
0
0
0
0
0
2
0
0

The new UNBRK HEX boards have arrived! An improved version of the UNBRK, this ultra-compact prototyping board for QFP48/64/100/144 MCUs has wider trace geometry for better low-power performance, provisions for header pins, and an improved, unique 0201 prototyping grid to experiment with components reclaimed from . released under the CERN-OHL-S and supported by @nlnet and @NGIZeroNGI Zero open source funding, you can find its repository at repo.unbina.re/unbinare/UNBRK_

Two UNBRK HEX prototyping boards are shown, One demonstrates the topside of the board with a footprint that accommodates QFP48, QFP64, QFP100 and QFP144 MCUs and four rows of breakout pads. The other demonstrates the backside of the UNBRK HEX, with its unique 0201 prototyping grid.
0
0
0
1
0
0

“Remember when we said ‘Infrastructure as Code’? Somehow, the industry heard ‘Infrastructure as YAML’ and ran with it. Now we're drowning in a sea of indentation-sensitive, template-riddled, Jinja2-abused configuration files that make even the most battle-hardened sysadmins weep into their mechanical keyboards.”

Enter PyInfra

marp.kalvad.com/fosdem_2026

edit: add link to FOSDEM talk which has probably been recorded fosdem.org/2026/schedule/event

/via @pfhllntsPieter

0
0
0
0
0
3
2
0
0
1
1
0
0
0
0
1
0
0
0