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

Keir Starmer warned his cabinet against an “overly deferential” approach to the Welsh, Scottish and Northern Irish governments, telling ministers they should be prepared to make spending decisions “even when devolved governments may oppose this”, according to a leaked memo.

0
0
0
0
0
1

가끔 아무 게임이나 테스트로만 해볼까해서 예전에 설치해본 게임중 하나가 '명조' 인데 이 미친게임은 간만에 들어갈 때마다 XXGB 단위의 패치를 한다. 게임 자체가 방대하다는건 알겠는데 최적화가 좀 필요할 것 같아보이네 😥

0
0
0
0

[보도자료] 손솔 의원, 본회의 대미투자특별법 반대토론 "투자의 책임은 아무도 지지 않고, 부담은 오롯이 국민에게 돌아가게 됩니다" jinboparty.com/pages/?p=286... 3,500억 달러 규모의 대미 투자가 국내에 어떤 영향을 미칠지에 대한 검토도 없이 국회는 미국이 제시한 일정에 맞추기 위해 이 법안을 서둘러 처리했습니다. 대한민국의 산업 정책과 국민의 재정에 영향을 미칠 수 있는 법안을 이렇게 처리하는 것은 결코 자랑스러운 일이 아닙니다. 무책임한 것입니다.

0
0
0

한편 여성 작가의 약진은 세계적인 현상이고, 여기에 관해서는 전에 미국쪽 사람들의 가설을 들은 적이 있다. 출판이 비인기 직종이 되면서 임금이 내려가자 기존의 남초 직장에서 여초 직장으로 변하고, 작품을 선정하는 편집자들도 여성이 주류가 되었는데, 남자 편집자들이 바글바글하던 시절 남자 작가들이 선택되던 것과 같이, 여성 편집자가 늘어나자 여성 작가들이 선택되게 되었다는 주장. 단지 작가의 성별을 보고 출간을 결정한다는 얘기가 아니라, 편집자가 공감하기 좋은 작품이 유리해진다는 얘기.

RE: https://bsky.app/profile/did:plc:fl6xvsneko2e7wryimmdyum6/post/3mgttqddp7s2c

0
0

Now that I have Openbox on FreeBSD 15 tuned to how I want it on my older i5 mac mini, features like window shade (show/hide) and mouse wheel desktop switching make it very difficult to want to use anything else.

Openbox is so incredibly small and efficient (i3 even more), I don't understand how some choose to install bloated KDE or Gnome instead on a BSD.

0
1

하 도저히 윈도우 알림 포함된 패키징을 못하겠어서(ㅠㅠ) 제미나이한테 또 짬때렸구요... 이렇게 되면 배포파일은 제 프로그램이 아니라는 생각이 들어서 그냥 1차 지인 한정 무료배포 하겠습니다... 난 딸깍이 하기싫어 원 포스트가서 멘션남겨주시면 내일 최종 테스트 후에 디엠으로 파일 드릴게요!! 관심 가져주셔서 감사합니다!

0
0
0
0

I'm writing this in English.

Not because English is my first language—it isn't. I'm writing this in English because if I wrote it in Korean, the people I'm addressing would run it through an outdated translator, misread it, and respond to something I never said. The responsibility for that mistranslation would fall on me. It always does.

This is the thing Eugen Rochko's post misses, despite its good intentions.

@GargronEugen Rochko argues that LLMs are no substitute for human translators, and that people who think otherwise don't actually rely on translation. He's right about some of this. A machine-translated novel is not the same as one rendered by a skilled human translator. But the argument rests on a premise that only makes sense from a certain position: that translation is primarily about quality, about the aesthetic experience of reading literature in another language.

For many of us, translation is first about access.

The professional translation market doesn't scale to cover everything. It never has. What gets translated—and into which languages—follows the logic of cultural hegemony. Works from dominant Western languages flow outward, translated into everything. Works from East Asian languages trickle in, selectively, slowly, on someone else's schedule. The asymmetry isn't incidental; it's structural.

@GargronEugen Rochko notes, fairly, that machine translation existed decades before LLMs. But this is only half the story, and which half matters depends entirely on which languages you're talking about. European language pairs were reasonably serviceable with older tools. Korean–English, Japanese–English, Chinese–English? Genuinely usable translation for these pairs arrived with the LLM era. Treating “machine translation” as a monolithic technology with a uniform history erases the experience of everyone whose language sits far from the Indo-European center.

There's also something uncomfortable in the framing of the button-press thought experiment: “I would erase LLMs even if it took machine translation with it.” For someone whose language has always been peripheral, that button looks very different. It's not an abstract philosophical position; it's a statement about whose access to information is expendable.

I want to be clear: none of this is an argument that LLMs are good, or that the harms @GargronEugen Rochko describes aren't real. They are. But a critique of AI doesn't become more universal by ignoring whose languages have always been on the margins. If anything, a serious critique of AI's political economy should be more attentive to those asymmetries, not less.

The fact that I'm writing this in English, carefully, so it won't be misread—that's not incidental to my argument. That is my argument.

5
13
0
0
0
0

404media.co/pinterest-is-drown

Pinterest is getting slammed with low-effort AI content that many users find boring or ugly, and its automated moderation is messing things up too — flagging normal posts and even banning people by mistake.

Creators are annoyed, feeds feel cluttered, and asking the company for fixes is a headache.

0
0
1

고인물 다음에 썩은물이라지만 그보다 더 무서운 게 자기는 물에서 나왔다는 자칭 탈덕들입니다. 그들은 대부분 물과 공기를 구분하지 못하는 상태입니다. 딴 물에 들어갔을 수는 있지만... 🤣😇🤦

0
0
0

working on a better method to build FreeBSD base packages. now every package has its own subdirectory, e.g. src/packages/cron, with a normal Makefile using the new bsd.pkg.mk:

WORLDPACKAGE= cron
SUBPACKAGES= dbg

UCLSRC= common.ucl

.include <bsd.pkg.mk>

common.ucl (or whatever you call it) replaces the old UCL files in release/packages/ucl/, and if needed, you can do something like "URLSRC.dbg=dbg.ucl" to use a subpackage-specific UCL.

src/packages/Makefile builds all of these using bsd.subdir.mk, so everything is automatically parallelised and works much more like how we build the rest of the system. (if you want to see something fun, have a look at how Makefile.inc1 does this right now using ${_PKGS}...)

all the *.pkg files are created in <objdir>/packages/<package>/ (like you'd expect) and staged to the repo using a 'stagepackage' target. this means we can eventually support something like this:

% make -C packages/cron clean all installpackage

... to install/upgrade a package from source without having to build the repo first.

another advantage of this (and the reason i started on it now) is that it lets the package Makefile do any build-specific customisation required for the UCL, such as changing dependencies based on src.conf options, which will be required for an LLVM change Ed is working on. in future, this should also let us do other things like staging and building sets in a much cleaner way.

i've been meaning to do this for a long time, so hopefully i can actually get it landed...

0
0
0
1
0
1
0
19
0
0
0
0
0
0
0
0
0
0
0
3
0