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
1

True, and this is why the pundit class keeps getting shocked by stuff normal protesters saw coming a mile away. To know what's going on in the US, you have to be a) brave enough to think straight in a crisis and b) plugged into the real resistance.

That's all it takes, but most of the pundits are flunking on both.

@sanderlinr says "I don't think polling is capturing how close millions of us are to grabbing torches and pitchforks."
0
0
0
1
0
1
2
0
0
0
0
0
1
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0

雖然明天上班大概又會很痛苦

但這兩天去了想去的地方,買了想買和好看的東西,曬到滿意的照片,有和家人見面,有約好和朋友出來

有好好活著的感覺

0
0
0

あと自分の側にできる流出対策といったら、SNS運営会社に自分のことを洗いざらい教えないのは一つの手です🤐

例えばユーザー登録で必須になっていない項目は埋めなくていいし、投稿内容をSNSごとに分けてリスクを分散させることもできる。

こうやって情報を限定しておけば、万が一データが漏洩しても傷が浅くて済みます。運営会社があまり信用できないならそっちの対策にもなる🛡️

ネット上のいかなるサイトであれ、画面の向こうには必ず誰か運営者がいるのだと意識することはいつでも大事。

ネット上のセキュリティに100%はないけれど、安全性にはどんな人が何のためにどこから資金を得て運営しているのかによって雲泥の差がある。

例えばFedibirdの運営者はのえるさんで、ユーザーからの寄付を運営費の足しにされてます :Shiropuyo_hohoemi:

0
0
0

看了好几个BBC的纪录片,都是从香港联络到大陆,香港的记者、香港的NGO组织还在做最后一道防线。
比如偷拍这个纪录片中提到,有一个香港的NGO组织在帮忙下架那些被偷拍的影片,受害者很多来自大陆。 ​​​

0
0
0
0
0
0
0
0

어처구니없는 이야기: 스마트폰이 벽돌이 되면 냉동고에 넣어서 냉동시킨 상태로 응급 복구를 할 수 있다고 해서 냉동실에 스마트폰을 넣어놓고 방치하자......................냉동고 안에서 알람이 울리기 시작했다. 이게 왜 됨?

RE: https://bsky.app/profile/did:plc:ijc4yb24tysgjiaiib2ldgyk/post/3mee24rgvys2v

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

@hongminhee洪 民憙 (Hong Minhee) :nonbinary: I'm reading this thread as a relative noob, but what I see again and again: almost no one "properly" implents largely because is hard but also because the spec itself is unclear. Most people who get stuff done have to go off-spec to actually ship.

This seems a fundamental weakness of the - and that disregarding the limitations coming from base architecture. Seems to pose a mid/long-term existential threat.

What can we do to help improve things?

0
0
0
0
0
0