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

accounts to follow:

➡️ !@crochetcrochet, tunisian crochet, ... - Crochet discussion group, follow to see posts, mention to post to group
➡️ @LittleBearCrochets@pixelfed.social (pictures) & @LittleBearCrochets@mastodon.art (text) - Designs crochet amigurumi patterns
➡️ @CeefercraftsSimone - Crochet & crafts enthusiast
➡️ @doomyfloDoomyflo 🐧🤘📚 - Crochet figures based on FOSS projects etc (in French)
➡️ @LaVisch - Knitting & crochet enthusiast, tutorials, patterns, designs
➡️ @thegiddystitcherMichelle / The Giddy Stitcher (main) & @michellemay (videos) - Multicrafter & craft video maker

🧵 1/2

0
0
0

i think is a beneficial exercise for anyone who writes technical content to read the left version and the right version and to think why they're essentially saying the same thing but one of them is a million times easier to follow. how did that happen?

Lexicon Resolution requires 2 things, control of the domain which the Lexicon's NSID refer to (e.g. bookhive.buzz in the example above), and for the Lexicon to be published in some account's PDS (where your account data is stored in ATProto). The process of Lexicon resolution is actually pretty simple:

Given a Lexicon NSID (buzz.bookhive.defs), remove the name part, to derive the Domain authority (which was in reverse-DNS notation).
So, we'd end up with bookhive.buzz
Look for a DNS TXT record at _lexicon.<domain authority>, just like handle resolution, which should have published did=<account did> to point to the account which holds the Lexicon schemas.
So, at _lexicon.bookhive.buzz there is a TXT record that stores did=did:plc:enu2j5xjlqsjaylv3du4myh4 (which is the did of the @bookhive.buzz account)
In the account's PDS, there should be a collection com.atproto.lexicon.schema which stores the schema's NSID as the record key (rkey) and the value is the Lexicon schema with "$type": "com.atproto.lexicon.schema", "lexicon": 1 added to the schema object.
So, at at://did:plc:enu2j5xjlqsjaylv3du4myh4/com.atproto.lexicon.schema/buzz.bookhive.defs it will contain the Lexicon schema:Lexicon schemas are published publicly as records in atproto repositories, using the com.atproto.lexicon.schema type. The domain name authority for NSIDs to specific atproto repositories (identified by DID is linked by a DNS TXT record (_lexicon), similar to but distinct from the handle resolution system.

The com.atproto.lexicon.schema Lexicon itself is very minimal: it only requires the lexicon integer field, which must be 1 for this version of the Lexicon language. In practice, same fields as Lexicon Files should be included, along with $type. The record key is the NSID of the schema.

A summary of record fields:

$type: must be com.atproto.lexicon.schema (as with all atproto records)
lexicon: integer, indicates the overall version of the Lexicon (currently 1)
id: the NSID of this Lexicon. Must be a simple NSID (no fragment), and must match the record key
defs: the schema definitions themselves, as a map-of-objects. Names should not include a # prefix.
description: optional description of the overall schema; though descriptions are best included on individual defs, not the overall schema.
The com.atproto.lexicon.schema meta-schema is somewhat unlike other Lexicons, in that it is defined and governed as part of the protocol. Future versions of the language and protocol might not follow the evolution rules. It is an intentional decision to not express the Lexicon schema language itself recursively, using the schema language.

Authority for NSID namespaces is done at the "group" level, meaning that all NSIDs which differ only by the final "name" part are all published in the same repository. Lexicon resolution of NSIDs is not hierarchical: DNS TXT records must be created for each authority section, and resolvers should not recurse up or down the DNS hierarchy looking for TXT records.
0
0
0
0
0
0
1

【ごあいさつ】
オリジナルキャラクターや相互の方の絵を描いています!
こちらでは他のSNSではあげられないようなセンシティブなものもアップしていきたいです!
よろしくお願いします!

1

i more or less stopped caring about this myself when i realized i can feed unreadable docs (specs?) into claude and ask it to explain it back to me in a normal human way, like ok i wanna publish a lexicon, what do i *actually* do and in what order and give me examples maybe that's fine

0

RE: mastodon.social/@e_mydata/1157

2/2 Why is the Digital Omnibus proposal a privacy threat?

🔸Legal uncertainty: GDPR may no longer apply if companies claim not to identify you
🔸Vague rules allowing broader remote access to device data
🔸Big Tech could use Europeans’ personal & sensitive data to train AI
🔸User rights weakened: access to your own data restricted to privacy complaints

👉 Full article by noyb: noyb.eu/en/digital-omnibus-eu-

0
0
0

1/2 🇪🇺 Digital Omnibus: Is the EU becoming more “business-friendly” - or giving in to pressure from Trump?

A new EU proposal would fundamentally weaken the GDPR - offering no benefits for European SMEs, but opening the door for Big Tech.

Max Schrems @noybeu : “The biggest attack on Europeans’ digital rights in years.”

0
0
1
0

I recently refreshed my article on analog-to-digital and digital-to-analog conversions. Did you know that there are many different ways to convert analog voltages to bits and bytes, and that some of the methods are quite... unhinged?

Check it out: lcamtuf.coredump.cx/blog/conve

0

this isn't to shit on the team's work, i think the team is aware. and getting spec-level content out is probably most important on their end since (hopefully) people able to get through this should be able to later explain "for the masses" and claude can eat these docs too still a bit sad

0

whereas atproto docs very rarely do that. they dump a bunch of information from all directions — no intended order of learning, no avoiding cycles, just random bits and pieces in extreme amount of detail with no unifying narrative an exception is philosophical guides and tutorials which are great

0
0
0
0
0

이 건과 함께 여러가지 불만이 겹쳐서 키어 스타머의 노동당 지지율은 끊임없이 추락하여 녹색당과 비슷한 수준이 되었고, 이대로라면 다음 선거(2029년 예정, 그 전에 해산할 수는 있지만 가능성 낮음)에서 이전에 브렉시트를 주도했던 나이절 패라지의 극우당 Reform이 과반을 차지할 수도 있다는 관측이 나옵니다.

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

accounts to follow:

➡️ @PolarBremenPolar Remote Sensing, Bremen - Research group monitoring sea ice in polar regions

➡️ @Ruth_Mottram@fediscience.org (main) & @ruth_mottram@tilvids.com (videos) - Climate scientist studying ice & atmosphere in Antarctic, Arctic, Greenland

➡️ @RRSSirDavidAttenborough - Webcam on polar research vessel RRS Sir David Attenborough (the ship which was nearly named Boaty McBoatface)

➡️ @southpoleviewsViews from South Pole - Webcams showing images from various Antarctic research bases

0
0
0

2025년 7월 5일, 영국 정부는 Terrorism Act 2000에 근거하여 Palestine Action을 테러리스트 집단으로 규정하였고 이에 동조하는 사람은 최대 14년의 징역에 처할 수 있게 되었습니다. 피켓만 들고 있어도 사지를 들려 끌려가는 것은 당연해졌고, 이 때문에 관련되어 체포되는 건수가 660% 증가했다고 알려졌습니다. 유엔 인권최고대표사무소는 7월 25일 이는 "'충격적인' 반테러 규제의 오용"이며 "영국 내 정당한 기본 인권 행사 침해"를 경고하는 뜻을 표명한 바 있습니다.

RE: https://bsky.app/profile/did:plc:5peluurz7zasjb4qlkjjyfrd/post/3manrmu6er22b


UK police arrest over 466 at p...

1
1

Password found: 𒔼𒁓𒐞𒑟𒀂𒋝𒐕𒆸𒉼𒀼𒀂𒋝𒑚𒐕𒉼𒀼𒀂𒐕𐎣𒐖𒔼𒑚𒐕𒆸𒀼𒀂𐎣𒋝𒆸𒇬𒐕𒔼𒋻𒀼𒑟𐎣𒋝𒐞𒁇𒑟𒉼𒔼𒀼𒀂𐎣𒋝𒐕𒆸𒑟𒀼𒉼𒐖𒋝𒐞𒁇𒑟𒋻𒐞𒉼𐎣𒐕𒀂𒑟𒔼𒁓𒇲𒆸𒇬𒋝𒑟𒔼𒁓𒀼𒇲𒐕𒆸𒋝𒑟𒔼𒇲𒀼𒐕𒆸4902𒁓𒋝𒑟𒁓𒔼𒀂𒇲𒋝𒆸𒐕𒀼𒇲𒑟𒐕𒆸𒋝𒀂𒑚𒀼𒑟𒀼𒐕𒇲𒀂𒆸𒐕𒇲𒀼𒁓𒑟𒀂𒋝𒁓𒐕𒆸𒇲𒑟𒋝𒀼4𒉼𒇲𒇬𒐕𒀂𒐖𒋝𒇬

This password would take centuries to crack,
@link@meowing.menlink (t)wink: blog edition :neocat_flag_pan: is a good password generator :3

RE: https://meowing.men/fediverse/post/9532749a-511d-4afc-b3de-b52bbe769836

0
0
1

今回の​:unicode_1d54f_bg_black:のシャドウバンは重めのやつなので、解除されるまで数ヶ月はかかりそうです。
35万詰んだのに….ᐟ.ᐟ
その間大人しくしてなきゃいけないのがつらみ…
もしかしから二段階リプをお願いするかもしれませんが、その時はよろしくお願いします
💦

1
0

쿠팡 김범석, '일부러 욕설·갈등 증폭하라' 경영진에 이메일

n.news.naver.com/article/437/0

❝김범석 쿠팡 의장이 핵심 경영진에게 '노동자 해고를 위한 조직을 구축하고, 의도적으로 욕설을 사용하고, 갈등을 의도적으로 증폭한다'는 내용의 경영 철학을 공유한 것으로 전해졌습니다. ❞

진짜 쓰레기네...

0

【ブログ書いたやで】 CSS で独自のチェックボックスやラジオボタンをデザインする時に label や span の擬似要素を使うより input 要素そのものの擬似要素を使った方が何かと便利で簡単だよ、という話を書きました。ギリギリですが何とかリリース日前に記事を公開できて良かったなと思います(ポイントはそこじゃないです。涙)
👇
えっ先輩まだチェックボックスやラジオボタンのカスタマイズに label とかの擬似要素使ってんすか? それもう古いっすよ… jeffreyfrancesco.org/weblog/20

0
0
2
0
0
0
0