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

Jaeyeol Lee shared the below article:

LogTape 1.1.0: Smarter buffering, seamless integration

洪 民憙 (Hong Minhee) @hongminhee@hackers.pub

LogTape 1.1.0 introduces smarter and more flexible logging with two major features. The first is "fingers crossed" logging, which buffers debug and low-level logs in memory and only outputs them when an error occurs, providing a complete sequence of events leading up to the problem. Category isolation prevents one component's errors from flushing unrelated logs, keeping logs focused and relevant. The second feature is direct log emission via the `Logger.emit()` method, which allows feeding logs from external systems like Kafka directly into LogTape while preserving original timestamps and metadata. This release also includes bug fixes and improvements across the ecosystem, such as fixes for potential data loss during high-volume logging and improved cross-runtime compatibility. Upgrading to 1.1.0 is backward-compatible and enhances debugging in production by providing complete context for every error without constant verbose logging.

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

국회 엘리베이터에서 만난 송언석, "그리 됐으면" 막말 입장 물었더니 omn.kr/2fab8 "기자 : (함께 엘리베이터에 타며) 정청래 민주당 대표가 '(연설 날) 그리 됐으면 좋았을 것'이라고 말한 '범인'으로 지목했는데 입장 있으신가요? 송언석 원내대표 : 식사하셨어요? 기자 : 네. 송언석 : 즐거운 점심시간 되길 바랍니다. 기자 : 한 번도 입장을 말씀 안 해주셔서. 궁금해서요. 송언석 : ..."

국회 엘리베이터에서 만난 송언석, "그리 됐으면" 막말...

0

McK shared the below article:

LogTape 1.1.0: Smarter buffering, seamless integration

洪 民憙 (Hong Minhee) @hongminhee@hackers.pub

LogTape 1.1.0 introduces smarter and more flexible logging with two major features. The first is "fingers crossed" logging, which buffers debug and low-level logs in memory and only outputs them when an error occurs, providing a complete sequence of events leading up to the problem. Category isolation prevents one component's errors from flushing unrelated logs, keeping logs focused and relevant. The second feature is direct log emission via the `Logger.emit()` method, which allows feeding logs from external systems like Kafka directly into LogTape while preserving original timestamps and metadata. This release also includes bug fixes and improvements across the ecosystem, such as fixes for potential data loss during high-volume logging and improved cross-runtime compatibility. Upgrading to 1.1.0 is backward-compatible and enhances debugging in production by providing complete context for every error without constant verbose logging.

Read more →
0
0
0

올만에 컴파일러 lexical analysis 설명 읽으니깐 짱 재밌으면서도 동시에 쓰여진 코드도 이해하려고 하니깐 머리가 터질 것 같군...닝겐이 자연어를 처리하는 과정도 재밌는데 기계가 입력 기호들을 처리하는 걸 들여다볼 수 있다는 사실 그 자체가 되게 신기한 것 같다. 전자는 언어라는 추상적 정보를 뭉탱이로 있다가 유링게슝하게 여러 층위로 쪼개서 (예: 통사, 의미) 순차적 혹은 병렬적으로 처리한다는 게 재밌고 후자는 기호를 임의의 단위로 쪼개는 과정들을 구현 수준에서 디테일하게 볼 수 있다는 게 짱 신기하다...여튼 머리도 식힐 겸 운동하러 가야지.

1
0
0
0
0
0
0
0
0

@GossiTheDogKevin Beaumont

Around ten years ago, one of the FreeBSD developers had an SSH key compromised. This key gave access to the machine with our subversion server on it. And, due to how svn worked, every user had write access to the directory containing the repo.

Subversion does not have any way of doing integrity checks, so the recovery process involved (via a script) checking out each revision in turn, then doing the same with a git mirror, and validating that they were the same.

Audit logs showed that the attacker had logged in, tried running a few Linux commands, got error messages, and logged out. We were incredibly fortunate that they didn’t do anything more serious.

0
0
1

I cannot tell you have many security incidents I’ve worked at orgs on critical national infrastructure over the years where the threat actor got access and *mind boggles* deployed coin miners.

No really, I don’t think I can you tell you, I’d get sued 🤣

@GossiTheDogKevin Beaumont

Around ten years ago, one of the FreeBSD developers had an SSH key compromised. This key gave access to the machine with our subversion server on it. And, due to how svn worked, every user had write access to the directory containing the repo.

Subversion does not have any way of doing integrity checks, so the recovery process involved (via a script) checking out each revision in turn, then doing the same with a git mirror, and validating that they were the same.

Audit logs showed that the attacker had logged in, tried running a few Linux commands, got error messages, and logged out. We were incredibly fortunate that they didn’t do anything more serious.

0
0
0
0

It is with great excitement that we are launching this years community survey.

survey.nixos.org/759934

We are conducting this survey to improve our understanding of the community and better support various teams. This year we have questions from the Nix Team, the StdEnv Team, the Steering Committee, and the Foundation which will help inform the work they do for the project.

As always, the survey is anonymous. Aggregated statistics and major findings will be published on Discourse.

0
0

슈퍼마켙에 콩 통조림 점장이
직접 담근 술을 저렴하게 팔아...

하지만 그 누구도 술의 재료가
무엇인지 알려고 해서는 안 돼...

그리고 그 술을 언급하면 안 돼...

0
0
0

Claude에 따르면 대부분의 JavaScript 엔진에서 배열을 비울 때 a.length = 0과 같이 대입하는 게 가장 빠르고 최적화가 잘 된다고 하는데, 이걸 믿어야 할 지 말아야 할 지… 이게 사실이라고 해도 참 답이 없다고 느낀다. 🤦

3
0
0
0

한진 제주 지하수 증산 심의 D-1...물 더 퍼내도 환경영향 없나?:
한국공항㈜의 제주도 먹는샘물 지하수 증산 동의안이 12일 제주도의회 환경도시위원회 심의를 앞두고 있다. 제주도청은 과학적·기술적으로는 고갈이나 수위 하강 우려가 없다는 입장이지만, 시민사회는 “문제는 양이 아니라 원칙”이라고 맞섰다. 한국공항이 2011년 이후 여섯 번째 시도하는 증산안이 이번에는 의회의 벽을 넘을 수 있을지 관심이 집중된다.도청 “환경 영향 없다”제주 지하수를 취수해 먹는샘물 ‘제주퓨어워터’를 생산하는 한국공항㈜이 한 달 취수량을 현행 3000톤에서 4400톤으로 늘려 달라고 신청했다. 하루 기준 100톤에서 14
newspenguin.com/news/articleVi
(2025-09-11 17:40:52)

0

I cannot tell you have many security incidents I’ve worked at orgs on critical national infrastructure over the years where the threat actor got access and *mind boggles* deployed coin miners.

No really, I don’t think I can you tell you, I’d get sued 🤣

@GossiTheDogKevin Beaumont

Around ten years ago, one of the FreeBSD developers had an SSH key compromised. This key gave access to the machine with our subversion server on it. And, due to how svn worked, every user had write access to the directory containing the repo.

Subversion does not have any way of doing integrity checks, so the recovery process involved (via a script) checking out each revision in turn, then doing the same with a git mirror, and validating that they were the same.

Audit logs showed that the attacker had logged in, tried running a few Linux commands, got error messages, and logged out. We were incredibly fortunate that they didn’t do anything more serious.

0
0
0
0
0
0
0