"And here's the key bit...", etc. I agree there's a few signs that this was at least editorialized by AI. That being said, saying it's slop is a bit of a stretch.

Not quite. The Kuru Toga mechanism that rotates the led every time you pick up the pencil is present on the cheaper models and is also present here.

The big feature on this pencil is an adjustable automatic lead extrusion mechanism on top of the rotation mechanism.

Looking at the source I don't think that's true -- it's using GitHub specific APIs to read/write files. It's not standard git so any remote wouldn't work, and the mechanics are more akin to a key-value store than git really.

Not to say you couldn't add a generic git protocol to this, just that that's not being done here.

I think it's pretty clear from the readme that this is a humorous proof of concept more so than anything someone should seriously use.

True, but imagine this use case:

A messenger file with hardcoded settings and a hardcoded PGP key, stored on a USB stick.

You send a message.

Then you physically destroy the USB stick.

The client, the key, and the configuration are gone.

At some point the joke starts looking suspiciously like a dead-drop communication protocol.

How do you like that, FBI?

That’s literally what release 1.03 enables.

From the translated readme:

Macaroni Messenger is not a joke. It simply refuses to complicate solutions unnecessarily.

That's why some technical decisions might look like a joke.

Sometimes it really is a joke. But most of the time, it's just the simplest working option.

https://news.ycombinator.com/item?id=48487542

Speed running is so bizarre to me, the rules seem so arbitrary. I struggle to see how any form of hardware level modification that results in a meaningful deviation in the behavior of the game would be allowed. At that point what's the difference between smudging your disk and using a GameShark, etc?

Similar thoughts on things like shiny hunting in the Pokemon community.

Are you also confused about kids playing outside making up arbitrary rules for their games? The point to have fun by challenging yourself in a competition with others. That means allowing things that make the competition more fun/challenging and disallowing those things that trivialize it. Sometimes that's a subjective thing.

What's 'allowed' in a speed run is decided by the community who do the speed running. Further, run leaderboards are broken into categories based around defined parameters. So, perhaps there would be a category unique to hardware manipulation such as this. For major speed running games, the rules are often very well defined and enforced.

The Panasonic Toughbook range isn't even the same class of device as Macbooks. They're like twice the size and significantly heavier.

>The Panasonic Toughbook range isn't even the same class of device as Macbooks.

You are precisely correct, which is why you should evaluate them. Not only will it run any code you want it to, it's extremely well supported in Linux, built solidly, and you can buy parts directly from Panasonic.

Not all of them are as bulky or heavy as the fully-rugged models. This one is "semi-rugged", not that much thicker than a ThinkPad.

The size, texture, precision, functionality (tapping, multi-finger), palm rejection are all just about flawless on Macbooks. Other manufacturers have good trackpads that are great at some of these things but never all of them.

What’s wrong with the OCL if you’re a business owner?

I don't want to ask Prusa for permission.

Permission to do what exactly?

Was there something before the OCL you could / were planning to do that the OCL now prohibits?

I don't know why it's so mysterious for you. It's not an open hardware platform and prusa is the gatekeeper here.

I think it's as misterios to GP as to anyone else, inclusing yourself given how difficult it seems to be to come up with an actual answer.

No. It's easy. I develop tools. Some of which are tools I may want to sell to other. if I am dependent on a platform to make money, I don't want to ask permission to do so.

You still didn't answer either of their questions:

> Permission to do what exactly?

> Was there something before the OCL you could / were planning to do that the OCL now prohibits?

Make modifications and sell it, duh. It's something to contemplate when I am trying to solve a manufacturing problem.

I don't know why is it so difficult for you to conceive based on well known definition of open hardware and the analogy to free software.

I look forward to your modifications and advancements in the 3d printing community that are published under completely open licenses!

Presumably the original dev that implemented the changes for this functionality that pulled the repo does not want to be associated so some level of squashing was required but yeah, the whole history was maybe a bit silly.

Apparently the full history is here: https://github.com/DARKFiB3R/OrcaSlicer-bambulab

And it doesn't look good. This has me call into question the caliber of developer who made the fork. No sane open source project would allow this to be upstreamed in this shape

I mean, the presence of a CLAUDE.md file tells me everything I need to know about this fork.

5 hours with LiFePo4 and 8 hours with Li-ion since the battery system in the Reform Next should support both chemistries you can choose battery longevity or longer runtime and more frequent battery replacements.