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
0
0
0
1
0
0
0

Typing a lot causes flare ups of the health issues I’ve been having (and still getting to bottom of). The next day will usually consist of pins and needles and shooting pains up and down my arm.

And while LLMs are problematic for various reasons - LLMs plus modern voice recognition can really help me reduce my typing. I have to remember to force myself to use voice (muscle memory is a bitch), but it works extremely well when I do.

0
0

This is an immensely significant document that continues to get virtually no attention in US media—but lots abroad. In Jul 2015, Epstein arranged a meeting between a known highest-level Russian intel operative, Sergey Belyakov and Peter Thiel, the man who owns Palantir, a key contractor to the US intelligence community. Under US law, Thiel, as a holder of high level security clearances, was required to report this contact to USG. It does not appear he did so.

bsky.app/profile/robertscottho

0
0
0
0
1
0
0

1.0.0-rc-2 has been published. In this version, you can connect your domain to create your unique account identity. The first time, it will send a Move activity so you don't lose your followers/following. Then you will have an identity that no longer depends on the relays, and you'll be free to move between relays whenever you want.

More about custom domains: holos.social/custom-domains

Download: holos.social/signup

Release notes: codeberg.org/tom79/Holos-App/r

0
0
0

Well, that's a new one. 🤪

Saw somebody posting a huge diatribe on LinkedIn where she basically accused every "digital" artist of hypocrisy when they're critical of the slop machines, because these new generative algorithms are apparently no different than Photoshop or 3D animation software. "The computer automates all the work for you!"

? ??

??? ?

Pushed back on that ignorant argument and got castigated with more nonsense.

Blocked and moving on! 😂

They're really running out of arguments… 🙃

0

今回の選挙、どこがどれだけ勝ったかとかより、やっぱり投票率が気になるなぁ。虚しい選挙だとおもうし、希望持っていない人のほうが多いんじゃないかなという気がして、そうなら投票率上がらないんじゃないかな。これがすごい投票率高かったら、自分がなにか見誤っているんだろうけど。

0

⚠️ PSA for anyone still on the mastodon.cloud server, you might want to move off there ASAP.

The server's admin hasn't posted since February 2023 and the server software is so old it's no longer supported for security updates.

There have been cases of extreme abuse posted by mastodon.cloud members and the admin took no action after months of reports. It is possibly an abandoned server, so you might want to transfer your account elsewhere while you still can.

If you need help transferring your account, there's a step-by-step guide at fedi.tips/transferring-your-ma

If you need help choosing a new server, see fedi.garden

0
0
0

If RGMII and GiveDirectly / OpenResearch can deliver 90+ cents on the dollar to those most in need via a simple means test (200% FPL), we create a benchmark that makes the government’s 70-cent efficiency look indefensible, while helping MORE people.

0

Swift Concurrency question (Swift 5, no approachable concurrency, nonisolated default actor isolation): when you add a simple Task block in a func in a view controller, I thought it always executes on the main thread if the callee invokes that func while on main. If you want to run code on a background thread, you implement an async func and call it in the Task, but the next line in the Task would still be back on main. Is that wrong, any line in the Task body can run on any thread??

0

今回の選挙、どこがどれだけ勝ったかとかより、やっぱり投票率が気になるなぁ。虚しい選挙だとおもうし、希望持っていない人のほうが多いんじゃないかなという気がして、そうなら投票率上がらないんじゃないかな。これがすごい投票率高かったら、自分がなにか見誤っているんだろうけど。

0
0

RE: muenchen.social/@joerg_spengle

Ist ein undemokratisch?

Nein. Es ist ein vom Grundgesetz vorgesehenes Instrument.
Es dient dazu die Demokratie vor ihrer Zerstörung zu schützen.

Aber das dauert… Drum sollte der Prüfauftrag sofort erteilt werden!
Aber davon sind die Nazis nicht weg… Nein, aber sie befehlen nicht mehr über Polizeikräfte oder bekommen Steuergeld oder Sendezeit im ÖRR…

Weitere Argumente:
Demokratie retten - AfD verbieten?
confessio.de/index.php/artikel

0
0

""簡嫚書同樣也在社群媒體上致歉,簡嫚書坦言沒有全面了解林家案件始末,當時以劇本判斷誤以為是伸張正義的劇本,所以才答應接演,簡嫚書也說自己難辭其咎。

不過簡嫚書提出當時與製作方簽約時,製作方在合約上有保證已取得拍攝本片的合法授權,在記者會後才知道製作方疑似未聯繫當事人、甚至未取得當事人授權的情況下就進行拍攝。

簡嫚書表示,在這段期間與與經紀團隊協同律師檢視工作合約內容,也確認了製作公司確實未取得事件當事人的授權。簡嫚書痛心自己成為加害人之一且深感羞愧,她坦言除了道歉也將採取實際行動,「製作方未取得當事人授權,違約在先,我將不再參與該片的任何後續」。"

"李千娜提到此片製作人郭木盛是過去拍戲而認識的前輩,自己因對這個角色共感所以接演,但忽略了事實本質,僅以經驗和對人的信任接受邀請,隨後才知道電影未經林義雄先生本人或家屬同意即進行拍攝。

李千娜說,自己沒有清楚查證,責無旁貸,同時也會針對此合作啟動更明確的調查和後續處理,也為未顧及當事人、家屬及整體事件帶給社會的傷害,致上最大的歉意,現在李千娜會把參與此片的全數片酬捐贈給林義雄、方素敏創辦的慈林教育基金會,強調並非為了換取諒解或平息爭議,而是希望能表達最基本的歉意。"

0

[世紀血案取材林宅血案掀波 楊小黎李千娜簡嫚書致歉⸺中央社](cna.com.tw/news/amov/202602070)

"楊小黎今天在社群媒體上致歉且提及自身想法,她說,最初洽談時製作方強調透過史料與不同立場呈現,楊小黎也依照指令完成拍攝,拍攝完才詢問製作方,是否已取得當事人或家屬的同意,沒想到得到的答案是沒有,「在得知這個事實後,我無法認同任何涉及真實歷史傷痛,卻未取得當事人及家屬理解與尊重的創作前提」。

楊小黎坦言,如果一開始就得知此事,會直接拒絕出演這個作品,「我也要為自己沒有主動確認這一點道歉,這是我的疏忽,對不起,我很抱歉」。"

0

[世紀血案取材林宅血案惹議 製作單位致歉認未取得林義雄授權⸺中央社](cna.com.tw/news/amov/202602070)

"國片「世紀血案」取材自1980年震驚全台、至今仍未偵破的「林宅血案」,事件涉及民進黨創黨元老林義雄一家,沒想到卻傳出未取得當事人及家屬授權。

製作單位費思兔文化娛樂與風尚國際文化傳媒今天發出聯合聲明,強調林義雄先生是受國人尊重的黨外運動前輩,其家中發生如此不幸事故,舉國哀悼,「我們絕無不敬之意,未能在第一時間登門請教,未來也將以尊重為前提,主動說明、並虛心聆聽任何可能的意見與指教。」"

//發表聲明但沒有具名。

回顧一下那段時間:

1979年12月10日:美麗島事件爆發
1979年12月13日:大逮捕,包括林義雄在內許多黨外人士被捕
1980年2月20日:警備總司令部軍法處以叛亂罪起訴林義雄(二條一唯一死刑)
1980年2月28日:美麗島案第一次開調查庭,林義雄被關在景美軍法看守所(今天國家人權博物館景美園區),妻子方素敏與助理田秋堇去旁聽開庭,大約中午時間,林義雄母親與雙胞胎女兒在家中遭到殺害,大女兒重傷倖存。當時林宅處於情治單位嚴密監控下,兇手幾乎不可能是一般強盜。

這是國民黨會用黑社會殺人製造恐怖的時代。

作為參考,
1981年7月3日:陳文成命案
1984年10月15日:劉宜良命案(江南案)
都是在那段時期。

台灣最後一個以二條一唯一死刑逮捕的政治犯是獨台會案幾名大學生,時間是1991年5月9日。之後在社會的反彈與學生群眾的救援下,立法院陸續廢止《懲治叛亂條例》與刑法100條拿掉「預備」叛亂罪,學生們才最終免訴。

0
0
0
0
0
0
0
0

So, France wants to send a letter to 29 years old, to remind them about how their biological clock can affect fertility.
Meanwhile, endometriosis, which is a disease that touches 1/10 person with a uterus and usually has a strong negative effect on fertility, is barely studied?

Yeah, love the irony

0

我要瘋掉了

難以想像這麼一個受盡折磨又年事已高的民主鬥士
此時此刻身邊的人該怎麼告訴他現在發生了什麼事

然後網傳的劇本中 (尚未證實真偽) 竟大膽誣指史明先生是幕後兇手
這到底是什麼新時代鬼故事
轉型正義
真的來不及了嗎

0
0
0
0
0
0
0

我要瘋掉了

難以想像這麼一個受盡折磨又年事已高的民主鬥士
此時此刻身邊的人該怎麼告訴他現在發生了什麼事

然後網傳的劇本中 (尚未證實真偽) 竟大膽誣指史明先生是幕後兇手
這到底是什麼新時代鬼故事
轉型正義
真的來不及了嗎

0
0
0
0
0

I have deeply mixed feelings about 's adoption of JSON-LD, as someone who's spent way too long dealing with it while building .

Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.

But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.

Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.

To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.

Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.

2
12
1

I have deeply mixed feelings about 's adoption of JSON-LD, as someone who's spent way too long dealing with it while building .

Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.

But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.

Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.

To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.

Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.

2
12
1
0
0

I'm starting to understand why the two words "means testing" are so triggering over on Reddit:

The "Means-Testing Industrial Complex": Private contractors like Deloitte and Equifax make billions running the eligibility systems for Medicaid and SNAP.

The Profit Incentive: In the business world, efficiency means "profit." For these contractors, complexity is profitable. The more complicated the eligibility rules, the more expensive the software and verification services they can sell to the state.

0
0
0
0
0
0
0