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
0

사후 세계에서도 죽을 때까지 일하는 이야기 ridibooks.com/books/206600... "블랙기업의 과로와 괴롭힘을 견딜 수 없었던 여직원인 하쿠지츠 코히루는 스스로 목숨을 끊는다. 자살한 그녀가 도착한 곳은 천국도 지옥도 아닌, 화이트 기업이다?! 오로지 행복하게 살고 싶었던 그녀의 소원은 사후 세계에서 이뤄져 가는데…." 아무리 요즘 만화, 웹소설들이 사람들의 욕망을 저격한다지만 이건 정말 힘들어요...

사후 세계에서도 죽을 때까지 일하는 이야기 - 최신권 ...

1

📣 Phanpy folks using non-QWERTY keyboards, now you can test this keyboard-layout-dependant shortcuts on dev site 🙇‍♂️ github.com/cheeaun/phanpy/issu

For context, currently keyboard shortcuts are keyboard-layout-independant (`e.code`). E.g. for a Dvorak keyboard layout, the physical `c` key is mapped to `j`, so it's confusing. Now with keyboard-layout-dependant shortcuts, it will listen to the produced key (`e.key`) rather than the code (`e.code`).

0
0
0
0
0

喜歡當代藝術館的空間,
查了一下後才知道,
其前身為日治時代的建成尋常小學。

真是不意外了,
許多日治時代的建築物都很美。

0

I've been considering what to add in the next version of BotKit (v0.2.0) and wanted to share my current plans. After reviewing feedback and examining the ecosystem, I've identified three key features that would significantly enhance the framework's capabilities:

  1. Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.

  2. Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).

  3. Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

These additions should make more capable while maintaining its simple, developer-friendly API. I expect implementation to involve extending the Message class and adding new Text processing capabilities, all while keeping backward compatibility with existing bots. Having built both Hollo and Hackers' Pub, I already have deep familiarity with how various ActivityPub implementations handle these features across the fediverse. I welcome any community feedback on priorities or implementation details before I begin coding.

1

I've been considering what to add in the next version of BotKit (v0.2.0) and wanted to share my current plans. After reviewing feedback and examining the ecosystem, I've identified three key features that would significantly enhance the framework's capabilities:

  1. Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.

  2. Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).

  3. Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

These additions should make more capable while maintaining its simple, developer-friendly API. I expect implementation to involve extending the Message class and adding new Text processing capabilities, all while keeping backward compatibility with existing bots. Having built both Hollo and Hackers' Pub, I already have deep familiarity with how various ActivityPub implementations handle these features across the fediverse. I welcome any community feedback on priorities or implementation details before I begin coding.

0

I've been considering what to add in the next version of BotKit (v0.2.0) and wanted to share my current plans. After reviewing feedback and examining the ecosystem, I've identified three key features that would significantly enhance the framework's capabilities:

  1. Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.

  2. Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).

  3. Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

These additions should make more capable while maintaining its simple, developer-friendly API. I expect implementation to involve extending the Message class and adding new Text processing capabilities, all while keeping backward compatibility with existing bots. Having built both Hollo and Hackers' Pub, I already have deep familiarity with how various ActivityPub implementations handle these features across the fediverse. I welcome any community feedback on priorities or implementation details before I begin coding.

1
0
0

赤城センセの記事かなんかで「50mmをレトロフォーカスで作ったら?」ってのに対してメーカーさんが「クソデカレンズになりますよ」って答えてたのを読んだ
クソデカ上等!ってやったのがZEISS

0

赤城センセの記事かなんかで「50mmをレトロフォーカスで作ったら?」ってのに対してメーカーさんが「クソデカレンズになりますよ」って答えてたのを読んだ
クソデカ上等!ってやったのがZEISS

0
0
0

이제 Python에 검증된 암호화 코드 15,000줄이 제공됩니다
------------------------------
- Python 기본 해시 및 HMAC 알고리듬이 이제 *검증된 암호화 코드* 인
HACL *로 대체됨
- 약 *15,000줄의 C 코드* 가 HACL\*로부터 자동으로 Python 코드베이스에 통합됨
- 다양한 블록 알고리듬을 처리할 수 있도록 *스트리밍 API* 가 범용적으로 설계되어 검증됨
- *메모리 할당 실패 처리* ,
AVX2 컴…
------------------------------
https://news.hada.io/topic?id=20423&utm_source=googlechat&utm_medium=bot&utm_campaign=1834

0
0
1

還記得前幾天搜尋民調新聞時,搜出一整串“關稅導致罷免支持度降低”(大部分是親共媒體),心中是有一些煩惱。但昨天走過一整排的罷免攤位,看到大家士氣高昂且努力的樣子,想到他們都是沒拿錢的志工,內心頓時充滿感動與放心,覺得台灣還是有很多正常人XD
我蠻慶幸自己有來這裡走走,因為這次感受很不一樣,我是第一次在集會上喊中華民國萬歲,喊的有點彆扭,但也不是那麼難以說出口,內心那個分裂的國家好像正在慢慢的融合起來,這真的還要謝謝現在的國民黨,我們能報答的,就是努力的把他掃進歷史的塵埃,連回收都不要。

0
0
1
0
0
1
0
1
0
1

모든게 히틀러, 파시즘을 뚜렷하게 가리키고 있음. 건강하지 못함은 애국이 아니다. 건강 보험 예산을 소모하는 것은 애국자가 할 일이 아니다...

RE: https://bsky.app/profile/did:plc:hsb3iofnzkivsla3htzvmgfb/post/3ln6hvlt6lc2u

0
0
0
1
0
0

轉載 活水帳冊房 FB

m.facebook.com/story.php?story

藍白真正會嚇破膽的是這場大罷免造勢,隨處可見青天白日滿地紅旗。

「獨立建國」、「法理建國」、「臺灣是臺灣人的臺灣」,青天白日滿地紅旗與這些旗子並存,一起揮舞。沒有人互相敵視,沒有語言衝突。
..........

這是不是一個新的互相溝通和理解的契機呢?我們是不是能夠團結起來,更看清楚藍白現在的狂態呢?
...........

沒有政黨主導主辦(「民進黨主辦的話,會準備這麼多青天白日滿地紅旗?」請用這句話堵住質疑者的嘴),這場公民發起的造勢,值得載入臺灣政治史。就如同這次活動的主訴:大罷免,不是因為恨,恰恰是因為對這塊土地的愛。

然而連署還要繼續拚下去,因為要通過的門檻真的很高,不容許放鬆。如果這次罷免狀況理想,被拉下來的立委有整整七年可以不用看到他們的嘴臉;但如果不理想,他們會立法打造出更高的罷免門檻來自保(已經有法案已經擬好在排隊了)!

今天的造勢非常成功,然而罷免的進度不容樂觀,請別猶豫,去填罷免!

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

As someone who has developed several software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the is .

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 . 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.

3
6
1