Recent submissions

Comment · 1 month ago
It seems people are missing the point: it's not even the submodule incompatibility that's going to become an issue majorly (like python2 --> python3 but worse), the main issue is the loss of traceability for repos that changes in place (which I assume many will do). Imagine what will happen to these:

- SLSA and Provenance or SBOM data in the supply chain security that uses commit hash. All the previous images are now pointing to a non-existing commit

- All the documentation and tooling as the article calls out

- All your traceability links from your project tool to your git repo, they will lose all the past data as it will be dead links

So I hope there IS NOT a migration path for in-place replacement!

Comment · 3 years ago
This seems very simiilar to Gitlab's MR. Does anyone know all of them to highlight their strengths and drawbacks?
Comment · 3 years ago
Comment · 4 years ago
Comment · 7 years ago
Most of the 3d printer firmwares can detect heat spikes and stop heating the extruder to prevent fire and you can control your printer's power with rpi with a simple relay circuit. You can also setup a bot with camera to alert you via mail/message/telegram if there is a fire risk. These are the common precautions I have seen people take.
Comment · 8 years ago
I am currently leading the on premise hosting of a Gitlab instance and I can say this with ease: I have been spending 1 day of each week for ops work. Let it be helping people, database adjustments, admin stuff, hardware checks, etc.
Comment · 8 years ago
Also you can just use github and some macros to auto commit changes on save. This way you can edit from mobile and desktop and you will have index and history capabilities
Comment · 8 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton