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.

1
0

Kia ora fedizens, a few months ago I was shoulder-tapped to take on stewardship of fediverse.party. One of a bunch of websites that aim to gather lots of useful info about the fediverse in one place. This is a project I've been a casual contributor to for years, and I really want to see it maintained. So I said yes.

(1/2)

Problem is, I've been drifting in and out of burnout since 2020 (if not longer), and I'm currently struggling with the day-to-day, while trying to support aging family members. I really want to work on fediverse.party, but I'm not sure I have the spoons.

I'm happy to be a steward in the sense of holding the site's history and other institutional knowledge, and giving feedback on update or reform proposals. Does anyone have enthusiasm for driving this?

(2/2)

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

아직 인생이 끝나지 않아 망한건지 잘 모르겠습니다. 그래서 삶이 끝날 때까지 어찌저찌 계속 살아보려 합니다. 그러면 삶이 끝날때 제 인생이 망한건지 확인해서 말씀드릴 수 있을 것 같습니다.

RE: https://bsky.app/profile/did:plc:w2ee5xxnx6y6qqukl5zt52gj/post/3md7tsbtquk2h

1
0
0

JSON vs IETF JSON

JSON and IETF JSON feel different in spirit in some important ways to me.

For example, numbers.

JSON doesn't seem to put constraints on numbers. JSON also doesn't seem to suggest that decoding numbers in a lossy way is acceptable

IETF JSON suggests a constraint and even a lossy-ness on numbers that has been included some JSON implementations

I would have preferred that the paragraph in the screen-shot, from the latest IETF RFC, did not exist in there

This specification allows implementations to set limits on the range and precision of numbers accepted.  Since software that implements IEEE 754 binary64 (double precision) numbers [IEEE754] is generally available and widely used, good interoperability can be achieved by implementations that expect no more precision or range than these provide, in the sense that implementations will approximate JSON numbers within the expected precision.  A JSON number such as 1E400 or 3.141592653589793238462643383279 may indicate potential interoperability problems, since it suggests that the software that created it expects receiving software to have greater capabilities for numeric magnitude and precision than is widely available.
0
0
0
0
1
0
0
1
0

I remember explaining this exact use case to Very Serious People at multiple non-profits who had received literal millions of dollars to research privacy, and these Very Serious People assured me that could never happen.

I quit these places with joy because these folks were myopic assholes who allowed their privilege to exacerbate harms.

One of these fuckers told me "but I like the ads - they help me see what sneakers I should buy."

wired.com/story/ice-asks-compa

0
0
0
0
0
0
0

Did someone post something? It's on mastodon.social. It's literally on booping.synth.download. It's maybe in wetdry.world. It's literally on gts.apicrim.es. You can probably find it on app.wafrn.net. Dude it's on shrimp.starlightnet.work. It's a infosec.exchange original. Check out mas.to for it. You'll find it on hachyderm.io. It's definitely on oomfie.city. Look for it on tech.lgbt. It's over on yeen.town. You can see it on waf.moe. It's been shared on akko.wtf. Go peek at fuzzies.wtf. It's trending on transfem.social. You can catch it on eepy.moe. Browse over to lethallava.land. It's on hackers.pub. You can read it on hackers.pub. You can go to hackers.pub and like it. Log onto hackers.pub right now. Go to hackers.pub. Dive into hackers.pub. You can hackers.pub it. It's on hackers.pub. hackers.pub has it for you. hackers.pub has it for you.

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