feb

That one actually looks more like a real kernel with services like memory management, syscalls, processes and context switching. Nice work.

For a functionnal language, TCO is really a must have. How would you do the equivalent of loops without it ?

There's another HN thread about this project: https://news.ycombinator.com/item?id=46144199

For those of us who are not used to the acronyms, DUI means Driving Under Influence. Similar term is DWI, Driving While Intoxicated.

There's PeerTube (https://peertube.tv/) which is based on Free software (https://joinpeertube.org/).

This sounds like the technique shown by 3D Printing Nerd on YouTube: https://m.youtube.com/watch?v=oHPrnYMdLow There they called it computed axial lithography.

The difference is surprising. Digging deeper, the US shop does not include shipping or taxes. To get an idea, I tried for CA and that already adds $12. That's already $38 without custom tax and VAT.

Fully charging the battery can cause it to age more quickly and lose capacity. Limiting charge level helps to protect it, especially when it's always connected to a power supply and don't need the battery that much.

Nice system built with only a couple of C99 macros. That small header also achieves matching for specific C types over the "sum types".

In the context of C99, isn't tagged union the more usual name instead of sum type?

Actually Qwant.com uses bing API too and has a warning at the top of their homepage.

From valetudo.cloud: Conga is a brand that uses existing robot designs with a slightly customized cloud.They’re not a robot manufacturer.

The paper explains how to get the profile of the key to 3D print the equivalent of key blanks. But one needs the cuts in the key and that part is secret that cannot be easily detected from a photo of the key hole.

It disappeared without any visible explanations. Apparently, it was a a friendly fork of the Breath project (https://github.com/cb-linux/breath) by Apacelus (https://github.com/Apacelus/Apacelus). But Apacelus stopped working on it on May 26th (https://github.com/Apacelus/Apacelus/commit/c84ee94310144ec9...).

There's another project on Github with the same name: eupnea-linux-backup https://github.com/eupnea-linux-backup

Filippo describes how evolutions in the source code and hidden assumptions caused a bug in a special case implementation he kept for performance reasons. This is a great example of how the incompleteness of the old Weierstrass curves multiplication formulas still bites us and how he uses the opportunity to get valuable lessons from this accident. It also shows again how optimizing for performance can cost security and hurt maintainability.

And it's also illegal in EU. The GRPD imposes to have the choice to reject tracking cookies. And it must be easy to reject, not hidden somewhere or requiring one to manually delete the cookies with the browser mechanisms.

According to a german news report [1], it could be due to material fatigue.

[1] https://www.rbb24.de/panorama/beitrag/2022/12/berlin-karl-li...

It seems like a decent guide, though like others mentioned, you should download and run the code most of the time, except for trivial changes.

Actually, that's not true at all. Code review is not a replacement for automated builds and testing. That's what Continuous Integration is for. Let humans concentrate on what they do best (understanding and comment on code) and don't lose their time and patience with things that can be automated.

Projects often enforce that by running CI on code submitted for review and it cannot be accepted as long as a CI fails. It also reduces breakages for other devs of the builds of the code base.

The README is a bit optimistic about it the security model. Like the parent said the room UUID is a very critical asset and should be handled as a critical secret. Sadly, users may not know that.

In addition, the README says one can audit the full code and the assets used. For example, it suggests to audit the gh-pages branch for the static assets. But when hosting with github, that branch could change at any time and deliver non-audited content. Powerful attackers like government could do it easily, and less powerful ones too.

This article about IKEA boxes sounds a lot like the cake mix marketing story. But apparently, that story is a legend: https://gobraithwaite.com/thinking/cake-mixes-fresh-eggs-and...

And maybe this study should be taken with a grain of salt too.

Impressive work by GAMI who are working on it since decades. AVWeb made 2 videos on the subject of leaded avgas and on how hard it is to get it approved. In addition, the FAA launched several failed attempts with the industry at large.

  * https://www.youtube.com/watch?v=9F-WngVMJBQ The Long, Twisted And Slightly Ridiculous Story of Avgas Part 1
  * https://www.youtube.com/watch?v=Mvse4Xhzwuk The Long, Twisted And Slightly Ridiculous Story of Avgas Part 2

On the other hand, there are some niches where compression tension, aka tensegrity, may have a practical utility. For example, the current lightest hammock stands are inspired by it. The HandyHammock stands [1][2] use cords to reduce the weight of the poles. Sadly, that model is not manufactured nor sold anymore. The small company Tensa Outdoor makes and sells the Tensa4 [3] which is based on an equilibrium with poles and guy lines. They also have plans for a DIY version [4], called tensahedron stand. The DIY 3-person Hammock Stand from The Ultimate Hang is also inspired by tensegrity [5]. The 3-Pole, 3-Person Tensegrity Stand (DIY) is even more impressive [6].

Although none of them are floating like in the sculptures, the concept and the art inspired some practical constructions.

[1] https://www.ddhammocks.com/images/products/_ALL_PRODUCTS/Ham... [2] https://theultimatehang.com/2012/12/11/handy-hammock-stand-r... [3] https://www.tensaoutdoor.com/product/tensa4-hammock-stand/?v... [4] https://www.tensaoutdoor.com/make-your-own-tensahedron-stand... [5] https://theultimatehang.com/2013/04/02/3-person-hammock-stan... [6] https://sectionhiker.com/portable-hammock-stands-for-camping...

About longevity, on https://www.stringbike.com/stringbike_support_questionsandan... they say strings last between 500 to 1500km.

Bike chains supposedly last from 500 to 5000 miles (https://www.bikeshepherd.org/how-long-do-bike-chains-last/) depending on usage and maintenance.

Transmission via shafts is also less efficient. It doesn't matter much on a motor bike where there's plenty of power. But on a human powered bike, every watt counts. See for example https://www.cyclingabout.com/chainless-shaft-drive-bicycles/ for more information.

The proposal consists in filtering out crappy or scoring sites based on how much affiliate links and ads they use. In addition, it could also penalize:

  * GDPR popups
  * excessive JavaScript
  * presence of modal dialogs requesting email

In the PS3 they lacked a real random number in ECSDA computation. That effectively broke the signature and actually made it possible to recover the private key.

For more info see for example:

* https://www.cs.uaf.edu/2012/fall/cs441/students/sc_ps3.pdf

* A presentation at CCC about how hackers broke the different security features or PS3 including ECDSA https://media.ccc.de/v/27c3-4087-en-console_hacking_2010#t=2...

When sleeping on your belly, doesn't your back "push" on your lungs? There's then more mass to compress your lungs than when sleeping on your back.

Even local variables of functions can take up a lot of room can take quite a lot of space. Especially when you minimize use of the heap. Using the stack instead of heap where possible makes for clean automatic free-ing of unused memory.

Those all make sense for long trips. For the short trips, users will more likely charge at home and thus there will be less demand for "fuel" stations.

The more one dives into the relationship between society and energy, the more it appears energy sources and availability mold society, like transport, food, architecture, politics, urbanization, philosophy or medicine. The book "Oil, Power, and War: A Dark History" by Matthieu Auzanneau (Or in French: "Or Noir") shows that quite well.

Out of curiosity, what do you consider the worst architecture choices in IRC ? And what would be better solutions ?