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

https://www.youtube.com/watch?v=vASNqX0wv_I

덜 선명한 렌즈는 고화소 바디에서 낭비인가? 라는 질문에, 그렇지 않다, 고화소 바디는 덜 선명한 렌즈에서도 저화소 대비 디테일이 더 좋으며 렌즈의 각종 수차들의 영향이 더 크지 않다고 설명하는 Simon d'Entremont의 영상.

렌즈의 샤프니스와 바디의 해상도는 각 다른 영역이고, 저화소 바디에서의 고급 렌즈 사용도 장점이 존재한다고. 고급 렌즈, 고화소 바디에 대해 고민하고 있는 분들이 참고하면 좋을 듯.

1

衆議院議席で与党が2/3を超えたので、法案が参議院で否決されても再可決可能。一方憲法は、両院で2/3の賛成の上、国民投票が必要。参院では与党が半数に届いていないので、成立させるには未達。ということか。

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

1월 하순부터 다양한 공적, 사적 불운이 찾아와 이미 온 몸과 정신이 일종의 비상 상태에 있는 와중에, 조금 전 스마트폰이 아무 예고 없이 벽돌이 되었고, 급하게 공기계로 갈아탄 상태. 인생 억까 구간이라는 생각을 지울 수가 없다.

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

大方の予想通り、衆院選は自民党の圧勝となりましたが、これは「首相が勝てそうなタイミングで衆院解散をした」結果に過ぎないので、与野党の勝因・敗因を分析する意味はあまりないと思います。これから議論すべきことは以下の3点だと、私は考えています。

1.首相の衆院解散権を法的に制限する
2.選挙期間を極端に短くできないようにする
3.インターネット(SNS)の選挙運動を規制する

現状では、以上の3点の制限がないので、首相が好きな時に衆院解散をできて、なおかつ超短期決戦で、インターネット(SNS)では言いたい放題という状況なので、政策議論が深まるはずもないのです。とにかく、現在の日本は「選挙が多すぎる」ので、もう少し、国会で熟議を尽くせるようにすべきではないでしょうか。

asahi.com/senkyo/shuinsen/

0
0
1

抱怨文

人跟人之間,常常因為誤會而對對方有情緒(生氣),甚至引發衝突。這個我可以理解。

但是在我解釋澄清了是誤會之後,基本的禮貌不是起碼要說一聲,「唉啊,不好意思。是我誤會你了。」

雖然我並不是很在意道歉這種事,但是對方一句話都不吭,連個「啊,原來是這樣。」都沒有,好像一切都沒有發生過,我還是會很生氣。

發生過的事情卻假裝沒有發生,這樣的情境就會讓我很生氣。

似乎也是一個過往的成長型創傷。我有不少被家人,被老師這樣對待的經驗。

0
0
0