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

日本自民黨確定眾議院席次單獨過半情勢
19:32

根據本台NHK在投票站進行的出口民調結果和情勢分析顯示,在本次日本國會眾議院選舉中,自民黨有可能單獨贏得300個席次,遠遠超過半數的233個席次,預計高市政權將繼續執政。
www3.nhk.or.jp/nhkworld/zt/new

0

神鬼妖怪院開票速報に注目もっ!​:foxjump:
八百万神党に龍神党も強いし付喪神党も強いも…っ!
鬼神党もなかなか議席を取ってるも。
西洋魔術党や現代妖怪党っていう新たな政党もございますもっ。

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

리듬게임에 대한 네거티브

불타는 ​:birdsite:​를 보고 느낀것은 최근 서비스를 시작한 중국 리듬게임은 일반적인 사용자에게 비슷한 가격대의 일반적인 인기 게임을 두고 선택 해야할 이유를 잘 설명하지 못했다고 생각합니다. 그저 게임 안해봤다고 의견을 말하는 것이 잘못되었다고 하는거 보면 정작 자신들도 게임을 해보지 않은 사람에게 추천할 이유를 잘 설명하지 못한다고 생각합니다. ​:blobcat_googly_thisisfine:

0
0
0

Wine-Staging 11.2 Brings More Patches To Help Adobe Photoshop On Linux

Building off Friday's release of Wine 11.2 is now Wine-Staging 11.2 as this experimental/testing version of Wine with hundreds of extra patches that have yet to be introduced in upstream proper for this open-source software enabling Windows games and applications on Linux. Notable in this bi-weekly update are more patches for continuing to improve the Adobe Photoshop installer support on Linux...
phoronix.com/news/Wine-Staging

0
0
0
0
1
0
0

今天去了集中營,天氣如圖,大約幾百公尺以外的地方就因為濃霧看不清楚了,有的地方我也沒有逛,好幾個告示牌寫了博物館維修中,冬天土地濕滑,要逛請自行負責人身安全。
因為天氣太差了,雪融化之後跟泥巴融合在一起到處都是水坑,石子容易掉進鞋子裡面。但我還是臉被凍得發麻,有時候不小心踩進雪裡那個黏糊糊的感覺真的很糟,還會留一個棕色的腳印。
總之這樣的天氣之下去看了園區部分的地方,這一根根柱子是因為墳墓被破壞了所以只好用這個方式紀念去世的人。這不是紀念去世的猶太人,而是這個猶太集中營被改建為蘇聯在東德的勞改營之後死在裡面的納粹黨員。
他們的處境一樣很差,蘇聯時期東德的人被迫對此保持沈默,與此相對的是西德的人可以談論這件事情,但也有人用來替納粹辯護。

0
0
0
0
1
1
1
1
0

AI coding tools, why they're a bad idea, work

The heads of my department at work have been pushing AI coding tools, but the internal adoption rate hasn't been as strong as they hoped. They've picked someone to go around and do interviews with various engineers to try to get an understanding of the various internal opinions on these tools. I'm being interviewed tomorrow, and want to impart my interviewer with the strongest negative takeaway on the subject I can muster. The more points and sources for those points I have going into this, the better.

So fedi: what am I missing here? Anything noteworthy that I should include in my list?

- The power and water consumption of AI products should be reason enough to not use them.
- The fact that they're built with stolen materials should be reason enough to not use them.
- My main value add at the company is not the speed at which I write code, but my ability to understand the team's code.
- Anthropic released a paper recently showing that using AI coding tools harms understanding.
- There was that paper last spring that showed that programmers consistently overestimate the productivity impact of AI coding tools, and the impact is actually negative.
- Key copyright issues around AI generated code remain unresolved, which is a massive legal liability.
- The entire industry is sitting atop a massive bubble, it will be extremely painful for us when it pops, and us using these tools adds more fuel to the fire.
- These tools are
heavily subsidized right now, and there's no way that lasts forever. Usage fees will surely be massively increased in the future.
- If these truly were wonder tools of massive productivity boosts, we'd see the gains in the open source community, but to date this hasn't happened. There's not a massive boom of new and successful open source projects.
- The wave of slop issues and PRs filed against open source projects demonstrates how these add little value and a ton of noise.
- The wave of scrapers making the lives of website owners hard should be reason enough to not use these tools.
- People internally have already openly complained about low quality AI code from their colleagues, we have no reason to believe the issue won't get worse if adoption increases.
- We have no evidence to believe the narrative that these tools will improve radically over the coming months/years.
- It's bizarre to have a top-down push to use a specific tool. It's always been up to the engineers to use what tools they feel make them most productive. If I think I'm more productive without AI coding tools, and my work performance is still good, then just leave me alone. No one has been trying to pressure me into using the Rust language server, for example.
- The way that AI coding tools are consistently used to justify massive layoffs across the industry leaves a really bad impression that the point of all of this isn't productivity, but to punish workers. My team has been really understaffed for a couple years now because of layoffs, and this is
not helping.
- Frankly all of the ethical and practical reasons to avoid these tools are really clear to me, and the way many of my coworkers have been uncritically adopting these tools is both really depressing and makes me think less of them.

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