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

A few people have pointed out that the memeing comes because of Rust’s enthusiasts being annoying about proselytizing, and in that case please read this as nudging your dunks towards “Rust didn’t save you” so they’re more effective.

0
0

#opensource #privacy #techpolicy #hardware #iot #surveillance #qualcomm #arduino #makers #infosec #datarights #termsandconditions #cloudcomputing | Adafruit Industries | 163 comments

Qualcomm-owned Arduino quietly pushed a sweeping rewrite of its Terms of Service and Privacy Policy, and the changes mark a clear break from the open-hardware ethos that built the platform. The new documents introduce an irrevocable, perpetual license over anything users upload, broad surveillance-style monitoring of AI features, a clause preventing users from identifying potential patent infringement, years-long retention of usernames even after account deletion, and the integration of all user data (including minors) into Qualcomm’s global data ecosystem. Military weird things and more. Several sections effectively reshape Arduino from an open community platform into a tightly controlled corporate service with deep data extraction built in. The most striking addition: users are now explicitly forbidden from reverse-engineering or even attempting to understand how the platform works unless Arduino gives permission. That’s a profound shift for a brand long embraced by educators, makers, researchers, and open-source advocates. With the cloud having a rough day and many systems offline, yesterday... Anyone invested in transparency, community governance, or data rights should read these documents closely. Links: https://lnkd.in/efKSip3e https://lnkd.in/eKDWCZT4 Somewhere an old Uno is whispering “this is not my beautiful life"... Forbes did a couple press-release style "features" with incorrect information that Qualcomm or Arduino supplied, obviously Qualcomm has severe issues with fraud, acquisitions, et. this was 3 DAYS AGO - Former Qualcomm executive sentenced to prison for $180M fraud scheme. @Bill Curtis & Steve McDowell please consider a revisit... Nakul Duggal seems to be the one that will end up taking the fall for this, the CEO of Qualcomm is not in the press release for the sale (and the press release seems like it was made by ChatGPT when you put it through those AI detectors?).. ANY WAY - Naukul and the Ardunio better get a ride in the over 10 Gulfstreams, which are a puzzle to investors, why so many? And why get a G800 now that's over $75m ...? That's how much Arduino has in funding... US's Qualcomm adds G800 to corporate jet fleet... https://lnkd.in/ddiCikpf LIKE, SHARE, AND SUBSCRIBE FOR MORE DIY ELECTRONICS AND OPEN SOURCE NEWS @ Adafruit Industries Qualcomm Arduino Cristiano R. Amon Massimo Banzi Fabio Violante Pietro D. Marcello Majonchi Federico Musto (龍獵人) <-- #opensource #privacy #techpolicy #hardware #iot #surveillance #qualcomm #arduino #makers #infosec #datarights #termsandconditions #cloudcomputing | 163 comments on LinkedIn

www.linkedin.com

0
0

@alexmu But we do know the right level! They are the boundaries at which we accept the user data coming from outside the system. For example in Haskell or Java, I'd propagate such errors to a boundary and make a decision there instead of crashing at somewhere deep in in the program. I think it is a culture thing.

very long blather about rust errors

@abnvAbhinav 🌏 @alexmu so .. folks don't always discuss this in presentations of rust errors (and I'm not here to totally defend where rust errors wound up) but the question of recovery boundaries was _central_ to the design discussions and iterations.

many of us had experienced working in C++ (or eg. Java) where "pervasive exceptions from any possible expression" + "lots of mutable state that touches all other mutable state" meant that there was rarely any place in a real-world try/catch programs where a catch would actually wind up with a program in a safe, non-corrupt state.

(there's a whole literature about this in C++ called "exception safely levels" -- en.wikipedia.org/wiki/Exceptio -- which of course nothing can check or reason about statically and most programs completely fail to adhere to. It's extremely hard to even consistently write exception-safe C++ destructors.)

in addition, there are a bunch of things in C++ at least that _don't_ throw, but _do_ kill the process. and that's going to be true in most systems languages. rust has unsafe! and if you segfault or execute an illegal instruction your process is toast.

given that, we saw and continue to see a lot of programs adopt "process boundary" as the safe(r) boundary for "major error recovery". web browsers and many network servers for example tend to do process separation. so there was an argument that "unrecoverable error that kills the process" is probably a good primitive concept to include, and for super-pervasive errors they should probably be routed into there.

but of course, not all errors are fatal, and some are a bit more "expected" and _some_ seem meaningfully recoverable (eg. see the distinctions between checked and unchecked exceptions in Java), and so we iterated a bunch on the question of lesser types of error (including a condition-handling system a bit more like common lisp) and ultimately landed on the result type, and a copy of Swift's ? operator for propagating it, which is .. eh .. ok? not great but at least fairly explicit and well-marked, and easier to reason about than "every expression everywhere might throw mid-evaluation".

the result is a bit of a muddle. error and result shipped with too little support for abstraction and composition, and there are probably too many ways to panic, and unwinding and unwind-catching is a thing of arguable utility (I'd kinda prefer to remove both). but the whole design does have a rationale behind it, it's not just foolishness. at worst I'd say "they shipped something incomplete under time pressure and limited information about how it'd wind up being used".

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

> 日本ではVine LinuxやKondara MNU/Linux、Momong Linuxも人気でした。
ってKondaraとMomongaが登場してる❤️って思ったらaが仲間外れだったw

第888回 【はじめてのUbuntu刊行記念】 あなたのUbuntuはどこから、どこへ? | gihyo.jp
https://gihyo.jp/admin/serial/01/ubuntu-recipe/0888

0
0
0
0
0
1

#opensource #privacy #techpolicy #hardware #iot #surveillance #qualcomm #arduino #makers #infosec #datarights #termsandconditions #cloudcomputing | Adafruit Industries | 163 comments

Qualcomm-owned Arduino quietly pushed a sweeping rewrite of its Terms of Service and Privacy Policy, and the changes mark a clear break from the open-hardware ethos that built the platform. The new documents introduce an irrevocable, perpetual license over anything users upload, broad surveillance-style monitoring of AI features, a clause preventing users from identifying potential patent infringement, years-long retention of usernames even after account deletion, and the integration of all user data (including minors) into Qualcomm’s global data ecosystem. Military weird things and more. Several sections effectively reshape Arduino from an open community platform into a tightly controlled corporate service with deep data extraction built in. The most striking addition: users are now explicitly forbidden from reverse-engineering or even attempting to understand how the platform works unless Arduino gives permission. That’s a profound shift for a brand long embraced by educators, makers, researchers, and open-source advocates. With the cloud having a rough day and many systems offline, yesterday... Anyone invested in transparency, community governance, or data rights should read these documents closely. Links: https://lnkd.in/efKSip3e https://lnkd.in/eKDWCZT4 Somewhere an old Uno is whispering “this is not my beautiful life"... Forbes did a couple press-release style "features" with incorrect information that Qualcomm or Arduino supplied, obviously Qualcomm has severe issues with fraud, acquisitions, et. this was 3 DAYS AGO - Former Qualcomm executive sentenced to prison for $180M fraud scheme. @Bill Curtis & Steve McDowell please consider a revisit... Nakul Duggal seems to be the one that will end up taking the fall for this, the CEO of Qualcomm is not in the press release for the sale (and the press release seems like it was made by ChatGPT when you put it through those AI detectors?).. ANY WAY - Naukul and the Ardunio better get a ride in the over 10 Gulfstreams, which are a puzzle to investors, why so many? And why get a G800 now that's over $75m ...? That's how much Arduino has in funding... US's Qualcomm adds G800 to corporate jet fleet... https://lnkd.in/ddiCikpf LIKE, SHARE, AND SUBSCRIBE FOR MORE DIY ELECTRONICS AND OPEN SOURCE NEWS @ Adafruit Industries Qualcomm Arduino Cristiano R. Amon Massimo Banzi Fabio Violante Pietro D. Marcello Majonchi Federico Musto (龍獵人) <-- #opensource #privacy #techpolicy #hardware #iot #surveillance #qualcomm #arduino #makers #infosec #datarights #termsandconditions #cloudcomputing | 163 comments on LinkedIn

www.linkedin.com

0
0
0

Today's letter to my congressman.

Dear Congressman,
The point of this message is to urge you to use your seat on the House Judiciary Committee to investigate the partisan hackery that appears to be rampant within the Department of Justice.

As I pointed out in my last email, Kash Patel appears to have lied to your face during his statements regarding Mr. Trump's name being mentioned in the Epstein Files. I hope you will avail yourself to demand Mr. Patel clarify his remarks, and apologize if warranted.

Additionally, I'd like to draw your attention the the testimony by Lindsey Halligan today in the DOJ prosecution of James Comey. Halligan testified that she did not present to the entire grand jury the indictment that she presented to the court itself.

I'm not writing to defend James Comey - he's awful, and remains awful. I'm writing because 1) it seems like the Department of Justice (Comey, Patel) is making a habit of misleading the Congress, and 2) the current crop of DOJ lawyers - specifically Ms. Halligan - are inept at doing their jobs.

Fixing these two problems are exactly what your Committee is tasked with fixing. Please step up your efforts.

Finally, let me thank you for changing your vote to support the release of the Epstein Files. I'd glad that Mr. Trump's fit of pique was able to assuage your valid and thoughtful concerns about the privacy of Epstein's victims.

Regards,

0
0
0
0

Today's letter to my congressman.

Dear Congressman,
The point of this message is to urge you to use your seat on the House Judiciary Committee to investigate the partisan hackery that appears to be rampant within the Department of Justice.

As I pointed out in my last email, Kash Patel appears to have lied to your face during his statements regarding Mr. Trump's name being mentioned in the Epstein Files. I hope you will avail yourself to demand Mr. Patel clarify his remarks, and apologize if warranted.

Additionally, I'd like to draw your attention the the testimony by Lindsey Halligan today in the DOJ prosecution of James Comey. Halligan testified that she did not present to the entire grand jury the indictment that she presented to the court itself.

I'm not writing to defend James Comey - he's awful, and remains awful. I'm writing because 1) it seems like the Department of Justice (Comey, Patel) is making a habit of misleading the Congress, and 2) the current crop of DOJ lawyers - specifically Ms. Halligan - are inept at doing their jobs.

Fixing these two problems are exactly what your Committee is tasked with fixing. Please step up your efforts.

Finally, let me thank you for changing your vote to support the release of the Epstein Files. I'd glad that Mr. Trump's fit of pique was able to assuage your valid and thoughtful concerns about the privacy of Epstein's victims.

Regards,

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

Suppose you run your web app with gunicorn. And for metrics, you run the Python Prometheus client in multiprocess mode, since you have multiple worker processes. And you set PROMETHEUS_MULTIPROC_DIR the way the docs tell you to.

Now, what's your favorite way to implement the other thing the docs tell you to do?

> This directory must be wiped between process/Gunicorn runs (before startup is recommended).

So. Do you wipe it only when gunicorn itself boots? Do you wipe it on every worker process start? Periodically via cron-type job? Something else?

Genuine question. Asking for a friend, and the friend happens to be me.

0

Suppose you run your web app with gunicorn. And for metrics, you run the Python Prometheus client in multiprocess mode, since you have multiple worker processes. And you set PROMETHEUS_MULTIPROC_DIR the way the docs tell you to.

Now, what's your favorite way to implement the other thing the docs tell you to do?

> This directory must be wiped between process/Gunicorn runs (before startup is recommended).

So. Do you wipe it only when gunicorn itself boots? Do you wipe it on every worker process start? Periodically via cron-type job? Something else?

Genuine question. Asking for a friend, and the friend happens to be me.

0

📰🇪🇺 Die plant nach Kritik aus der Branche eine Lockerung der Auflagen für Technologiekonzerne. kritisierte den Gesetzentwurf scharf. „Dies ist der größte Angriff auf die digitalen Rechte der Europäer seit Jahren“, sagte .

👉 Lies mehr: handelsblatt.com/politik/inter

0
0
0
0
0
0