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.
できた〜〜〜
一人誕生日を祝う
ハッピーバースデー画猫ー♪
あ！botが祝いに来てくれた！
@nyanpuppu_bot@misskey.ioにゃんぷっぷー ＠みんな大好き 
@oishiibot@misskey.ioおいしいBot
誕生日おいしい！
一人誕生日閉会
ねるぞ
00:02 です。 お水飲みましたか?
Did you know the CA in CAPTCHA stands for Completely Automated? lmao
Anyway, here’s a new T-shirt design.
00:02 です。 お水飲みましたか?
あけおめ
언제 만팔천포인트 넣어줬지... 뭘 살까..
As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.
The challenges are numerous:
First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.
Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.
Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.
What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.
昨日のMisskeyの活動は
ノート: 13600(+12)
フォロー: 130(+0)
フォロワー: 129(+0)
でした。
#misshaialert
Apple’s early homepage (~1993)
암호학에 나오는 Alice와 Bob을 가은이와 나은이로 번역하는 생각
No need to reinvent how blobs work—just add cryptographic access on top. Secure, simple, and flexible. Might prototype this soon.
To manage access, another XRPC: com.atproto.repo.manageBlobAccess. Add DIDs, optionally with expiry. List who has access. Revoke as needed.
You could enforce it with a transparent proxy in front of the PDS. Proxy checks the signature, notAfter, did, and nonce before letting the blob request through.
The XRPC looks like this: com.atproto.repo.signBlob. You give it a blob CID and a signed payload. It gives you a signed URL with an expiry and nonce. No global ACLs, just crypto and timing.
This unlocks use cases like private media, community-only access, and paid content - without changing blob storage itself. Everything rides on the URL signature
The idea: blobs could require a signed URL to fetch. First request? You get a 401. Then you hit an XRPC method to generate a signed URL tied to your DID. Use that to fetch the blob. Short-lived, verifiable, and secure.
Been thinking about how we could support access-controlled blobs in ATProtocol. Right now, all blobs are public - anyone can fetch them with a CID. But what if we could gate them? #atproto #atdev 🧵
private_blobs.md
あれ標準化されてないんだ
まあそりゃそうか…?
ふわふわ
As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.
The challenges are numerous:
First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.
Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.
Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.
What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.
As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.
The challenges are numerous:
First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.
Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.
Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.
What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.
As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.
The challenges are numerous:
First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.
Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.
Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.
What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.
身為割過三次內針眼長過好幾次外針眼的的人，在這邊要認真的勸大啊
沒事不要揉眼睛！要揉眼睛的話用衛生紙擦一擦揉一揉，碰眼睛的時候要注意手有沒有髒，如果手髒髒的要洗手再碰眼睛ㄛ！ 
라면 먹으까
だからねフォロイー
ちいさなことでもいいから幸せになって
RE: https://chpk.kur0den.net/notes/a6rwbray12ig0mn3
A good cheat sheet on how to migrate your GitHub code depositories to codeberg
https://taggart-tech.com/migrate-to-codeberg/#cheat-sheet
#Programming #codeberg #OpenSource #GitHub #migration #Microsoft
【NHKニュース速報 23:52】
ロシア 復活祭にあわせて一時停戦へ
プーチン大統領が表明 ３０時間
#ニュース #NHKニュース速報
【NHKニュース速報 23:52】
ロシア 復活祭にあわせて一時停戦へ
プーチン大統領が表明 ３０時間
#ニュース #NHKニュース速報
今年もやって来た春の風物詩
みぇ
キャップ部分だけじゃなくて下の包みの部分ごと回すのが正解だった...:
しあわせににゃりたかったですわね
アルミのボトルキャップと格闘する事15分、ようやくワイン開封できた...
まず自分が幸せになる必要があるのでは???
@kur0den0010Kur0den0010@ふわふわ 俳句を発見しました！
『幸せに なる必要が あるのでは』
노트북이 좀 더 유용한 곳으로 모험을 떠났어!
(노트북이 고장난 불쌍한 대학생에세 빌려줌)
まず自分が幸せになる必要があるのでは???
암호학에 나오는 Alice와 Bob을 가은이와 나은이로 번역하는 생각
幸せそうなフォロイーを見て満足するなど活動は多岐にわたる
てきとう
やあ、疲れたな今日は、体力大大事よほんと。
Sayaka Murata's Vanishing Word is out in English next week! ❤️ (translated by Ginny Tapley Takemori)
‘Marriage feels like a hostage situation, and motherhood a curse’: Japanese author Sayaka Murata https://www.theguardian.com/books/2025/apr/19/marriage-feels-like-a-hostage-situation-and-motherhood-a-curse-japanese-author-sayaka-murata
다씻엇다예요
眠い
ひと段落ついたのでシャワーをしゃわーっと
画猫大可汗
@
@
Chee Aun 🤔
洪 民憙 (Hong Minhee)
sublimer@あすてろいどん鯖管
코미 
