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

My blog post about how software rendered depth based occlusion culling in Block Game functions is out now!

enikofox.com/posts/software-re

Note! Any public or quiet public/unlisted replies to this toot will be shown as comments on the blog. If you don't want that please use followers only or private mention when replying

Software occlusion culling in Block Game

My GPU is the integrated Radeon Vega 8 that comes with my AMD Ryzen 7 5700G CPU. I tell you this so you know that my workstation is not a graphical computing powerhouse. It is, in fact, quite weak. To its credit my integrated GPU shows up as 48% faster on UserBenchmark than the GPU in my low end hardware target; a laptop I bought in 2012.That, and the fact I want my game to run well even on a potato, is why I recently decided to try my hand at writing a software rendered occlusion culling solution for the Block Game (working title) I’m developing as I’ve always been interested in the idea. Blocks and chunks are axis aligned cubes, which makes things easier, and block games tend to have a ton of hidden geometry in the form of underground caves. There are other ways to cull these, but the algorithms tend to be fairly complex and this seemed like a good way to avoid that complexity and stick with something very conceptually simple.In this post I’ll be explaining the development process and the solution that I eventually landed on. If you like you can also read the development thread I posted on Mastodon and Bluesky.Before I start though I’d like to say that this came out quite well, better than I expected. It runs in half a frame at 60 FPS or less (threaded, of course) and generally culls at least 50% of the chunks that survive frustum culling. Above ground, looking straight ahead at the horizon it’ll cull around between 50 and 60% of chunks, but indoors and below ground in caves it can cull upwards of 95% of chunks, resulting in framerates of 400+ even on my weak system. All around a resounding success, though it has some cases where it breaks down which I’ll touch on at the very end of this post.Comparison of depth occlusion culling on/off, off on left, on on right.

enikofox.com · Eniko does bad things to code

0
1
0
0
0
1
0

FEP-8c13: Context-Authority Routing with Object Integrity Proofs for Restricted Threads

dima skavish @skavish@socialhub.activitypub.rocks

I was writing a spec for how to handle replies in our project, and once I finished it, I realized it might be useful to others as well. There’s nothing fundamentally new here (as far as I know), it builds on existing specs, but brings them together into a single, coherent set of instructions with examples. It also makes certain logic and attributes mandatory (MUST) to reduce ambiguity and limit overly flexible interpretations

https://codeberg.org/skavish/fep/src/branch/fep-8c13/fep/8c13/fep-8c13.md

Please let me know if you notice any issues. Thanks!

Read more →
0
0
0
0
1
0
0
0
0
0

Federal agents filmed dragging a woman from her car in

By SAFIYAH RIDDLE, SARAH BRUMFIELD and HALLIE GOLDEN
Updated 9:44 PM EST, January 15, 2026

"A U.S. citizen on her way to a medical appointment in Minneapolis was dragged out of her car and detained by immigration officers, according to a statement released by the woman on Thursday, after a video of her arrest drew millions of views on social media.

"Aliya Rahman said she was brought to a detention center where she was denied medical care and lost consciousness. The Department of Homeland Security said she was an agitator who was obstructing agents conducting arrests in the area.

"That video is the latest in a deluge of online content that documents an intensifying across the midwestern city, as thousands of federal agents execute arrests amid protests in what local officials have likened to a 'federal invasion.' "

apnews.com/article/aliya-rahma

0
0
0
0

일론머스크는 죽었습니까? 일론머스크는 죽었습니까? 일론머스크는 죽었습니까? 비계기능은 얼마나 완성되었습니까? 비계기능은 얼마나 완성되었습니까? 비계기능은 얼마나 완성되었습니까?

0
1
0

Dear

We want to expand our team! @AaidanbirdThe Bird (recently promoted from moderator) and @McCullohMDChris McCulloh, MD ♿️(he/him) are our administrators, and I’m a mod! We’d like 2-3 more mods

We train all new mods/admins, previous experience is nice but not required — usually mod work is light, 10 hours or less monthly

This call is members only, but you can join our server if you’re disabled and interested!

Please get to know our rules: disabled.social/about

Apply to be a mod: newmodcall@disabled.social

0
0
0

I've never had an agent fail VCS conflict resolution yet. A modern VCS should automatically defer to agents for resolution and in addition to showing the conflict, show the proposed resolution with an easy way to say "yes/no/edit" in a tight CLI loop.

It doesn't require any smart prompting. It always figures it out and just does the right thing.

Examples:
ampcode.com/threads/T-019bc8a2

ampcode.com/threads/T-019bc8ad

0
0

Quick question...

I've been trying to fix a knackered old Dell laptop for my neighbour's 13 year old daughter. It was obviously important that it looks good.

But I've just spoken to a friend who gave me a Mac laptop for work (that's finished) which will obviously be way cooler (and I don't use it apart from for rolling joints).

So he's happy for me to give her the Mac, but it's a UK QWERTY keyboard. Is there any way to change to a French AZERTY keyboard expediently? She'll be really chuffed if we can do this.

Paging @iFixit

Boosts much appreciated!

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

🚨 Last call for our survey! 🚨 Are you a security researcher or journalist? We want to hear from you — please take this survey!

Dissent Doe at DataBreaches, and I, are running this survey to better understand the state of legal demands and criminal threats in cybersecurity.

Please help us by filling out this survey (and please share!)

forms.gle/yAiNNq2gTqE6ctWU8

Survey about legal and criminal threats experienced by journalists and security researchers

Researchers who try to responsibly disclose leaks, vulnerabilities, and other security breaches or mishaps may face legal threats or lawsuits. Similarly, journalists may find themselves threatened with lawsuits or other legal consequences if they report on leaks or breaches. Both researchers and journalists also face threats by criminals ("threat actors") if they report on them in ways the threat actors find unflattering or harmful. In our many years of reporting on leaks, breaches, and criminal gangs, DataBreaches.net and Zack Whittaker have often exchanged "war stories" about what threats we have received or had to contend with. After one particularly tiring week, we wanted to conduct a survey of researchers and journalists to ask about their experience with threats. We are using a broad definition of "researcher" to include self-defining or volunteer researchers (and not just academic or vendor-based researchers), as well as a broad definition of "journalist," to include bloggers and anyone who regularly reports on news and research, including commentary sites. Here are our questions, and we hope you will respond. Responses can be anonymous, but it will be helpful if you provide a real name or moniker and contact information, so we can follow up if we have questions. (Responses are encrypted in transmission and at-rest in line with Google's privacy policies. We plan to close this survey by end of day January 18, 2026.) Thank you for taking the time to complete this survey. (To report a survey bug, please reach out.)

docs.google.com · Google Docs

0

🚨 Last call for our survey! 🚨 Are you a security researcher or journalist? We want to hear from you — please take this survey!

Dissent Doe at DataBreaches, and I, are running this survey to better understand the state of legal demands and criminal threats in cybersecurity.

Please help us by filling out this survey (and please share!)

forms.gle/yAiNNq2gTqE6ctWU8

Survey about legal and criminal threats experienced by journalists and security researchers

Researchers who try to responsibly disclose leaks, vulnerabilities, and other security breaches or mishaps may face legal threats or lawsuits. Similarly, journalists may find themselves threatened with lawsuits or other legal consequences if they report on leaks or breaches. Both researchers and journalists also face threats by criminals ("threat actors") if they report on them in ways the threat actors find unflattering or harmful. In our many years of reporting on leaks, breaches, and criminal gangs, DataBreaches.net and Zack Whittaker have often exchanged "war stories" about what threats we have received or had to contend with. After one particularly tiring week, we wanted to conduct a survey of researchers and journalists to ask about their experience with threats. We are using a broad definition of "researcher" to include self-defining or volunteer researchers (and not just academic or vendor-based researchers), as well as a broad definition of "journalist," to include bloggers and anyone who regularly reports on news and research, including commentary sites. Here are our questions, and we hope you will respond. Responses can be anonymous, but it will be helpful if you provide a real name or moniker and contact information, so we can follow up if we have questions. (Responses are encrypted in transmission and at-rest in line with Google's privacy policies. We plan to close this survey by end of day January 18, 2026.) Thank you for taking the time to complete this survey. (To report a survey bug, please reach out.)

docs.google.com · Google Docs

0

A thought that popped into my head when I woke up at 4 am and couldn’t get back to sleep…

Imagine that AI/LLM tools were being marketed to workers as a way to do the same work more quickly and work fewer hours without telling their employers.

“Use ChatGPT to write your TPS reports, go home at lunchtime. Spend more time with your kids!” “Use Claude to write your code, turn 60-hour weeks into four-day weekends!” “Collect two paychecks by using AI! You can hold two jobs without the boss knowing the difference!”

Imagine if AI/LLM tools were not shareholder catnip, but a grassroots movement of tooling that workers were sharing with each other to work less. Same quality of output, but instead of being pushed top-down, being adopted to empower people to work less and “cheat” employers.

Imagine if unions were arguing for the right of workers to use LLMs as labor saving devices, instead of trying to protect members from their damage.

CEOs would be screaming bloody murder. There’d be an overnight industry in AI-detection tools and immediate bans on AI in the workplace. Instead of Microsoft CoPilot 365, Satya would be out promoting Microsoft SlopGuard - add ons that detect LLM tools running on Windows and prevent AI scrapers from harvesting your company’s valuable content for training.

The media would be running horror stories about the terrible trend of workers getting the same pay for working less, and the awful quality of LLM output. Maybe they’d still call them “hallucinations,” but it’d be in the terrified tone of 80s anti-drug PSAs.

What I’m trying to say in my sleep-deprived state is that you shouldn’t ignore the intent and ill effects of these tools. If they were good for you, shareholders would hate them.

You should understand that they’re anti-worker and anti-human. TPTB would be fighting them tooth and nail if their benefits were reversed. It doesn’t matter how good they get, or how interesting they are: the ultimate purpose of the industry behind them is to create less demand for labor and aggregate more wealth in fewer hands.

Unless you happen to be in a very very small club of ultra-wealthy tech bros, they’re not for you, they’re against you.

0
0
0

VRChat turns 12 today!

Happy Anniversary and thank you to our amazing community for being here with us.

Stroll around the updated VRChat Home world to see pictures from our history and take pictures with the cake.

Share your memories with us using the hashtag #VRC12Years ! We'll RT our favorites.

0