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.

📆 Open till January 26!

The EU will get an online database that allows anyone, especially researchers/journalists, to learn about online political advertising.

The archive will collect political ads to create transparency around their source and funding.

Technical specifications are currently being developed.

Public feedback on that is welcome until January 26: ec.europa.eu/info/law/better-r

0
1

📆 Open till January 26!

The EU will get an online database that allows anyone, especially researchers/journalists, to learn about online political advertising.

The archive will collect political ads to create transparency around their source and funding.

Technical specifications are currently being developed.

Public feedback on that is welcome until January 26: ec.europa.eu/info/law/better-r

0
0
0
0
0
0
0
0
0

The next session of Club is scheduled on this Saturday 17th January at 2:30 PM IST. Join us this time for a tech and design focused session. We'll co-work on our personal websites, try new designs, squash bugs, or just do some long-neglected digital housekeeping.

If you don't have any programming experience, don't worry! We'll help you with any technical questions you might have about building your personal website, blog, or participating on the IndieWeb. If possible, we'll pair you up with a buddy who can help you out with the technical and design side of web development.

Bring:
1. Your laptop (+ charger)
2. Ideas for new features/designs you want to add to your website (or just a list of enhancements you want to make)
3. If you're new to programming, come with questions so we can find you answers!

As usual, we will end the meetup with a writing prompt and a focused writing session. Register to confirm your attendance at blr.indiewebclub.org.

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

TIL the way piano keys are laid out is not well documented on the internet, and not even standardized!

This site explains the problem... but neither of the solutions it proposes are what actually happens as far as I can tell.

datagenetics.com/blog/may32016

On both my KORG and my Yamaha keyboards, the key giveaway is that C# and D# are significantly further apart than F# and G# (and G# and A#). You can easily feel this if you slide your finger on top of D and G/A.

I don't have a good way to measure exactly, but just looking closely at my keyboards, I think what actually happens is roughly:

  • F through B are laid out as in "Scenario #1" on that site.
  • Then, KORG and Yamaha do two things:
    • Yamaha has C=F and E=B, and places C# and D# at the same relative positions to C and E as F# and A# are to F and B, which leaves D an oddball white key: its "stem" is much wider than that of the other white keys. Also maybe F is a bit weird?
    • KORG cheats more: They split the difference between the CDE stems (which are slightly wider) and the gaps around C# and D# (which are now positioned slightly closer together than Yamaha's, but still further apart than F# and G#).
  • For both designs, I believe the underlying mechanism/sensors are evenly spaced across the octave, and the mismatch (most prominent at the boundary between E and F) is just handwaved away (sensors are not on the centerline of keys).

I wonder if this correct, and what other solutions are out there in the wild?

0
0
知人 = 지인 , 그냥 아는 사람
友達, 友人 = 친구, 友人 이 조금 더 격식차린 느낌.
親友 = 인생의 친구.
仲間 = 친구 무리의 범주에 든 사람.
友達에도 개인 연락처 공유와 거리감에 따라 다양한 층위가 있으니 주의하십시요.
0
0
0
0
1
0
0
0
0
0
0
0
0
0

Today I found out about a Mastodon instance called Weirder.Earth/, "a space to celebrate our diversity. Be true to yourself and let others do the same."

So great to see so diverse communities on the Fedi, defining their own space, setting their own rules, while being interconnected with the rest of us.

@WtebbensWouter Tebbens ⁂

well, it is a "Hometown" instance.
Darius put much work in this github.com/hometown-fork/homet and especially since some US devs currently „disappear“, I think:

If we should "celebrate our diversity", it would be the diversity of the fedi softaware and not only the monopoly :)

0

내 구독 목록을 보는 SubList Me 를 소개합니다.

  • 대 AI 시대라, 저도 AI 에이전트와 함께 개인적으로 장난감을 만들어 보았습니다.

  • Cloudflare에서 도메인을 샀고, 서버리스로 Pages와 Workers를 사용합니다.

  • Nextjs, Hono를 사용하고 있습니다.

  • 선택UI 는 Installkit에서 영감을 받았습니다.

  • Hackers.pub 에 제일 먼저 공개하고 싶었고, 그러므로, 최초 공개입니다. 😅

  • 많이 부족하고 아직 버그나 개선의 여지도 많지만 개밥먹기하면서 수정해 나가려고 합니다.

  • 소개 페이지: https://www.sublistme.com/

  • 서비스 링크: https://app.sublistme.com/

소스는 요기

Sublist Me Screenshot 1Sublist Me Screenshot 2
2
1
1
0

내 구독 목록을 보는 SubList Me 를 소개합니다.

  • 대 AI 시대라, 저도 AI 에이전트와 함께 개인적으로 장난감을 만들어 보았습니다.

  • Cloudflare에서 도메인을 샀고, 서버리스로 Pages와 Workers를 사용합니다.

  • Nextjs, Hono를 사용하고 있습니다.

  • 선택UI 는 Installkit에서 영감을 받았습니다.

  • Hackers.pub 에 제일 먼저 공개하고 싶었고, 그러므로, 최초 공개입니다. 😅

  • 많이 부족하고 아직 버그나 개선의 여지도 많지만 개밥먹기하면서 수정해 나가려고 합니다.

  • 소개 페이지: https://www.sublistme.com/

  • 서비스 링크: https://app.sublistme.com/

소스는 요기

Sublist Me Screenshot 1Sublist Me Screenshot 2
2

海までお散歩。目に付いたゴミを拾って捨てようと思ったら1月~3月はゴミ箱が無いとのこと。が、ビーチクリーン用ゴミ袋の集積場に誰かが集めたゴミ袋がおいてあったのでその中に押し込んできた。

逗子海岸の砂浜の上においてあるひらがなの「ずし」の形のオブジェ。奥におだやかな海が広がる。
0

Today I found out about a Mastodon instance called Weirder.Earth/, "a space to celebrate our diversity. Be true to yourself and let others do the same."

So great to see so diverse communities on the Fedi, defining their own space, setting their own rules, while being interconnected with the rest of us.

0
0
0
0

내 구독 목록을 보는 SubList Me 를 소개합니다.

  • 대 AI 시대라, 저도 AI 에이전트와 함께 개인적으로 장난감을 만들어 보았습니다.

  • Cloudflare에서 도메인을 샀고, 서버리스로 Pages와 Workers를 사용합니다.

  • Nextjs, Hono를 사용하고 있습니다.

  • 선택UI 는 Installkit에서 영감을 받았습니다.

  • Hackers.pub 에 제일 먼저 공개하고 싶었고, 그러므로, 최초 공개입니다. 😅

  • 많이 부족하고 아직 버그나 개선의 여지도 많지만 개밥먹기하면서 수정해 나가려고 합니다.

  • 소개 페이지: https://www.sublistme.com/

  • 서비스 링크: https://app.sublistme.com/

소스는 요기

Sublist Me Screenshot 1Sublist Me Screenshot 2
2

Been thinking a lot about @algernonI'm in my database, and I don't like it's recent post on FLOSS and LLM training. The frustration with AI companies is spot on, but I wonder if there's a different strategic path. Instead of withdrawal, what if this is our GPL moment for AI—a chance to evolve copyleft to cover training? Tried to work through the idea here: Histomat of F/OSS: We should reclaim LLMs, not reject them.

AI 企業(기업)이 F/OSS 코드로 LLM 訓練(훈련)하는 걸 막을 게 아니라, 訓練(훈련)한 모델을 公開(공개)하도록 要求(요구)해야 한다고 생각합니다.

撤收(철수)가 아니라 再專有(재전유)! GPL이 그랬던 것처럼요.

訓練(훈련) 카피레프트에 ()한 글을 썼습니다: 〈F/OSS 史唯(사유): 우리는 LLM을 拒否(거부)할 게 아니라 되찾아 와야 한다〉(한글).

2

TIL the way piano keys are laid out is not well documented on the internet, and not even standardized!

This site explains the problem... but neither of the solutions it proposes are what actually happens as far as I can tell.

datagenetics.com/blog/may32016

On both my KORG and my Yamaha keyboards, the key giveaway is that C# and D# are significantly further apart than F# and G# (and G# and A#). You can easily feel this if you slide your finger on top of D and G/A.

I don't have a good way to measure exactly, but just looking closely at my keyboards, I think what actually happens is roughly:

  • F through B are laid out as in "Scenario #1" on that site.
  • Then, KORG and Yamaha do two things:
    • Yamaha has C=F and E=B, and places C# and D# at the same relative positions to C and E as F# and A# are to F and B, which leaves D an oddball white key: its "stem" is much wider than that of the other white keys. Also maybe F is a bit weird?
    • KORG cheats more: They split the difference between the CDE stems (which are slightly wider) and the gaps around C# and D# (which are now positioned slightly closer together than Yamaha's, but still further apart than F# and G#).
  • For both designs, I believe the underlying mechanism/sensors are evenly spaced across the octave, and the mismatch (most prominent at the boundary between E and F) is just handwaved away (sensors are not on the centerline of keys).

I wonder if this correct, and what other solutions are out there in the wild?

0
0
0
1
0
0