What is Hackers' Pub?

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

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

People with #FreeSoftware experience make excellent workers! Learn how you can advertise your position on our #job page: https://u.fsf.org/46v

RE: https://muenchen.social/@joerg_spengler/116025272874053189

Ist ein #Parteiverbot 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?
https://www.confessio.de/index.php/artikel/1517

#PRÜF #Freiheit #Demokratie #AfDVerbot

지인캐

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

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

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

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

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

回顧一下那段時間：

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

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

作為參考，
1981年7月3日：陳文成命案
1984年10月15日：劉宜良命案（江南案）
都是在那段時期。

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

근데 울집은 손님 받기엔 정말 너무 작다. 방 하나만 더 있었음 좋겠다

Efficiency is the removal of redundancy. Redundancy is a necessary element of resilient systems. The unbounded search for efficiency has one result: brittleness.

Honestly this is increasingly tempting

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

我要瘋掉了

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

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

이제 곧 중학생 되는데 방학 때 혼자 배낭매고 오라 그랬음ㅋㅋ

The JSTOR Collective, (2026 Feb 7), the first rule of Cite Club: tell everyone where you learned about Cite Club [Text post], Tumblr. https://www.tumblr.com/communities/jstor-collective/post/807401944948883456?source=share

초등학생 조카랑 놀기 너무 재밌다

지금도 일본어를 몰라서 27번이라는 것과 중길이라는 것 정도밖에 해석을 못하겠다 (Claude한테 이미지를 그대로 넣어봤는데 환각이 너무 심합니다. 텍스트로 변환해서 번역해볼 테니 잠시만 기다려주세요)

我要瘋掉了

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

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

Bit late to the party with Feb’s scone of the month. It’s rhubarb crumble, and it’s a particularly tasty one #food #Scones

British drivers over 70 to face eye tests every three years

Link: https://www.bbc.com/news/articles/c205nxy0p31o
Discussion: https://news.ycombinator.com/item?id=46924813

@cafouCafou, influenceur fraise Mme Sirène demande un payement en gratouilles

今天買了一件覺得好看的拼布外套，而且還有八折優惠🥺🥺

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

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.

#JSONLD #fedidev

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

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.

#JSONLD #fedidev

@april@fedi.fabrykajabo.liNomz @jasiew@lewacki.space @oaj@mastodon.com.plOliwier Jaszczyszyn

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.

Google staff call for firm to cut ties with ICE

Link: https://www.bbc.com/news/articles/cvgjg98vmzjo
Discussion: https://news.ycombinator.com/item?id=46924544

RE: https://mastodon.social/@stroughtonsmith/116030146417314239

Existential crise, in the sense that all of a sudden I can make everything I've ever wanted to make.

Ulven is sceptical about Caturday today but we aren’t! Hope you’re having a mogginificent day!

🥩

What day/night will be the wildest party on your island?”

@dansup
Check also @berlinfedidayBerliner Fediverse Tag - September in Berlin

근데 왜 다른 사람들은 그걸 잘 안 쓰는 걸까요...?

근데 너무 오랜만에 이래라 저래라 잔소리 폭탄 맞으니까 어질어질하다

The people of Minnesota are fucking marvellous.

They're deliberately putting Mexican flags on their cars so that CBP/DHS waste time chasing them. They're calling it ICE fishing 🤣 ✊

#Minnesota #SolidarityIsBeautiful #USPolitics

속상한데 속상하지 않으려고 노력 중. 누구 잘못도 아니고 피할 수도 없는 일이었다 생각

When will people figure out that machines working in an unconstrained human environment need AGI to be fully autonomous?

There are no shortcuts.

https://www.theregister.com/2026/01/30/road_sign_hijack_ai/

I just got cursed out for asking someone to CW political posts.

Apparently, I'm what's wrong with the Fediverse.

So… am I?

Okay, I'd like to know more.

生成AIにあいまいな文章生成させようとしたけど、やっぱり自分で書かないと駄目だってなってる

When will people figure out that machines working in an unconstrained human environment need AGI to be fully autonomous?

There are no shortcuts.

https://www.theregister.com/2026/01/30/road_sign_hijack_ai/

"Final Answer: Your GMI idea at the 200% level is improbable if funded solely by billionaire taxes. However, a GMI targeted at the 100% poverty line is completely financially viable if we actually enforced the tax code and enacted a wealth tax. We could end official poverty tomorrow; we just choose not to." 🤔

요즘 절찬리에 펨보이 타락중인데 꽤 재밌음

and here's a bit of a post-mortem of the first year of good internet!

https://library.xandra.cc/starting-a-print-magazine/

@djangonews is a wonderful resource for the #Django community. I'm always excited to read the latest edition. This week's included some love for https://django-antipatterns.com

The site includes extra context on JsonResponse(safe=) which clarifies why it's important. Thankfully, browsers have gotten better to the point where this feature (and antipattern) can be removed!

https://www.better-simple.com/django/2026/02/06/a-riskier-jsonresponse/

Does anyone in my Django world use Scalingo for hosting? I hadn't heard of it until today, but they've been around for over a decade!

It seems like every time Heroku comes closer to actually closing its doors, we learn about new hosting options.

#Python #Django

https://scalingo.com

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

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.

#JSONLD #fedidev