kensand

Just following your above link, you could pre-convert your comics using this: https://framagit.org/nicooo/kumiko

To me it looks like tuning your pressure advance might help.

https://ellis3dp.com/Print-Tuning-Guide/articles/pressure_linear_advance/introduction.html

Ah yes, keeping your Lambda functions running, rendering the main benefit of them pointless 🙃

People really should just set up a Fargate task instead...

This process is called 'bootstrapping', and is actually quite common in software. For example, the C compiler is written in C. The first iteration of the C compiler was written by hand in assembly code with a very limitted feature set, and that compiler was then used to compile the next iteration, allowing the second version (I'm not sure it was actually the second version; there may have been a few iterations in assembly) to be written in C itself.

For Forgejo, you dont actually need Forgejo to build Forgejo; just a computer with the Go compiler and any other dependencies. Then, once you have the first version, you can publish the code you have on Forgejo. Nothing too crazy there 🙂

This also leads to 'dogfooding', which is a whole other term...

Since you're a bit concerned about self hosting and collaboration, I would recommend Codeberg - they are a non-profit based in Germany with widespread support and, as far as I know, is the public Forgejo instance with the largest user base.

If you want, you can also host your own Forgejo instance and mirror your Codeberg repos to it. That way you can have two copies of your data, just in case Codeberg ever goes offline.

You could also potentially use Gitlab, but I would personally prefer something Forgejo based. Forgejo has been much more responsive/snappier in my opinion; Forgejo is primarily written in Go, while Gitlab is mostly Ruby.

https://forgejo.org/compare-to-gitea/

CI actions and actually being free software are my main notes, but there are many reasons.

A better* fork of Gitea!

IMO, the issue here is that Microsoft appears to have violated the MIT license requiring inclusion of the original author's copyright notice. I think he has every right to be salty about that violation.

In your analogy, the sign on the furniture says:

Free, but if anyone asks, you got this furniture from .

Microsoft took the furniture from the curb, but isn't telling people whom they got it from.

I agree in regards to your opinion that he shouldn't be complaining about the fact that someone forked his project, that just the nature of the MIT license. However, I do think he is justified in being upset that the license was violated. Hopefully this gets remedied; it's not hard nor expensive for Microsoft to add his name to the copyright notice in the license.

I'd be mildly worried about the heat/cold cycles damaging the insulation of the non-outdoor rated cable, but it would probably take a long time even in an area that gets extreme temperature swings. If you're moving in the next few years, I'd just stick with standard riser cable. However, if there's any location that is at risk of getting wet or exposed to sunlight (UV), you should definitely stick with outdoor rated cable.

I have an Elegoo Saturn 4 Ultra. I hate that it's proprietary, but in the resin printing world the only non-proprietary option is Prusa, and it was just too small and expensive to justify. My Elegoo doesnt get network connectivity (so no risk of unapproved updates), and I use prusa slicer to slice and then uvtools to convert to the "encrypted" chitubox format. Since the printer isn't allowed to update, I'm not worried about ever being forced into using chitubox.

I don't really care about network connectivity for it; the built in camera is useless for me. I just have a rpi zero with a webcam on it for monitoring, and I also have an IOT switch controlled by that pi via a lan-only http server with a toggle button to control its power. If I see a print is failing via the webcam, I just cut power to the whole printer to stop it remotely. This works even outside my LAN via VPN.

I do still have to start prints the old fashioned way using a usb stick. This doesn't bug me much, since I have to go check on resin levels, make sure there's no crap in the tank, etc before starting a print anyways. I have a short usb extender cable to avoid wearing out the usb port on the printer itself as well. I have mucked about with using the rpi as a dummy usb drive where I can just upload files to the rpi and then the printer reads off of it via the usb port, but I couldn't get it working :/

I'm happy enough with the printer itself - it's fast, reliable (so far) and produces some high quality prints. The price was very reasonable at the time (iirc $450 for the printer, $250 for wash and cure station), all things considered. If someone ever produced a mainboard that supported an open-source firmware for it, I would buy and install it in a heartbeat.

I'm assuming there was no ID or contact info with it, since you probably wouldn't be asking if there was.

Hypothetically, if you were to give it to the police, how would the police know that who the rightful owner is? If I walk into a police station right now and say I lost $200, do you think they would hand over $200 to me? No, I have no way of proving thats my money, and they wouldn't believe me for a second.

Keep it. Lord knows everyone could probably use an extra few hundred bucks these days...

It doesnt look too hard to build from source if you want to go that route... You could just make a debug apk and install it with ADB.