What is Hackers' Pub?

夕飯のデザートにソアン・パブディ食べた。美味

해커스펍! 흥한다!

Hackers' Pub 쓰고 계신 분들 중에서, 자신의 Hackers' Pub 계정을 연합우주(fediverse)뿐만 아니라 Bluesky에도 노출하고 그쪽 사람들과 교류하고 싶으신 분이 있다면, 상단 검색창에 @bsky.brid.gy@bsky.brid.gy을 검색하셔서 나오는 프로필을 팔로해 보세요. 그리고 1분 정도 뒤에 Bluesky에서 본인ID.hackers.pub.ap.brid.gy로 검색하면 본인의 Hackers' Pub 계정이 Bluesky에서도 보이는 걸 확인하실 수 있을 겁니다.

Wordle 1,361 2/6*

🟩🟨🟨⬜⬜
🟩🟩🟩🟩🟩

WordleBot
Skill 74/99
Luck 92/99

I should buy a lottery ticket

Previously @holloHollo used cryptography for authorization codes and access tokens, this had some implications such as preventing us from implementing PKCE, which requires state to be tracked between the authorize screen and the authorization code token exchange.

So this paves the path to supporting PKCE in Hollo.

Whew that was a lot for a Sunday afternoon: Implementing the usage of Access Grants for OAuth in @holloHollo

It's not done yet, but it's showing promise.

https://github.com/fedify-dev/hollo/pull/130

Previously @holloHollo used cryptography for authorization codes and access tokens, this had some implications such as preventing us from implementing PKCE, which requires state to be tracked between the authorize screen and the authorization code token exchange.

So this paves the path to supporting PKCE in Hollo.

Whew that was a lot for a Sunday afternoon: Implementing the usage of Access Grants for OAuth in @holloHollo

It's not done yet, but it's showing promise.

https://github.com/fedify-dev/hollo/pull/130

Previously @holloHollo used cryptography for authorization codes and access tokens, this had some implications such as preventing us from implementing PKCE, which requires state to be tracked between the authorize screen and the authorization code token exchange.

So this paves the path to supporting PKCE in Hollo.

Whew that was a lot for a Sunday afternoon: Implementing the usage of Access Grants for OAuth in @holloHollo

It's not done yet, but it's showing promise.

https://github.com/fedify-dev/hollo/pull/130

OW2con'25: join the open source community annual conference

📍June 17-18, in Paris Châtillon
The program committee is now evaluating a great bunch of quality proposals.

🙏 Yann Lechelle, Matthieu Porte, Alberto Pace and Artur Queiroz. Our Keynote Speakers will share their view on OSS and responsible AI: https://www.ow2con.org/view/2025/Keynotes_Speakers

🙏 Thanks to Orange, Worteks, BPCE, Centreon, Linagora, Thales, MAIF and NGI. Join them as OW2con'25 sponsor!
👉 Sponsoring opportunities: https://www.ow2con.org/view/2025/Sponsors

ランチはお気に入りのレストラン、GuidfordのPadbury's Cafe Restaurant。ちょうど切らしていたワインを買いにNIKOLA Wineryに行く途中。

わたしは海老のオムレツ、サラダ添え。友だちはオーストラリアの定番、誰がこんなに食うんだというほど盛りだくさんの朝ゴハンセット。ポーチドエッグ2個ｋソーセージ2本、ベーコン、チェリートマト、ほうれん草のソテー、きのこのソテー、パン、バター。これにいつものOlive Farm白ワインを1本。

最後にここの名物ふわふわのパンケーキを半分ずつ。
#eatout #そとごはん #パース #オーストラリア

WIP #orgmode (9.8pre) x #rnote

#emacs

https://theonion.com/trump-says-recession-unfortunate-but-necessary-step-to-get-to-depression/

https://theonion.com/trump-says-recession-unfortunate-but-necessary-step-to-get-to-depression/

2011年3月11日に日本で発生した東日本大震災から14年。あの日を境に、災害時に役に立つ地理空間情報とはなにかを突き詰めるといった、自分のやりたいことが明確になり今に至っています。答えはシンプルで、『災害時には普段使いしているものしか役に立たない』ことと『災害時は普段当たり前にあるインフラが使えなくなる』という至極真っ当なこの２つの条件で機能する地理空間情報とは何か。そんな漠然とした、けれどもグローバルに通用する答え現在も追い求めて、イタリア・ミラノの地で研究に励んでいます。

14年前はできなかったことも多かったけれど、今、自信を持って言えることは、我々はあの時よりもできることが確実に増えている。あの頃無名だった OpenStreetMap は現在、世界の地理空間情報のインフラを支えている。まだまだ課題も多いけれど、解決すべき課題が明確に見えていることはとてもやりがいがある。

政治的には世界各地で苦しいニュースも飛び交っているけれども、我々はきっと世の中をもっとよくすることができる。

Photo: U.S. Navy photo, Public Domain
#一億総伊能化

@PossiblyMaxMax Great question about our queue implementation! Fedify doesn't actually create separate physical queues, but rather uses a single logical queue where each message contains its own destination information.

For resource management, we generally rely on the underlying queue implementation (Redis, PostgreSQL, etc.) to handle concurrent processing efficiently. Since version 1.0.0, we've introduced ParallelMessageQueue which processes multiple messages concurrently with a configurable worker count—usually set close to your CPU core count for IO-bound operations.

We don't spin up new queues dynamically; instead, we focus on making the message processing scalable. You can control the parallelism level when using ParallelMessageQueue, and for high-volume instances, you can horizontally scale by running multiple worker processes that connect to the same shared queue backend.

This approach keeps the architecture simpler while still allowing for good throughput and resource utilization that can scale with your instance size.

Just released @fedify/markdown-it-mention v0.3.0! This update adds support for bare handles (e.g., @username without domain) with the new localDomain option, allowing you to specify the domain for these shortened mentions.

Install via npm, Bun, or Deno:

npm add @fedify/markdown-it-mention@0.3.0
bun add @fedify/markdown-it-mention@0.3.0
deno add jsr:@fedify/markdown-it-mention@0.3.0

Just released @fedify/markdown-it-mention v0.3.0! This update adds support for bare handles (e.g., @username without domain) with the new localDomain option, allowing you to specify the domain for these shortened mentions.

Install via npm, Bun, or Deno:

npm add @fedify/markdown-it-mention@0.3.0
bun add @fedify/markdown-it-mention@0.3.0
deno add jsr:@fedify/markdown-it-mention@0.3.0

@PossiblyMaxMax Great question about our queue implementation! Fedify doesn't actually create separate physical queues, but rather uses a single logical queue where each message contains its own destination information.

For resource management, we generally rely on the underlying queue implementation (Redis, PostgreSQL, etc.) to handle concurrent processing efficiently. Since version 1.0.0, we've introduced ParallelMessageQueue which processes multiple messages concurrently with a configurable worker count—usually set close to your CPU core count for IO-bound operations.

We don't spin up new queues dynamically; instead, we focus on making the message processing scalable. You can control the parallelism level when using ParallelMessageQueue, and for high-volume instances, you can horizontally scale by running multiple worker processes that connect to the same shared queue backend.

This approach keeps the architecture simpler while still allowing for good throughput and resource utilization that can scale with your instance size.

At #FediverseHouse, after @pluralisticCory Doctorow 's talk, I came up and thanked him for speaking. We've never met before in person, so I asked if we could do a selfie.

#やぁようこそ、ioへ。このイラストはサービスだから、まずは見て落ち着いてほしい。

@PossiblyMaxMax Great question about our queue implementation! Fedify doesn't actually create separate physical queues, but rather uses a single logical queue where each message contains its own destination information.

For resource management, we generally rely on the underlying queue implementation (Redis, PostgreSQL, etc.) to handle concurrent processing efficiently. Since version 1.0.0, we've introduced ParallelMessageQueue which processes multiple messages concurrently with a configurable worker count—usually set close to your CPU core count for IO-bound operations.

We don't spin up new queues dynamically; instead, we focus on making the message processing scalable. You can control the parallelism level when using ParallelMessageQueue, and for high-volume instances, you can horizontally scale by running multiple worker processes that connect to the same shared queue backend.

This approach keeps the architecture simpler while still allowing for good throughput and resource utilization that can scale with your instance size.

그래도 트젠 인권은 존재하고 소중합니다. 블스에 이 말 하는 사람 한명은 늘리려고ㅎㅎ

CloudflareのBotプロテクション（Turnstile）にAPIが弾かれてたみたいです
エンドポイントを直で叩いてTurnstileを通過したら見れるようになりました
明らかに設定おかしいやろ

RE: https://misskey.io/notes/a57x4svhesn502zn

昨日お菓子作りしたのでアホみたいな量の洗い物が溜まっている。どうしようか

CloudflareのBotプロテクション（Turnstile）にAPIが弾かれてたみたいです
エンドポイントを直で叩いてTurnstileを通過したら見れるようになりました
明らかに設定おかしいやろ

RE: https://misskey.io/notes/a57x4svhesn502zn

ビットコインは死ぬ前に現金化しておこう！

그러한 불평등inequality이 결과적으로 건강 악화와 조기 사망을 야기함은 압도적으로 많은 증거에 의해 입증되었으며 가장 최근에는 전염병으로 운명을 달리한 영국과 미국의 코로나바이러스감염증-19Covid-19 희생자들의 사례에서도 극명하게 드러난 사실이다. 더욱이 불평등이 폭력을 발생시키기도 한다는 것은 많은 서구 국가에 존재하는 체제적 인종주의systemic racism의 한 측면 즉 법 집행기관과 소수민족 공동체 사이 관계만 봐도 지난 수십 년에 걸쳐 명백해진 바다. 다수의 서구 국가-오스트레일리아, 영국, 프랑스, 미국에서는 소수자minorities가 경찰에 의해 수감된 수와 사망한 수 모두에서 과다대표되는over-represented 경우가 흔하다. 세계에서 〔현지〕 선주민 수감률이 가장 높은 국가가 오스트레일리아임을 알면 놀랄 사람이 많을 것이다.
-필립 드와이어·마크 S. 미칼레『우리 본성의 악한 천사』중에서

X見れないけどおま環かしら

たぶん日本の皆さんにとって
３月１１日は
一生忘れられない日でしょう。
災害でお亡くなりになった皆さんの
ご冥福をお祈りします。

RE: https://mustard.blog/users/thx/statuses/114143319297578550

プラグイン書くぐらいならmisskey弄る

頭痛いわね

オタクに優しいギャルなんていない。
オタクに優しいんだったらみんなに優しいギャルになる

早く寝るか

あ〜

気がついたら近くにいるドッキリしようかなと

RE: https://misskey.io/notes/a57w9jv9e2zv0j7f

#Calculemus: Reto f(f(f(b))) = f(b). https://jaalonso.github.io/calculemus/posts/2020/01/24-reto/ #IsabelleHOL #Lógica #Matemática

あったかい

​​

ねみ

にゃあ

핑커와 피케티를 예로 들어보자. 두 저자는 각기 전하는 목적과 메시지가 전혀 다르다. 피케티는 어째서 자본주의가 세계의 불평등을 일으키는 주요 동인의 하나인지, 어떻게 극심한 불평등이 민주주의적 가치의 기반을 약화시킬 수 있는 불만 요소를 만들어내는지 입증하고자 한다. 《우리 본성의 선한 천사》와 700쪽이나 되는 2018년 후속작 《지금 다시 계몽: 이성, 과학, 휴머니즘, 그리고 진보를 말하다Enlightenment Now: The Case for Reason, Science, Humanism, and Progress》에서 핑커가 보여준 세계관은 피케티의 그것과 정반대다. 핑커의 두 책은 자본주의를, 더 정확히는 핑커가 "온화한 상업gentle commerce"이라고 이름 붙인 것을 격찬한다. 핑커는 이에 더해 다른 사회과학자들이 의견 일치를 본 것에 반해서 경제 불평등-즉 빈곤-이 폭력의 한 형태임을 부인하기까지 한다.

안녕하세요! 2025년 다이스페스타를 앞두고, 신간 룰북의 수요조사(통판 포함)로 찾아뵙게 되었습니다. (~03/31)
이번에 발매될 작품은 아래 세 작품입니다!

·모테몬!!
·회색성기담
·마녀와 짐승과 둘만의 여행

샘플 페이지 ▶ https://blueflowerpub.tistory.com/51
수요조사 링크 ▶ https://tmm.im/d/5638

brb launching a movement:

https://github.com/fasterthanlime/free-of-syn

結構する時間とお金と情報がない

いうてしららにゃんへのドッキリは考えて入るんですよ。

お夕飯食べた

Misskeyはフロントだけで完結できるのあまりないかも？

基本Misskeyの設定作るときってバックエンドもいじらないといけないので。