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

4인 파티 던전 액션 RPG였는데, 이런 포지션의 게임은 마비노기 영웅전이 하고 있었고... 아니 차라리 영웅전처럼 스핀오프로 내놓았으면 어땠으려나? 일단 넘버링이 달리면 사람들은 이전 작에서 연결되는걸 기대하니까... 같은 생각을 했던 그런 게임. 결국 세상에 못나왔지만.

0
0
0

we have a phrase in the labor movement: "don't panic, organize"

if we apply it, it works every time

it quells existential dread, builds solidarity, and makes things better for the working class

remember, "rebellions are built on hope"

don't let THE MAN get u down

we can do amazing things if we bring our care, joy, kindness, and equanimity to the fore

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

그나저나 마비노기 모바일에 나오가 말하는 "연결됐어"의 대사는 과거 마비노기2 아레나의 트레일러에서 들은것 같은 기억이 나서 검색해보니까, 그러네, 그때도 "연결됐어" 라는 말을 했네. youtu.be/BC5_yQRINHI?...

Mabinogi II: Arena - Official ...

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
0

NPR: "...“This is MYOC,” Laffey said.

In Lenexa police parlance, MYOC is shorthand for “make your own case.” With no arrest warrant for Ashworth, police were looking for any reason to stop him.
... Chief Schmitz described MYOC this way: “You need to build your own probable cause, your own reasonable suspicion. It's pretty much that, make your own case.”

Kubic, from the ACLU, is especially worried about that.

“The idea that you can essentially just make something up to throw against the wall and see if it sticks to be able to go after someone, is a really chilling and dangerous thing,” he said..."

0
0
0
1
0
0

cleaning up some personal projects I worked on in the past months and won't have much time for when my new job starts (Monday):

**cosmo** - a fast command line tool for converting data into GeoJSON(seq) or parquet.

Another one of those you say? Sure, but this one takes the best of some of the existing tools and combines them into one:
1. speed
2. scale (entire planet with ease on a 16GB laptop)
3. really good data filtering and transformation using YAML.

codeberg.org/mvexel/cosmo

0

LLMとAI駆動開発によってコードベースを理解することなく一見それらしく見えるが品質がきわめて低いパッチを量産することが容易になった今、FOSSプロジェクトはレビューで低品質なコントリビューションをふるいにかけるのが難しくなってきた。そこで、ユーザーの二値評価をファイルとして記録し、プロジェクト間でweb of trustを共有できるようにしてはどうかというアイデアがこれ。

github.com/mitchellh/vouch

0
0
0

As an addendum, let me emphasize: if someone is making 10^{5.5} dollars per year, they're rich. My point is that economic disparity is so incredibly bad in the US that being "rich" doesn't mean one has anything meaningfully in common with "owner-class rich" in terms of political power *or* security with respect to having basic needs met. It is a mistake for someone who is rich to think that it is not in their best interest to show solidarity with other laborers.

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

Note: Spout2PW requires AMD GCN5 (Vega) or newer GPUs due to a missing Mesa feature in older ones! If you have an RX Vega or 4-digit RX GPU you should be fine. Any Ryzen APU should be fine too (Zen cores).

gitlab.freedesktop.org/mesa/me

I'm going to add verbose error messages so users know when there's a problem.

Nvidia cards can also have similar issues, but I think that's mostly due to old or not properly configured drivers.

If you're having issues where it silently doesn't work, please wait for the next update which will show proper error messages in this case.

0
1
1
1
1

So just in case anyone missed it, I want to spell this out for you. The point of using FPS as ICE agents is that FPS is stocked full of troops from EriK Prince's private army (now called "Academi" but formerly called "Blackwater"). This means that carrying out ethnic cleansing can dump money directly into the pockets of America's version of the Wagner Group (side from, of course GEO Group).

It also means that there can be an alternative chain of command that exists outside of official channels. ICE is already bad enough, but similar people have worked as mercenaries for a long time. Having an established chain of command over armed occupiers, one based entirely on economic incentives, one that can't be legally monitored or audited, one that's completely outside of the government, should be especially worrying.

The bit reason J6 didn't go as planned is that Erik Prince wasn't behind it. Now there are troops with experience occupying American cities who can be called directly via Erik when Trump wants to make sure he doesn't lose again. And Erik won't back out at the last minute, because he's already seen that there will be no consequences for participating in a coup... if the time comes.

0
2
1
1

I've been watching the 1970s Canadian scifi show The Starlost on YouTube, having never heard of it before but it was mentioned on Bluesky as a wacky show. It's low budget and awkward but kind of interesting youtu.be/tNm0K-N4x7g

0