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

[공유해주세요: 부산집회 5개월내내 여성패싱사람들에게 계속된 상습 스토킹, 괴롭힘 공론화] 부산 윤석열 탄핵 집회에서 퀴어/앨라이 기수가 많이 모인 기수존을 집중적으로 배회하며 집회참석자들을 괴롭히는 자가 있습니다. 남성패싱 참석자들에겐 깍듯하며 퀴어연대를 다짐하나 머리가 길거나 스커트에 가까운 옷을 입거나 '여성패싱'되는 집회 참석자들에게는 집요한 호구조사와 신체접촉, 얼평, 왜 자신에게 닉네임 등 신상정보를 안 주냐는 원망과 비난 등 괴롭힘을 매일 일삼는 이자는 2016년 박근혜탄핵 집회때도 온오프라인괴롭힘이 적발되었습니다.

0
0
0
1
0
0
0
0
0
0

사람은 정말 온건하고 순하고 조심스러운 태도로도 개쎈혐오가짜뉴스를 말할 수 있는 것이다. 온건하다고 가만 놔 두면 온건하게 동조자가 늘어나고, 그거 아니라고 정색하고 뜯어말리면 당혹하거나 심지어 "공격받았다"며 진심으로 토라지는 사람들을... 대체 어째야 하는가.

1
1
0
0
0
0
0
0
0
1

가짜뉴스와 선동과 파편화의 시대. 스스로는 순박하고 온건하고 비편향적인 입장을 취한다고 취하지만, 딛고 선 논리가 남들이 파탄내 놓은 구렁텅이인 줄을 모른다. 결국 남들이 해줄 말은 "당신 말이 처음부터 끝까지 다틀렸다" 밖에 없는데 그런 반응에는 상처입고 분노하더라... 당연함. 스스로는 소박한 진실만 말한 것인데 인신공격 수준의 대꾸가 돌아왔다고 여기기 때문임. 그런데 도대체 이 참사를 어째야하나.

0
0
0
1
0
0

Large Language Models (LLMs) are lying machines. You might say: "I use it all the time for coding or research and I find it extremely helpful". I can't and won't dispute your experience of useful, insightful, or even spiritually awakening output. I am stating that its impossible for the LLM not to lie. This is because the LLM has no concept of fact, fiction, lie, or truth. Some lies happen to be true, some lies can be insightful or helpful, some lies can even be deeply personal. Humans are wonderfully powerful pattern matchers. We can extract meaning from enormous piles of nonsense, quickly forgetting the meaningless and remembering the useful. It gives us an extremely warped perception of these systems.

This isn't a bug to be worked out or a temporary issue that some company can overcome with just one more model, its an inherent part of how the system works. LLMs are just that, language models. When fed unimaginable amounts of examples they can produce syntactically correct text. They don't have the capacity to understand and no amount of tweaking, training, or layering will produce a system that does, that's magical thinking.

0

so, the gdb protocol specifies g and G commands, "read/write target register", to transfer register values in target byte order. i don't know what must be wrong with you to define a protocol this way, but okay

... but then lldb interprets them always in the host (the machine lldb runs at) byte order.

you can't win.

0
0
0
0
0
0
0
1

We are implementing the final version of RFC9421 (HTTP Signatures) in Mastodon, and would like to test this with other ActivityPub implementations.

Do you know of any AP implementations supporting both incoming (verification) and outgoing (signing) RFC9421 signatures, and if possible with support for the double-knocking mechanism as described in swicg.github.io/activitypub-ht (section 3.5)?

0
0
0

Please boost!

I'm looking for my next role as a program manager, team lead, or senior developer.

- 20+ years in open source
- 6 years experience in web dev with , , HTML, bootstrap
- 7 years experience in C, Linux kernel, embedded systems

My passions lie at the intersection of open source software development and creating welcoming spaces for people to learn and grow.

I'm currently the program manager for a technical internship program. I work remotely with a team of 4 people in New York, Brazil, and Nigeria.

Looking for a fully remote role. I'm open to relocation outside the USA.

Resume here: sage.thesharps.us/hire-me/

DM me or send an email to sage at thesharps dot us

0
0
0
0
0
0
0
0
0
0
0

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, 's approach seems to offer some architectural advantages:

  1. The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
  2. Separating approval objects from interactions appears more secure against forgery
  3. The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
  4. The extensible framework allows for handling diverse interaction types, not just replies

I wonder if creating an that extracts GoToSocial's interaction policy design into a standalone standard might be worthwhile. It could potentially serve as a more comprehensive foundation for access control in .

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

4
0

오늘은 싱글유저를 위한 패스워드 방식으로 인증정보 암호화 저장을 다시 만들었고, 내일 목표는 크롤링 소스 하나 포팅과 구글 캘린더로 출력코드 옮겨오기.

2
0