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.
RE: https://misskey.io/notes/aj1a3jqau3ms09ko
昨年
リクエストした作品、ほとんど納品いただいていて納品待ちはあと2件
So, you want me to code in a language that has no formal specification, no test suite, that changes continuously, where builds are not reproducible, where results depend on a hidden state in a build cache that can't be backed up, where I have to pay for each compilation, where I have to continuously send a copy of my code to a third party, and that might disappear with no notice?
Geee, vibe coding looks FUN!
The path is dark, with a few splashes of color.
But the light is there, at the end.
@david_megginson 
@benBen Werdmuller
Though with regards to progress, there's a difference in both approaches.
At the #SolidProject side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.
While at #ActivityPub side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix #interoperability breakages.
The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.
@david_megginson @benBen Werdmuller
Btw, just found the v2 release announcement of 
Kudos to the #fedify developers. Handing people tools they need to focus on solutions, and build without getting thrown into deep on-the-wire impl detail reeds to worry about.
That is the positive side of the equation. There's not only a big uptick in interest for the #SocialAPI i.e. #ActivityPub client-to-server, which offers new opportunity to correct course. But also are there more #FOSS projects focused on robust tool and library support for the 'Solution developer' stakeholder.
In the revamp of the delightful commons initiative, made possible with support of 
@nlnet I emphasized all these projects, while I de-emphasized the apps that are already doing good for themself, but contribute to further divergence from open standards.
https://delightful.coding.social
https://hollo.social/@fedify/019c8521-92ef-7d5f-be4d-c50eae575742
"Fedify 2.0.0 está aqui!
Esta é a maior atualização da história do Fedify. Destaques:
**Arquitetura modular** – O pacote monolítico `@fedify/fedify` foi dividido em pacotes independentes e focados: `@fedify/vocab`, `@fedify/vocab-runtime`, `@fedify/vocab-tools`, `@fedify/webfinger` e outros. Pacotes menores, imports mais limpos e a possibilidade de estender o ActivityPub com tipos de vocabulário personalizados.
**Painel de depuração em tempo real** – O novo pacote `@fedify/debugger` oferece um dashboard ao vivo em `/__debug__/` que mostra todo o tráfego de federação: traces, detalhes das atividades, verificação de assinaturas e logs correlacionados. Basta envolver seu objeto `Federation` e pronto.
**Suporte a relay do ActivityPub** – Suporte nativo a relays via `@fedify/relay` e o comando CLI `fedify relay`. Compatível com os protocolos Mastodon-style e LitePub-style (FEP-ae0c).
**Entrega ordenada de mensagens** – A nova opção `orderingKey` resolve o problema do "post zumbi", quando um `Delete` chega antes do seu `Create`. Atividades com a mesma chave são entregues garantidamente na ordem FIFO.
**Tratamento de falhas permanentes** – `setOutboxPermanentFailureHandler()` permite reagir quando uma inbox remota retorna 404 ou 410, possibilitando limpar seguidores inacessíveis em vez de tentar reenviar indefinidamente.
Outras novidades incluem negociação de conteúdo no nível do middleware, `@fedify/lint` para regras compartilhadas de linting, `@fedify/create` para scaffolding rápido de projetos, arquivos de configuração para a CLI, suporte nativo à CLI em Node.js/Bun e diversos fixes de bugs.
Esta versão conta com contribuições significativas de participantes do OSSCA da Coreia. Agradecemos imensamente a todos envolvidos!
Trata-se de uma release major com breaking changes. Consulte o guia de migração antes de atualizar.
Notas completas da release: https://github.com/fedify-dev/fedify/discussions/580
#Fedify #ActivityPub #fediverso #fedidev #TypeScript"
@fediverseFediverso 
@tecnologia 
@academicosAcadêmicos do Fediverso 
@internet (pode seguir para acompanhar os assuntos ou marcar para amplificar a postagem até no #lemmy tb)
自分はcron で過去1日分を書き出している
chrome で見たページの履歴を全てとっておく Archivist というツールを作った - tokuhirom's blog https://blog.64p.org/entry/2026/02/13/092448
matsuu: "わいわい。家庭内ラズパイとかVPSとかで動かしておきたい。いっちょやるか --- chrome で…" - Fedibird https://fedibird.com/@matsuu/116112492423199245
LogTape, the JavaScript/TypeScript logging library I created, was featured on Sentry's official YouTube channel!
UIをもち実行中であるアプリケーションソフトを何と言えば良いかというとインスタンスだろうか
なんかピンとこない
The really cool thing about this new architecture is that it can enable Client to Server architecture for AP with fedify (maybe vocab packages could be used in the browser too!)
Fedify 2.0.0 is here!
This is the biggest release in Fedify's history. Here are the highlights:
Paolo Melchiorre
Ian Wagner
洪 民憙 (Hong Minhee) 
nulta
洪 民憙 (Hong Minhee)@fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.@fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.@fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.setOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.
This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!
This is a major release with breaking changes—please check the migration guide before upgrading.
Full release notes: https://github.com/fedify-dev/fedify/discussions/580
@fedifyFedify: ActivityPub server framework Modular architecture — The monolithic @fedify/fedify package has been broken up into focused, independent packages:woo! that's excellent news! i had a handful of (not currently maintained or used) libraries i wrote myself (codeberg.org/outpost/ts-libs) because all the alternatives either did too much (fedify before this) or weren't that great (the existing http signature library does not do typescript from what i can tell)
Fedify 2.0.0 is here!
This is the biggest release in Fedify's history. Here are the highlights:
@fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.@fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.@fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.setOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.
This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!
This is a major release with breaking changes—please check the migration guide before upgrading.
Full release notes: https://github.com/fedify-dev/fedify/discussions/580
Fedify 2.0.0을 릴리스했습니다!
Fedify 역사상 가장 큰 릴리스입니다. 주요 변경 사항을 소개합니다:
@fedify/fedify 패키지를 @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger 등 독립적인 패키지들로 분리했습니다. 번들 크기가 줄어들고, 임포트가 깔끔해지며, 커스텀 어휘 타입으로 ActivityPub을 확장할 수도 있습니다.@fedify/debugger 패키지로 /__debug__/ 경로에 라이브 대시보드를 띄울 수 있습니다. 연합 트래픽의 트레이스, 액티비티 상세, 서명 검증, 로그까지 한눈에 확인할 수 있습니다. 기존 Federation 객체를 감싸기만 하면 됩니다.@fedify/relay 패키지와 fedify relay CLI 명령어로 릴레이 서버를 바로 띄울 수 있습니다. Mastodon 방식과 LitePub 방식 모두 지원합니다(FEP-ae0c).orderingKey 옵션으로 “좀비 포스트” 문제를 해결합니다. Delete가 Create보다 먼저 도착하는 문제가 더 이상 발생하지 않습니다. 같은 키를 공유하는 액티비티는 FIFO 순서가 보장됩니다.setOutboxPermanentFailureHandler()로 원격 인박스가 404나 410을 반환할 때 대응할 수 있습니다. 도달 불가능한 팔로워를 정리하는 등의 처리가 가능합니다.이 외에도 미들웨어 수준의 콘텐츠 협상, @fedify/lint, @fedify/create, CLI 설정 파일, 네이티브 Node.js/Bun CLI 지원, 다수의 버그 수정 등이 포함되어 있습니다.
이번 릴리스에는 한국 OSSCA (오픈소스 컨트리뷰션 아카데미) 참가자분들의 큰 기여가 담겨 있습니다. 참여해 주신 모든 분께 감사드립니다!
브레이킹 체인지가 포함된 메이저 릴리스입니다. 업그레이드 전에 마이그레이션 가이드를 꼭 확인해 주세요.
전체 릴리스 노트: https://github.com/fedify-dev/fedify/discussions/580
Fedify 2.0.0 is here!
This is the biggest release in Fedify's history. Here are the highlights:
@fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.@fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.@fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.setOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.
This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!
This is a major release with breaking changes—please check the migration guide before upgrading.
Full release notes: https://github.com/fedify-dev/fedify/discussions/580
Ihr kennt ja sicherlich diese Übersicht von Congress #Designs (u.a. vom #39c3 ): https://designs.events.ccc.de/
Oder auch die #Chaos #Sticker Collection: https://mwarning.github.io/chaos-sticker-collection/
Wir haben auch ein paar Designs gemacht und wollen von euch unbedingt Feedback dazu haben. Wie findet ihr die Designs? (Es kommen in den nächsten Tagen noch mehr) Würdet ihr was daran ändern? Würdet ihr solche Sticker haben wollen?
DNAが生命そのものではないようにプログラムと動いているアプリケーションは同じものではない
🫶
遅ればせながらですが
自画自賛ですがモンティス可愛く綺麗に描けたので嬉しくなっています
リクエストありがとうございました！
#Skeb #アークナイツ
https://skeb.jp/@waiomori/works/7
AI "artists". Nothing like a hard days work for those guys. 🧑🎨
#fuckai #noai #fuckaimusic #fuckaiart #aimusic #music #humanart #ai #aiart #humans #artist #musicians #art #creativity #creative #original #innovation #hardwork
Aus der Rubrik "Wir brauchen Alters- und Identiätskontrollen im Internet" heute:
Die Wiener Polizei sucht einen Betrüger, der mit zig gestohlenen Identitäten von Dezember 2024 bis Jänner 2025 mehrere Bankkonten eröffnet hat. Zudem soll er Handys bestellt und Verträge bei Mobilfunkbetreibern abgeschlossen haben.
https://wien.orf.at/stories/3342948/
今日の夜景にゃぷで「普通の」
ヶ丘は全パターン撮った感あるな
咖喱牛肉末飯
當我發現谷愛凌原來是江旻憓同一大學、同一學科的師妹，我開始懷疑史丹福大學國際關係課程怎樣收生
(截圖文章來源: https://time.com/7355691/eileen-gu-interview-2026-olympics/ )
24시간 맥도날드는 한국인 학생들도 가서 자는 사람 많아요
한편 백인들은 서울에 여행왔다면서 구걸을 하던데
RE: https://bsky.app/profile/did:plc:qqprlpqhpawgaytoyrif2iou/post/3mfggpwhjzs2y
SD1merrill撮って出し
できた、みまもり姉さんが
今日明日の強風で梅の花もかなり散っちゃいそうで
#misskey写真部 #photography #birdphotography #birds #野鳥
1차 비건 점심 먹은 곳이 이분법적 화장실이었는데, 2차 비건카페 갈 때까지 나 포함 모든 분이 화장실을 참고 계셨다 모임장소 선정에 신중을 기하겠습니다...
[IT카페]개인정보위 '나무위키' 정조준 왜?
수정2026.01.13. 오후 5:21
수년간 자료제출 요구에도 묵묵부답
탈퇴 어렵게 하고 개인정보 법 위반 적발
경찰 고발해 수사키로…국제 공조 가능성도 view.asiae.co.kr/article/2026...
[IT카페]개인정보위 '나무위키' 정조준 왜? - ...
Dear media writing about tech: Sam Altman shitting on "data centers in space" is not the story. Nobody thought that that narrative makes any sense.
You failed as reporters when you pretended it did just cause rich dude claimed it would be the future.
ちょっと散歩行ってきた
横浜遠かった
Dear media writing about tech: Sam Altman shitting on "data centers in space" is not the story. Nobody thought that that narrative makes any sense.
You failed as reporters when you pretended it did just cause rich dude claimed it would be the future.
オフトゥンでもふもふしてた結果、ガッツリ寝てしまってた
最近撮ったネコちゃんお写真
The really cool thing about this new architecture is that it can enable Client to Server architecture for AP with fedify (maybe vocab packages could be used in the browser too!)
The really cool thing about this new architecture is that it can enable Client to Server architecture for AP with fedify (maybe vocab packages could be used in the browser too!)
Fedify 2.0.0 is here!
This is the biggest release in Fedify's history. Here are the highlights:
leyrer
かぼぷ
dwn 
pkg update
Aslak Raanes@fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.@fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.@fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.setOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.
This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!
This is a major release with breaking changes—please check the migration guide before upgrading.
Full release notes: https://github.com/fedify-dev/fedify/discussions/580
NIKKOR Z 58mm f/0.95 S Noct
AI이미지(피규어화)
순서대로
GEMINI
Grok(X)
ChatGPT
챗지피티가 지금은 피규어 제일 잘 뽑는듯
猫の日～！🐾
음냐리
The path is dark, with a few splashes of color.
But the light is there, at the end.
Gehoord in de ether:
> Ik kan al een paar dagen geen #iDEAL / #Wero transacties meer doen met #Librewolf / #Firefox. Hebben jullie daar misschien ook last van?
Thank you for your query.
#ChrietTitulaerAI predicted the response of the future:
> Oh wacht, dan geef ik de Prompt Engineer in het single-person project even de opdracht om de Wero integratie op een iets andere manier door de #AI the laten vibe coden. Denk dat er een hallucinatietje op de lijn gekropen is of zo. De 100 millioen lines of code vergen wel een half dagje om te hergenereren. We hebben ook veel grotere terawatt datacenters nodig in EU, hè? Die bureaucraten daar, zucht.
College grading concept: "Use LLMs all you want, but you're never getting a grade higher than a C. Don't complain. A C is average. Right now you all have Cs."
@david_megginson @benBen Werdmuller
Though with regards to progress, there's a difference in both approaches.
At the #SolidProject side you have inertia by the slow standardization process. But should they figure things out in a good way, eventually the ecosystem catches up and the inertia can quickly decrease.
While at #ActivityPub side, since AS/AP remains stagnant, the ever increasing protocol decay and tech debt non-linearly increases inertia and progress. And on top of that, you are never done once you implemented the 'ad-hoc specs' of the installed base, and you have to account for continuous whack-a-mole development and maintenance burdens to fix #interoperability breakages.
The AS/AP based fediverse devolves into effectively no interoperability, and a situation that is more comporative to NPM dependency hell.
@david_megginson @benBen Werdmuller
Btw, just found the v2 release announcement of
Kudos to the #fedify developers. Handing people tools they need to focus on solutions, and build without getting thrown into deep on-the-wire impl detail reeds to worry about.
That is the positive side of the equation. There's not only a big uptick in interest for the #SocialAPI i.e. #ActivityPub client-to-server, which offers new opportunity to correct course. But also are there more #FOSS projects focused on robust tool and library support for the 'Solution developer' stakeholder.
In the revamp of the delightful commons initiative, made possible with support of @nlnet I emphasized all these projects, while I de-emphasized the apps that are already doing good for themself, but contribute to further divergence from open standards.
https://delightful.coding.social
https://hollo.social/@fedify/019c8521-92ef-7d5f-be4d-c50eae575742
