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

코딩 에이전트를 풀로 활용해서 나보단 코딩 에이전트가 만들고 있는 TypeScript와 Rust를 위한 스프레드시트 라이브러리. 타입스크립트에서 xlsx 파일을 다루는 라이브러리들 쓰다가 너무 괴로워서 만들게 되었다. (GitHub Actions 배포 이슈는 내일 마저 잡는걸로…)

https://github.com/Nebu1eto/sheetkit

5
0
1
1
0
0

ChatGPT Pro 구독은 이제 그만하고... 덕덕고에서 제공하는 duck.ai 로 갈아타는것이 좋은것 같음 보니까 완전 최신 모델은 아닌데 사용자 데이터를 훈련에 쓰지 않도록 명시되어있고 사생활 보호가 더 잘된다고 함 가격도 더 싸고 좋음 한글도 잘되는거 같음... 여전히 ChatGPT 5.1 모델을 쓸수 있음 5.2가 아닌것은 아쉽지만 아마 OpenAI에서 허용을 안해주는것 같음 ㅎㅎ Proton에서도 비슷한 서비스를 제공하는데 ChatGPT는 없는것 같음.

DuckDuckGo AI Chat at DuckDuck...

0
1

【MedHerbs紐西蘭醫學級腸道益生菌特約】美國佛羅里達州近日氣溫一度降至零下,州政府趁天氣寒冷,鏟除具生態威脅的綠鬣蜥。有網紅發現綠鬣蜥後未有交由政府處理,而是帶回家煮熟食用,事後更將過程上載至社交網。網民形容,起初以為網紅只是開玩笑,沒想過他會拍成如此詳盡的影片。

綠鬣蜥遇上攝氏7度或以下低溫會不能動彈,直至回暖前,其身體機能暫時停止運作,更會從樹上掉落。州政府上周日(1日)一連兩天展開行動,趁牠們進入假死狀態,抓捕這群來自熱帶地區、影響環境及經濟的外來入侵物種。

當地野生動物保護委員會與滅蟲公司聯手,最終尋獲超過5,000隻綠鬣蜥,並於稍後安排人道毀滅。網紅Gray Davis同樣發現綠鬣蜥蹤影,但他未有交出,而是將牠帶回家處置。他將蜥蜴去皮後,加入蒜頭、洋蔥、月桂葉等汆水再煎香,最後放入墨西哥薄餅皮之中。解剖期間,Davis還發現綠鬣蜥體內有約20顆卵子,決定烚至半熟,並與牛油果打成醬同吃。

0
0
0
0
0
1
1
0
1
1
0

회사 윗대가리...정말 아는척하려면 공부를 하던지 찾아보려는 노력이나 하라고.

작년까지도 본인이 git을 모르니까 개발과정에서 git 못쓰게 오만 방해를 하더니

내가 고집스럽게 git은 기본이라고 했더니만 git=소스업로드 기능 이라고 잘못 이해했는지
오만군데다 '업로드' 용어 대신 git이라고 쓰면서 아는척 중임 -_-

아이고 머리야.

0

다카이치 사나에 총리가 이끄는 일본 집권 자민당이 9일 최종 집계가 끝난 중의원 선거(하원·8일 실시)에서 단독으로 ‘개헌 발의 정족수’ 310석 이상을 확보하는 ‘역사적 승리’를 거뒀습니다. 제 1, 3야당이 합당 형태로 만든 신당 ‘중도개혁연합’은 기존 의석보다 120여석이 줄어드는 참패를 당했습니다.

‘다카이치 열풍’ 타고 자민당, ‘316석’ 단독 개헌...

0
1

I’ve just added social media interaction displays to my micro posts. Likes and comments from Bluesky and the Fediverse will now appear directly on my site.

If the same comment appears on multiple platforms, it will be merged using Levenshtein distance.

A micro post on my site, with a red box indicating 8 likes and a comments section showing a comment from Andrew James.
0

I'm cursed and I get the most cursed bugs, a thread

- Showing UI from Wine services is broken and racy
- Wine's syscall handler is racy and randomly triggers huge memory leaks in Unity apps
- Shared texture import in DXVK is racy and randomly breaks Spout2 resizing
- Nouveau dma-buf is racy with import into another GPU and crashes context on migration

(spot the pattern...)

- winepreloader breaks Flatpak LD_AUDIT thing sometimes because it temporarily restricts stack size and the audit lib calls a recursive glibc function that runs out of stack if path is too long (????)
- rundll32 doesn't accept quoted paths (it just takes the tail of args as path) but if you pass spaces in a UNIX arg Wine quotes it so it breaks, fix is to run through cmd.exe (???)
- Importing Nvidia-prop allocated dmabufs into non-Nvidia is just broken??
- steam-runtime breaks GBM entirely

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

2
26
1
1
0
0
0
1
1
1
0
0
0

그러니까 이게
기존에 클플 없는 상태에서 인증서 인증받고 -> 클플 연결 -> 재인증할 날짜가 되니까 클플이 막아버림
이 원인으로...
기존의 인증서를 삭제하고 클플이 있는 상태에서 인증할 수 있게 재인증을 했어요
szkorean.net/2020/05/cloudflar

마지막에 다 했는데 왜안돼......!!!! 하다가 nginx 리로드를 안한 걸 깨닫고 평화롭게 해결

0

ㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋㅋ
성난 블롭캣이 몰려온다!!!

0
0
0