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.
6일만에 출근하려니 싫다
『정진명의 굳이 써서 남기는 생각』에 새 블로그 포스팅이 올라왔습니다: 마마수제만두의 산동짜장면, 고기부추 물만두, 소룡포, 가지고기튀김
마마수제만두의 산동짜장면, 고기부추 물만두, 소룡포, ...
3대 특검법, 형사소송법 개정안, 상법 개정안, 방송 3법, 노란봉투법, 양곡관리법. 윤석열 정부 내내 ‘거부권’(재의요구권) 장벽에 막혀 좌절됐던 법안들이 재추진되고 있습니다.
‘대통령 재판정지’·상법·방송3법...민주 입법 속도전...
Most software engineers focus on efficiency rather than effectiveness.
What matters more: solving a $1M problem with 90% efficiency, or solving a $1K problem with 99.999% efficiency?
Efficiency matters, but there are infinite wants and scarce people to solve them.
Differentiate yourself by knowing when to stop optimizing and help your org deploy time more effectively.
각종 여론조사는 모수를 보정하게 되는데 그 보정하는 값이 이전 여론조사에 의존한다면 어떻게 되는거지?
인구 통계야 정확하게 있다지만 정치쪽은 평소 지지하는 정당을 가지고 보정을 할텐데 그 평소 지지하는 정당은 국가에서 각 잡고 통계를 낸 게 아니라 이전에 똑같이 여론조사 해서 나온 결과고 그것도 성별/나이/지역으로 보정한 결과일거잖아
Beachpatrol - 브라우저의 일상 업무를 자동화하는 CLI 허브
------------------------------
- 일반 웹 브라우저를 *CLI 기반 자동화 브라우저* 로 대체할 수 있게 해주는 오픈소스
- 이메일·은행·SNS 자동 체크, 파일 자동 다운로드, 텍스트 추출 및 저장
- 폼 자동 입력, 사이트 맞춤 메시지 수집, Bash·Python 스크립트 연동
- *일상적인 웹 브라우징 환경 전체를 자동화* 할 수 있음
- Play…
------------------------------
https://news.hada.io/topic?id=21349&utm_source=googlechat&utm_medium=bot&utm_campaign=1834
3-2-1 rule for backing up the Self
3-2-1 rule for backing up the Self
繼續整理臉書
看到 2012 興起的 Google +，那時候也滿好玩的，也因為幾乎大家都有帳號，跑過去玩都是順手，但也是說不玩就不玩的收攤了。
但至少，沒有玩到發臭。
2015.06.09
邊緣人是珍貴的，沒有我們，世界是無法被丈量的。
I found out it is harder to publish an app to the Play Store than is is to publish an app to the App Store. To publish to the Play Store you need 12 testers. Does Google know how hard it is to make friends?
If you are on #Android want to try out a super simple #map app with a gorgeous map of the Netherlands (map5topo.nl), DM me your e-mail and I will add you as a tester.
@hollo 같은 얘기입니다ㅋㅋ근데 하스켈에서 '요청을 보내되 응답은 다른 쓰레드에서 받기'란 이펙트를 구분할수가 없지 않나요? 새 쓰레드를 띄울수있는 이펙트랑은 좀 다르다고 생각합니다. 새로 쓰레드를 띄우면 거기서 무제한으로 요청/응답을 할수있는데 그걸 바라진 않아서요.
French journalist Yanis Mhamdi (working for 
@blast_info) aboard the #Madleen, at 1:49 AM CEST:
“I am a journalist, and after covering the Freedom Flotilla convoy for a week, my arrest by the Israeli army is imminent. Humanitarians and journalists should not be arrested. I call on all my colleagues to mobilize.”
So it's happened: Israel has seemingly arrested the crew of a humanitarian ship, including a European MP onboard, in international waters, and in complete disregard for international law.
Their impunity is through the roof.
魂の腐乱
TrinityNYC:
"現地の住民が皆、LAで「暴動」など起こってないと言ってるのに、ああしてわざと兵力を投入して暴力を煽り、戦争状態を作り上げて挑発し、平和的なプロテストが文字通りの暴動に発展するのを舌なめずりして待ってるんだ。暴動が起これば、戒厳令を発して、楯突く者を一網打尽に逮捕投獄して、他の都市への見せしめにできるからな。" — Bluesky
https://bsky.app/profile/frankie0320.bsky.social/post/3lr53yeu5ps2u
北捷不管悠遊卡做自己！最快 10 月支援 Apple Pay「快速模式」免解鎖進站！ - 蘋果仁 - 果仁 iPhone/iOS/好物推薦科技媒體 https://applealmond.com/posts/280668
do you think wilson had house as a headmate after all these years
人生410は激しいので418くらい擬態にしておこう #とは
무슨 일이지...?
GeekNews Weekly #309 Mary Meeker의 "AI" 트렌드 보고서
------------------------------
“인터넷의 여왕”이라는 별명을 가진 Mary Meeker는 1995년부터 거의 매년 Internet Trends라는 보고서를 통해 인터넷 산업의 다양한 발전상을 조망해 왔습니다. 2018년 클라이너 퍼킨스를 떠나 자신의 VC인 Bond Capital을 창업한 이후로는, 더 바빠진 탓인지 2019년을 마지막으로 인터넷 트렌드 보고서가 나오지 않아 아…
------------------------------
https://news.hada.io/weekly/202523?utm_source=googlechat&utm_medium=bot&utm_campaign=1834
Since when was it here at Southern Cross Station?
#Daniel’s Donuts
北捷不管悠遊卡做自己！最快 10 月支援 Apple Pay「快速模式」免解鎖進站！ - 蘋果仁 - 果仁 iPhone/iOS/好物推薦科技媒體 https://applealmond.com/posts/280668
@hwalyeopsu활엽수 
하지만 월요일은
너무 고된 날이니까요…
おくすりのんだにょ！
그래 ...... 나도 퍼플렉시티한테 많이 의존하니 퍼플렉시티가 좀 자주 블로그를 긁어가도 할말없지. ....아니 잠만. 님들은 유료잖아. 난 무료고. 이자식들이...!!?
洪 民憙 (Hong Minhee) 
shared the below article:
julian @julian@community.nodebb.org
<p>In February 2025, I presented a topic at FOSDEM in Brussels entitled <a href="https://spectra.video/w/xwCSYfZh1mJY64zJ9GngbE" rel="nofollow ugc">The Fediverse is Quiet — Let's Fix That!</a> In it, I outlined several "hard problems" endemic to the fediverse, focusing on one particular complaint that is often voiced by newcomers and oldtimers alike; that the fediverse is quiet because you don't ever see the full conversation due to some design considerations made at the protocol level.</p> <p>Since then there have been a number of approaches toward solving this problem, and it is worth spending the time to review the two main approaches and their pros and cons.</p> <p><em>N.B. I have a conflict of interest in this subject as I am a proponent of one of the approaches (FEP 7888/f228) outlined below. <strong>This article should be considered an opinion piece.</strong></em></p> <hr /> <h2>Crawling of the reply tree</h2> <p>First discussed 15 April 2024 and merged into Mastodon core on 12 Mar 2025, <a href="https://neuromatch.social/@jonny">@<bdi>jonny@neuromatch.social</bdi></a> pioneered this approach to "fetch all replies" by crawling the entirety of the reply tree. When presented with an object, the Mastodon service would make a call to the <code>context</code> endpoint, and if supported(?) would start to crawl the reply tree via the <code>replies</code> collection, generating a list of statuses to ingest.</p> <p>This approach is advantageous for a number of reasons, most notably that <code>inReplyTo</code> and <code>replies</code> are <strong>properties that are ubiquitous</strong> among nearly all implementations and their usage tends not to differ markedly from one another.</p> <p><em>N.B. I am not certain whether the service would crawl <em>up</em> the <code>inReplyTo</code> chain first, before expanding downwards, or whether <code>context</code> is set in intermediate and leaf nodes that point to the root-level object.</em></p> <p>One disadvantage is this approach's <strong>susceptibility to network fragility</strong>. If a single node in the reply tree is temporarily or permanently inaccessible, then every branch of the reply tree emanating from that node is inaccessible as well.</p> <p>Another disadvantage is the reliance on intermediate nodes for indexing the reply tree. The amount of work (CPU time, network requests, etc.) scales linearly with the size of the reply tree, and more importantly <strong>discoverability of new branches of the reply tree necessitate a re-crawl of the entire reply tree</strong>. For fast-growing trees, this may not net you a complete tree depending on when you begin crawling.</p> <p>Lastly, in the ideal case, a full tree crawl would net you a complete tree with all branches and leaves. Great!</p> <p>Mastodon is the sole implementor of this approach, although it is not proprietary or special to Mastodon by any means.</p> <h2>FEP 7888/f228, or FEP 171b/f228</h2> <p>Summarized by <a href="https://mitra.social/users/silverpill">@<bdi>silverpill@mitra.social</bdi></a> in <a href="https://w3id.org/fep/f228" rel="nofollow ugc">FEP f228</a> (as an extension of FEPs <a href="https://w3id.org/fep/7888" rel="nofollow ugc">7888</a> by <a href="https://mastodon.social/@trwnh">@<bdi>trwnh@mastodon.social</bdi></a> and <a href="https://w3id.org/fep/171b" rel="nofollow ugc">171b</a> by <a href="https://fediversity.site/channel/mikedev">@<bdi>mikedev@fediversity.site</bdi></a>), this conversational backfill approach defines the concept of a "context owner" as referenced by compatible nodes in the tree. This context owner returns an <code>OrderedCollection</code> containing all members of the context.</p> <p>A major advantage of this approach centers around the pseudo-centralization provided by the context owner. This "single source of truth" maintains the index of objects (or activities) and supplies their IDs (or signed full activities) on request. Individual implementations then retrieve the objects (or activities). It is important to note that <strong>should the context owner become inaccessible, then backfill is no longer possible to achieve</strong>. On the other hand, a dead or unresponsive intermediate node will not affect the ability of the downstream nodes to be processed.</p> <p>The context owner is only able to respond with a list of objects/activities that it knows about. This does mean that downstream branches that do not propagate upwards back to the root will not be known to the context owner.</p> <p>Additionally, consumers are also able to query the context owner for an index without needing to crawl the entire reply tree. The ability to de-duplicate objects at this level reduces the overall number of network requests (and CPU time from parsing retrieved objects) required, <strong>making this approach relatively more efficient</strong>.</p> <p>Additional synchronization methods (via id hashsums) could be leveraged to reduce the number of network calls further.</p> <p>A number of implementors follow this approach to backfill, including NodeBB, Discourse, WordPress, Frequency, Mitra, and Streams. Additional implementors like Lemmy and Piefed have expressed interest.</p> <p>One technical hurdle with this approach is technical buy-in from implementors themselves. Unlike crawling a reply tree, this approach only works when the context owner supports it, and thus should be combined with various other backfill strategies as part of an overall conversational backfill solution.</p> <h2>Conclusion</h2> <p>2025 is shaping up to be an exciting year for resolving some of the harder technical and social problems endemic to the open social web/fediverse. It is this author's opinion that we may be able to make good headway towards resolving the "quiet fedi" problem with these two approaches.</p> <p>It is important to note that <strong>neither approach conflicts with the other</strong>. Implementations are free to utilise multiple approaches to backfill a conversation. Both methods presented here have pros and cons, and a combination of both (or more) could be key.</p> <p>Feel free to use this as a starting point for discussions regarding either approach. Does one speak to you more than the other? Are the cons of either approach significant enough for you to disregard it? What other approaches or changes could you recommend?</p>
Read more →밥찵여
TrinityNYC:
"現地の住民が皆、LAで「暴動」など起こってないと言ってるのに、ああしてわざと兵力を投入して暴力を煽り、戦争状態を作り上げて挑発し、平和的なプロテストが文字通りの暴動に発展するのを舌なめずりして待ってるんだ。暴動が起これば、戒厳令を発して、楯突く者を一網打尽に逮捕投獄して、他の都市への見せしめにできるからな。" — Bluesky
https://bsky.app/profile/frankie0320.bsky.social/post/3lr53yeu5ps2u
alright, i making misskey plugin to change your note to uwu lang
here:
✧✦Catherine✦✧
MJ+
Frédéric Jacobs
SparklingOutlaw🍉
もこもこもっこもこ
/// @ 0.12.4
### {
name: "Uwuified",
version: "1.0.0",
author: "Misa",
description: "Change text to UwU~",
permissions: ["write:notes"]
}
Plugin:register_post_form_action("UwU", @(note, rewrite) {
let text = note.text
let text1 = text.replace("r", "w")
let text2 = text1.replace("l", "w")
let text3 = text2.replace("na", "nya")
let result = `{text3} uwu~`
Mk:dialog("Uwuified!", "UwU~", "success")
rewrite("text", result)
})
just small circles 🕊 shared the below article:
julian @julian@community.nodebb.org
<p>In February 2025, I presented a topic at FOSDEM in Brussels entitled <a href="https://spectra.video/w/xwCSYfZh1mJY64zJ9GngbE" rel="nofollow ugc">The Fediverse is Quiet — Let's Fix That!</a> In it, I outlined several "hard problems" endemic to the fediverse, focusing on one particular complaint that is often voiced by newcomers and oldtimers alike; that the fediverse is quiet because you don't ever see the full conversation due to some design considerations made at the protocol level.</p> <p>Since then there have been a number of approaches toward solving this problem, and it is worth spending the time to review the two main approaches and their pros and cons.</p> <p><em>N.B. I have a conflict of interest in this subject as I am a proponent of one of the approaches (FEP 7888/f228) outlined below. <strong>This article should be considered an opinion piece.</strong></em></p> <hr /> <h2>Crawling of the reply tree</h2> <p>First discussed 15 April 2024 and merged into Mastodon core on 12 Mar 2025, <a href="https://neuromatch.social/@jonny">@<bdi>jonny@neuromatch.social</bdi></a> pioneered this approach to "fetch all replies" by crawling the entirety of the reply tree. When presented with an object, the Mastodon service would make a call to the <code>context</code> endpoint, and if supported(?) would start to crawl the reply tree via the <code>replies</code> collection, generating a list of statuses to ingest.</p> <p>This approach is advantageous for a number of reasons, most notably that <code>inReplyTo</code> and <code>replies</code> are <strong>properties that are ubiquitous</strong> among nearly all implementations and their usage tends not to differ markedly from one another.</p> <p><em>N.B. I am not certain whether the service would crawl <em>up</em> the <code>inReplyTo</code> chain first, before expanding downwards, or whether <code>context</code> is set in intermediate and leaf nodes that point to the root-level object.</em></p> <p>One disadvantage is this approach's <strong>susceptibility to network fragility</strong>. If a single node in the reply tree is temporarily or permanently inaccessible, then every branch of the reply tree emanating from that node is inaccessible as well.</p> <p>Another disadvantage is the reliance on intermediate nodes for indexing the reply tree. The amount of work (CPU time, network requests, etc.) scales linearly with the size of the reply tree, and more importantly <strong>discoverability of new branches of the reply tree necessitate a re-crawl of the entire reply tree</strong>. For fast-growing trees, this may not net you a complete tree depending on when you begin crawling.</p> <p>Lastly, in the ideal case, a full tree crawl would net you a complete tree with all branches and leaves. Great!</p> <p>Mastodon is the sole implementor of this approach, although it is not proprietary or special to Mastodon by any means.</p> <h2>FEP 7888/f228, or FEP 171b/f228</h2> <p>Summarized by <a href="https://mitra.social/users/silverpill">@<bdi>silverpill@mitra.social</bdi></a> in <a href="https://w3id.org/fep/f228" rel="nofollow ugc">FEP f228</a> (as an extension of FEPs <a href="https://w3id.org/fep/7888" rel="nofollow ugc">7888</a> by <a href="https://mastodon.social/@trwnh">@<bdi>trwnh@mastodon.social</bdi></a> and <a href="https://w3id.org/fep/171b" rel="nofollow ugc">171b</a> by <a href="https://fediversity.site/channel/mikedev">@<bdi>mikedev@fediversity.site</bdi></a>), this conversational backfill approach defines the concept of a "context owner" as referenced by compatible nodes in the tree. This context owner returns an <code>OrderedCollection</code> containing all members of the context.</p> <p>A major advantage of this approach centers around the pseudo-centralization provided by the context owner. This "single source of truth" maintains the index of objects (or activities) and supplies their IDs (or signed full activities) on request. Individual implementations then retrieve the objects (or activities). It is important to note that <strong>should the context owner become inaccessible, then backfill is no longer possible to achieve</strong>. On the other hand, a dead or unresponsive intermediate node will not affect the ability of the downstream nodes to be processed.</p> <p>The context owner is only able to respond with a list of objects/activities that it knows about. This does mean that downstream branches that do not propagate upwards back to the root will not be known to the context owner.</p> <p>Additionally, consumers are also able to query the context owner for an index without needing to crawl the entire reply tree. The ability to de-duplicate objects at this level reduces the overall number of network requests (and CPU time from parsing retrieved objects) required, <strong>making this approach relatively more efficient</strong>.</p> <p>Additional synchronization methods (via id hashsums) could be leveraged to reduce the number of network calls further.</p> <p>A number of implementors follow this approach to backfill, including NodeBB, Discourse, WordPress, Frequency, Mitra, and Streams. Additional implementors like Lemmy and Piefed have expressed interest.</p> <p>One technical hurdle with this approach is technical buy-in from implementors themselves. Unlike crawling a reply tree, this approach only works when the context owner supports it, and thus should be combined with various other backfill strategies as part of an overall conversational backfill solution.</p> <h2>Conclusion</h2> <p>2025 is shaping up to be an exciting year for resolving some of the harder technical and social problems endemic to the open social web/fediverse. It is this author's opinion that we may be able to make good headway towards resolving the "quiet fedi" problem with these two approaches.</p> <p>It is important to note that <strong>neither approach conflicts with the other</strong>. Implementations are free to utilise multiple approaches to backfill a conversation. Both methods presented here have pros and cons, and a combination of both (or more) could be key.</p> <p>Feel free to use this as a starting point for discussions regarding either approach. Does one speak to you more than the other? Are the cons of either approach significant enough for you to disregard it? What other approaches or changes could you recommend?</p>
Read more →日本語で韓国のことを発信しているYouTuberの「きばるん」「デボちゃん」「李ファミリー」の政治系コンテンツは、完全に韓国右派の主張と同じで、自分も害しかないと感じていた
XユーザーのKoki Ito 高麗大学・政治外交学科さん: 「この｢可哀想な人｣という認識は先の兵庫県知事選でそっくりそのまま斎藤元彦に適用されていた｢表現｣で偏向した情報が創り出す｢世界観の恐怖｣にただただ怯えるしかなかった。名指しして申し訳ないが、きばるん・デボちゃんの政治コンテンツは｢百害あって一利なし｣だと断言しておきたい。」 / X: https://x.com/_imyour_koki/status/1881692848183275693
しゅいろママに今年の
조금 이른 감이 없잖아 있지만, 오늘이 금요일이었으면 좋겠어
쟈-지메이도 히-루챤
아 오늘 슬로뉴스 헤드라인 좋았다. 노회찬 보고 싶네...
昨晚有比較早上床，不過還是玩了一會手機才睡
入睡好像比之前的星期日晚上容易，但有覺得比較淺眠
而且鬧鐘響之前一段時間已經醒來無法繼續睡，以至於起來還是跟失眠的時候差不多累
覺得可以加個 #失眠小站 的tag 
ねむい…
んう
ラーベちゃんがエアリプをしてくれるようになった
"現代世界を築き上げる中で排出される廃棄物が、人類の未来に不可逆的な影響を与えようとしていることを示唆している"
人類のごみ、「わずか35年」で岩石化 英海岸で発見 | Forbes JAPAN 公式サイト（フォーブス ジャパン） https://forbesjapan.com/articles/detail/79686/page2
自分の感覚としてSNSは情報収集にちょっと娯楽が流れてくるようなもんで捉えてる この感覚は人とは違うのかもなと最近の気づきになってる（遅）
@bitofabother Yeah that one was good!
@mekkaokerekemekka okereke 
I have Cuban relatives in Florida. They are Republican (ofc), identify as white, and feel American. I’ve tried to understand how that works within a society that sees them as brown and inmigrants, but can’t get insights from them. It is very complex.
Also, some of them are diabetics and pay thousands for their insulin (that would cost them zero in my country), but “Democrats are communists and Social Security is a scam”.
It is hard to wrap my euro mind around it :/
@bitofabother It's good, it's SUPER slow burn but so rewarding and it feels so good to just simmer in it
Misskeyカード発送業務する
So I've run out the end of some of the yuri manga I've been reading and I'm trying to decide whether to start a new yuri or to finish out Kowloon Generic Romance, which is really good. Wait, maybe I've convinced myself I should just keep going with Kowloon Generic Romance
ひさびさSNSを見たら、林原めぐみ陰謀論者化が飛び込んできて悲しすぎる…
花の塔 - さユり (花の塔)
#NowPlaying
わー！林原めぐみさんのブログ、デボちゃんに、きばるんって！完全に排外主義、陰謀論に染まってるじゃないですか！
i don't get how there are people who hate jews, like that's the most random ass group ever, might've as well picked people who buy salted butter while you're at it
position: sticky が効かない原因を CSS 仕様から読み解く – スクロールコンテナーと包含ブロック - Katashin .info
세랄이 
GENKI
しゅいろ
