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.
The Princeton INTERCAL Compiler's source code
Link: https://esoteric.codes/blog/published-for-the-first-time-the-original-intercal72-compiler-code
Discussion: https://news.ycombinator.com/item?id=44155247
Just curious: How many of you were on ICQ when it was the way to chat online? 🙋🏻
기억해주세요,,,🥹 x.com/yuionyeon/st...
독일 외교부장관이 이스라엘 무기 공급이 인도적 기준에 맞는지 "(재)검토"하기로 했다고. 너무 늦었지만 전향적 결정을 바람.
@reiver ⊼ (Charles) 
shared the below article:
julian @julian@community.nodebb.org
<p>It all started <a href="https://community.nodebb.org/topic/18824/did-4.4.1-break-federation-with-lemmy-groups">with a report about federation breaking between Lemmy and NodeBB</a>. I was subconsciously aware that something was going on, but had chalked it up to network issues.</p> <p>Observed behaviour showed that some remote categories would be receiving content in spurts, with long gaps in between.</p> <p>I spent the next 3-4 days looking into it, but came up empty. Whatever was happening wasn't throwing any obvious errors, and along the way, I found what I <em>thought</em> was related (it was), but I wasn't sure why: against some Lemmy servers, the "follow"/"unfollow" mechanic would simply stop working, and this would often coincide with gaps in content. In some egregious cases, the flow of content stopped completely!</p> <p>Unable to make headway, I had to <a href="https://github.com/LemmyNet/lemmy/issues/5722" rel="nofollow ugc">reach out to the folks at Lemmy</a> to figure out what the issue was. NodeBB occasionally sends non-200 level responses depending on the activity. Specifically, the following scenarios:</p> <ul> <li>A remote user upvoting more than 20 posts in a single day (a spam prevention tactic) causing NodeBB to throw an error, which was caught and returned an <code>HTTP 500 Internal Server Error</code>.</li> <li>A <code>Dislike</code> activity, which is not currently handled by NodeBB. In these cases, NodeBB would send an <code>HTTP 501 Not Implemented</code></li> </ul> <p>When encountering either of these responses, Lemmy would return the activity back to the queue for later delivery and <strong>mark a delivery failure</strong>. If enough of these (~40) happened within 24 hours, Lemmy would give the instance a time-out and <em>pause delivery completely</em>.</p> <p>That was it — a quick pair of code updates later, and we started working through Lemmy's backlog of 4.1M activities.</p> <p>As of 4am this morning, <code>community.nodebb.org</code> is no longer behind <code>lemmy.world</code>.</p> <p><img src="https://community.nodebb.org/assets/uploads/files/1748873636999-d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" alt="d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" /></p> <p>Fun week. Let's not do that again LOL.</p> <p>v4.4.2 of NodeBB contains the updated logic for smoother Lemmy federation.</p>
Read more →SPC삼립 공장 가동중단⋯햄버거 빵 공급 차질 '속출'
n.news.naver.com/mnews/articl...
1. 아니 무슨 빵 공장에서 사람이 정기적으로 죽어요?
2. 롯데리아, 버거킹, 아웃백(부시맨), 노브랜드, 맘스터치, 크보빵
,
SPC삼립 공장 가동중단⋯햄버거 빵 공급 차질 '속출'
상어학땡스 
shared the below article:
julian @julian@community.nodebb.org
<p>It all started <a href="https://community.nodebb.org/topic/18824/did-4.4.1-break-federation-with-lemmy-groups">with a report about federation breaking between Lemmy and NodeBB</a>. I was subconsciously aware that something was going on, but had chalked it up to network issues.</p> <p>Observed behaviour showed that some remote categories would be receiving content in spurts, with long gaps in between.</p> <p>I spent the next 3-4 days looking into it, but came up empty. Whatever was happening wasn't throwing any obvious errors, and along the way, I found what I <em>thought</em> was related (it was), but I wasn't sure why: against some Lemmy servers, the "follow"/"unfollow" mechanic would simply stop working, and this would often coincide with gaps in content. In some egregious cases, the flow of content stopped completely!</p> <p>Unable to make headway, I had to <a href="https://github.com/LemmyNet/lemmy/issues/5722" rel="nofollow ugc">reach out to the folks at Lemmy</a> to figure out what the issue was. NodeBB occasionally sends non-200 level responses depending on the activity. Specifically, the following scenarios:</p> <ul> <li>A remote user upvoting more than 20 posts in a single day (a spam prevention tactic) causing NodeBB to throw an error, which was caught and returned an <code>HTTP 500 Internal Server Error</code>.</li> <li>A <code>Dislike</code> activity, which is not currently handled by NodeBB. In these cases, NodeBB would send an <code>HTTP 501 Not Implemented</code></li> </ul> <p>When encountering either of these responses, Lemmy would return the activity back to the queue for later delivery and <strong>mark a delivery failure</strong>. If enough of these (~40) happened within 24 hours, Lemmy would give the instance a time-out and <em>pause delivery completely</em>.</p> <p>That was it — a quick pair of code updates later, and we started working through Lemmy's backlog of 4.1M activities.</p> <p>As of 4am this morning, <code>community.nodebb.org</code> is no longer behind <code>lemmy.world</code>.</p> <p><img src="https://community.nodebb.org/assets/uploads/files/1748873636999-d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" alt="d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" /></p> <p>Fun week. Let's not do that again LOL.</p> <p>v4.4.2 of NodeBB contains the updated logic for smoother Lemmy federation.</p>
Read more →#wildlife #nature #picnickingcritters #squirrels
Random Wildlife
useit.com on February 18, 1997
https://web.archive.org/web/19970218113042if_/http://www.useit.com:80
this is the most brutal tech job interview process I’ve ever read for most popular #linux distro 😱
https://dustri.org/b/my-experience-with-canonicals-interview-process.html
음 ..... 아니 뭔가 정말 이상한데 ... 지하철에는 리디북스 웹툰 광고하는데 정작 리디북스엔 알라딘엔 있는 이북이 ... 찾을때마다 없다. ...... 우연이라고 하긴 좀 뭣한데 ......
쏘카 감당 가능하나??
일일대여료가 70 ㅋㅋㅋ;
NodeBB가 ActivityPub을 지원하는구나
맹꽁이 shared the below article:
julian @julian@community.nodebb.org
<p>It all started <a href="https://community.nodebb.org/topic/18824/did-4.4.1-break-federation-with-lemmy-groups">with a report about federation breaking between Lemmy and NodeBB</a>. I was subconsciously aware that something was going on, but had chalked it up to network issues.</p> <p>Observed behaviour showed that some remote categories would be receiving content in spurts, with long gaps in between.</p> <p>I spent the next 3-4 days looking into it, but came up empty. Whatever was happening wasn't throwing any obvious errors, and along the way, I found what I <em>thought</em> was related (it was), but I wasn't sure why: against some Lemmy servers, the "follow"/"unfollow" mechanic would simply stop working, and this would often coincide with gaps in content. In some egregious cases, the flow of content stopped completely!</p> <p>Unable to make headway, I had to <a href="https://github.com/LemmyNet/lemmy/issues/5722" rel="nofollow ugc">reach out to the folks at Lemmy</a> to figure out what the issue was. NodeBB occasionally sends non-200 level responses depending on the activity. Specifically, the following scenarios:</p> <ul> <li>A remote user upvoting more than 20 posts in a single day (a spam prevention tactic) causing NodeBB to throw an error, which was caught and returned an <code>HTTP 500 Internal Server Error</code>.</li> <li>A <code>Dislike</code> activity, which is not currently handled by NodeBB. In these cases, NodeBB would send an <code>HTTP 501 Not Implemented</code></li> </ul> <p>When encountering either of these responses, Lemmy would return the activity back to the queue for later delivery and <strong>mark a delivery failure</strong>. If enough of these (~40) happened within 24 hours, Lemmy would give the instance a time-out and <em>pause delivery completely</em>.</p> <p>That was it — a quick pair of code updates later, and we started working through Lemmy's backlog of 4.1M activities.</p> <p>As of 4am this morning, <code>community.nodebb.org</code> is no longer behind <code>lemmy.world</code>.</p> <p><img src="https://community.nodebb.org/assets/uploads/files/1748873636999-d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" alt="d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" /></p> <p>Fun week. Let's not do that again LOL.</p> <p>v4.4.2 of NodeBB contains the updated logic for smoother Lemmy federation.</p>
Read more →Hello, Hachyderm --
We're doing some system maintenance. You might notice a little bleep or bloop or three for the next hour or so. 
Happy Hachyderming,
The Infra Team
SPC삼립 공장 가동중단⋯햄버거 빵 공급 차질 '속출'
n.news.naver.com/mnews/articl...
1. 아니 무슨 빵 공장에서 사람이 정기적으로 죽어요?
2. 롯데리아, 버거킹, 아웃백(부시맨), 노브랜드, 맘스터치, 크보빵
,
SPC삼립 공장 가동중단⋯햄버거 빵 공급 차질 '속출'
폰낛리퀘받아요
炊飯器はほぼ未使用かつ新しくてサイズも小さいからせっかくだし、とパクもらってきたんだけど、やっぱ人んちの匂い（悪く言えば古い家のカビっぽい臭い）があるなーとなり 重曹とかで色々攻めてたけどめんどくなったのでまたあした
Practical /dev/tcp in the HTTPS Era https://lobste.rs/s/bbeigb #linux #security
https://blog.pkgforge.dev/https-via-http
洪 民憙 (Hong Minhee) shared the below article:
julian @julian@community.nodebb.org
<p>It all started <a href="https://community.nodebb.org/topic/18824/did-4.4.1-break-federation-with-lemmy-groups">with a report about federation breaking between Lemmy and NodeBB</a>. I was subconsciously aware that something was going on, but had chalked it up to network issues.</p> <p>Observed behaviour showed that some remote categories would be receiving content in spurts, with long gaps in between.</p> <p>I spent the next 3-4 days looking into it, but came up empty. Whatever was happening wasn't throwing any obvious errors, and along the way, I found what I <em>thought</em> was related (it was), but I wasn't sure why: against some Lemmy servers, the "follow"/"unfollow" mechanic would simply stop working, and this would often coincide with gaps in content. In some egregious cases, the flow of content stopped completely!</p> <p>Unable to make headway, I had to <a href="https://github.com/LemmyNet/lemmy/issues/5722" rel="nofollow ugc">reach out to the folks at Lemmy</a> to figure out what the issue was. NodeBB occasionally sends non-200 level responses depending on the activity. Specifically, the following scenarios:</p> <ul> <li>A remote user upvoting more than 20 posts in a single day (a spam prevention tactic) causing NodeBB to throw an error, which was caught and returned an <code>HTTP 500 Internal Server Error</code>.</li> <li>A <code>Dislike</code> activity, which is not currently handled by NodeBB. In these cases, NodeBB would send an <code>HTTP 501 Not Implemented</code></li> </ul> <p>When encountering either of these responses, Lemmy would return the activity back to the queue for later delivery and <strong>mark a delivery failure</strong>. If enough of these (~40) happened within 24 hours, Lemmy would give the instance a time-out and <em>pause delivery completely</em>.</p> <p>That was it — a quick pair of code updates later, and we started working through Lemmy's backlog of 4.1M activities.</p> <p>As of 4am this morning, <code>community.nodebb.org</code> is no longer behind <code>lemmy.world</code>.</p> <p><img src="https://community.nodebb.org/assets/uploads/files/1748873636999-d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" alt="d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" /></p> <p>Fun week. Let's not do that again LOL.</p> <p>v4.4.2 of NodeBB contains the updated logic for smoother Lemmy federation.</p>
Read more →I hope this email finds you at home and prepared.
"I've been thinking more and more about how much time I am almost certainly spending grading and writing feedback for papers that were not even written by the student. That sure feels like bullshit."
current status: docker-compose.fml
https://shkspr.mobi/blog/2022/08/dns-esoterica-bimi-svg-in-dns-txt-wtf/
<html><head></head><body>
You've been on the Internet a long time, right? Of course you know what BIMI is. All the cool kids do. But, for those of you who aren't hip to the jive of the Infobahn...
BIMI (Brand Indicators for Message Identification) is a new standard that can curb the issue of online impersonators. ... BIMI is a new standard that enables you to include your company’s logo alongside the emails you send. That way, your brand stands out among other emails, and your customers are sure that the emails are legitimate.How To Create a BIMI record
Wow! Much innovation! Such security! There's no way a fraudster could put a bank's logo on their dodgy spam, right?
*sigh*
OK, so in order for this not to be abused, most email providers require brands to pay for an expensive Verified Mark Certificate (VMC) - a digital certificate which says that you are the trademark owner of the logo.
How much does it cost?
US$1,499.00
Per year! No wonder no one is using BIMI.
Then it's just a case of sticking something like this in your DNS TXT records:
bgl gwyng
一般 Kyungmi Ahn ꉂꉂ(ᴖᗜᴖ*) 
Wez Furlong
TXTv=BIMI1;l=https://example.com/logo.svg;a=https://example.com/certificate.pemThat's nice, and all, but I don't think I've ever seen one in the wild. Even the BIMI Group haven't bothered paying for the VMC!
One of the few organisations who have set this up correctly is DigiCert. Because they're one of the orgs you can buy this service from.
dig txt default._bimi.digicert.com will get you:
TXT;; ANSWER SECTION:default._bimi.digicert.com. 3600 IN TXT "v=BIMI1; l=https://www.digicert.com/resources/DigiCertLogo_WhiteOnBlue.svg; a=https://cacerts.digicert.com/digicert_com_vmc_WhiteOnBlue.pem"You can read the PEM certificate using:openssl x509 -in digicert_com_vmc_WhiteOnBlue.pem -noout -text
Inside, you'll find this nugget:
data:image/svg+xml;base64,H4sIAAAAAAAACo1XXW/jRhJ8tn8FwzwF4NDzzaFhb3BRckmADRAgwL4eHFoxhePZhqiVN/…
Hmmm… H4sIAAA is the start of a base64 encoded zipped string.
Once decoded and unzipped, we find… the SVG logo!
It's fairly obvious that people want a nice logo next to their email in your inbox. If you're on GMail, you're probably used to seeing your friends faces smiling back at you. But that only works if everyone is on the same email system. So BIMI is a reasonable idea for a cross-provider standard.
There are several problems with BIMI.
The first is cost. If it were free then AbsolutelyYourBank@trust_me.biz could use the HSBC logo with impunity. I'm sure an extremely dedicated fraudster could spend the $1.5k and fool DigiCert into certifying their illegitimate use of someone else's logo. But it's unlikely to happen.
There's also a privacy issue. Because the BIMI logos are stored on a website, the website owner could track when they were downloaded and use that to work out who was reading their emails. Thankfully, both GMail and Yahoo proxy the images - so the provider doesn't get any additional analytics benefit.
Support is poor in GMail. Here's an email from LinkedIn:
As you can see, the BIMI logo is displayed by the email address - but is absent in the contact view.
Finally, DNS TXT records are limited to 255 bytes of data. That's why logos are restricted to being (fairly short) links.
I think the marketplace of ideas has answered this with a fairly resounding "no".
You can track adoption at BIMIBRadar.
It would be great to stick your face, logo, or picture next to every email you send. But the risk from fraudsters is just too high.
The cost of certification is necessary to stop misuse - but that also means that smaller brands and individuals are locked out. Which isn't what we want from an open Internet.
There's no worldwide brand registry which can certify your use of an image. And, even if there were, it would be a huge single-point-of-failure.
The conversation about BIMI chugs on in IETF mailing lists. Do get involved if you think you have something of value to add.
</body></html>
We know how hard it could be to handle the ever-increasing number of bad actors scraping your websites too well. Therefore, we decided to sponsor #Anubis¹ as a tool that helps users to block or at least slow down these bad actors.
We are currently evaluating how we could integrate Anubis or some similar solution to our stack and make it available as a uberspace command and backend.
일본어에서는 외래어를 줄일 때 앞쪽 몇 글자를 떼서 부르는 식으로 줄이는 구나 (썸네일 -> 썸네)
특징적인 글자 몇 개를 따서 줄이는 한국어랑 비교되는 것 같음 (마인크래프트 -> 마크)
「これからの社会を考えるための科学講義」／「科学を否定する人たち」 市民と共に 専門知識を踏まえて 朝日新聞書評から https://book.asahi.com/article/15808559
書評しました。
julian @julian@community.nodebb.org
<p>It all started <a href="https://community.nodebb.org/topic/18824/did-4.4.1-break-federation-with-lemmy-groups">with a report about federation breaking between Lemmy and NodeBB</a>. I was subconsciously aware that something was going on, but had chalked it up to network issues.</p> <p>Observed behaviour showed that some remote categories would be receiving content in spurts, with long gaps in between.</p> <p>I spent the next 3-4 days looking into it, but came up empty. Whatever was happening wasn't throwing any obvious errors, and along the way, I found what I <em>thought</em> was related (it was), but I wasn't sure why: against some Lemmy servers, the "follow"/"unfollow" mechanic would simply stop working, and this would often coincide with gaps in content. In some egregious cases, the flow of content stopped completely!</p> <p>Unable to make headway, I had to <a href="https://github.com/LemmyNet/lemmy/issues/5722" rel="nofollow ugc">reach out to the folks at Lemmy</a> to figure out what the issue was. NodeBB occasionally sends non-200 level responses depending on the activity. Specifically, the following scenarios:</p> <ul> <li>A remote user upvoting more than 20 posts in a single day (a spam prevention tactic) causing NodeBB to throw an error, which was caught and returned an <code>HTTP 500 Internal Server Error</code>.</li> <li>A <code>Dislike</code> activity, which is not currently handled by NodeBB. In these cases, NodeBB would send an <code>HTTP 501 Not Implemented</code></li> </ul> <p>When encountering either of these responses, Lemmy would return the activity back to the queue for later delivery and <strong>mark a delivery failure</strong>. If enough of these (~40) happened within 24 hours, Lemmy would give the instance a time-out and <em>pause delivery completely</em>.</p> <p>That was it — a quick pair of code updates later, and we started working through Lemmy's backlog of 4.1M activities.</p> <p>As of 4am this morning, <code>community.nodebb.org</code> is no longer behind <code>lemmy.world</code>.</p> <p><img src="https://community.nodebb.org/assets/uploads/files/1748873636999-d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" alt="d2b3dc1c-01f3-4203-b281-2406e949667d-image.png" /></p> <p>Fun week. Let's not do that again LOL.</p> <p>v4.4.2 of NodeBB contains the updated logic for smoother Lemmy federation.</p>
Read more →青い傷 - 猫又おかゆ (ぺるそにゃ～りすぺくと)
#NowPlaying
so now that bangbangcon and strange loop are gone, where are people doing their fun not-quite-tech/not-quite-art/not-quite-academic talks?
#wildlife #nature #birds #picnickingbirds
Picnicking Birds 🪶
아니
「これからの社会を考えるための科学講義」／「科学を否定する人たち」 市民と共に 専門知識を踏まえて 朝日新聞書評から https://book.asahi.com/article/15808559
書評しました。
친목도킹하고싶다 우웅 도킹도킹 친목도킹하실분
#wildlife #nature #picnickingcritters #squirrels
Random Wildlife
help, how do I properly take care of a brain frog? 
よそのこに、スパッツパーカーを着せたいラフです、。
저희 앵무가 한국어 욕설을 배웠습니다...
할머니톤으로 이 시부랄것아 이러는데
We ❤️ #opensource & we ❤️ being #GoogleFree
Break free from Big Tech tracking and go secure with Tuta! 💪 🔒
ここあにゃん 
SparklingOutlaw🍉
GENKI