0 Followers
0 Following
1 Posts
Clean the printing surface with dish soap and tepid water, and adjust your z offset. It appears to be too low from what I can see, but it’s hard to tell from a few pictures. It’s not supposed to be 0, and will depend on your specific printer, extruder, … You should aim to have fully filled squares, with no apparent “scars” on the surface left by the hotend moves. A nice rule of thumb is to be able to barely move a sheet of paper between your plate and the hotend freely without feeling friction (make sure to clean the tip of the hotend before). If after these steps it still produces these results, maybe there is an issue with you bed planarity, but most likely your pla has gone bad (I’ve even seen sealed bags go bad over a few years), try with a freshly dried filament, or a new roll from a reputable source

It really depends on your end goal I would say.

With a “bare” arch install you will probably learn the most (possibly the hard way). Also, arch being a rolling release, be prepared to update your system a lot, and fix problems as you go. That being said, I’ve been using the same arch install for a few years now and have had to fix stuff only once (Nvidia drivers, the usual culprit). If you want to try bleeding edge stuff, that would probably be the best option.

Nixos : same as you, tried, and left because the community couldn’t settle, and seemed to be fragmenting more and more. Also cool for bleeding edge stuff (thanks to the easy rollback)

You could also go for a debian based distro (debian or Ubuntu). My servers run on this, simply because they tend to require less maintenance.

There are also quite a few “docker-centric” distros, that can also be an option.

Whichever option you choose, if you use a lot of containers, mane sure to use something like docker compose, and keep your compose files safely somewhere (a git repository, a backup’d nas, …). You will keep a lot of nixos’s workflow goodness (everything is a config file), without some of the trouble.

Let my add a bit of love for the wurlitzer too :)
Can confirm, in my head op’s post meant : “I replaced some old appliance with something quite standard that won’t bother me for years”. The fizzing is just replaced with the warmth of undisturbed uptime after about 4-5 years

Most actual poisoning techniques don’t actually work that well. When I end up with a PDF, I usually strip out the existing text layer, apply a denoiser and a few other preprocessing steps to correct common errors, then a layout / reading order detector, and finally OCR the different blocs. This is against the most common poisoning techniques, and one of the most efficient, called : someone printed a document, forgot about it for 3 years, then scanned it slightly tilted (and dirty, crumpled, …), and the scanner decided to apply its crappy OCR.

Using screenshots of the PDF also avoid any kind of font face poisoning, and anti copy protection.

If you really, really need to protect your PDF, please consider accessibility first, then what would work imho is to use the scripting features of pdf to actually render your content on the fly. That would probably mess up most of the “automatic” processes.

It’s the “minus” button on switch

Ça m’intéresse aussi ! Pour l’instant le mieux que j’ai trouvé c’est chez selectspecs, prendre une paire “pas cher” et récupérer les verres. Sinon il me semble qu’ils peuvent faire la découpe+ assemblage, mais pas sûr qu’ils prendraient un cadre imprimé.

Si qqn trouve mieux, je suis preneur

I live in an area which has seen quite a few wildfires, and everytime they are put out with these planes using sea water. Never stopped anything from growing back, and it does grow back very fast !
For some reasons, there are now two models settings pages. One in the workspace, and another one in the admin settings (the old one was moved here). The feature you are looking for was probably just moved in the admin settings page

I went the /e/os way and quickly turned back. Not to dismiss the effort of the maintainers, but it really felt like a frontend on lineage os meant to sell alternative cloud services. I did not find convincing arguments over a bare lineage os and the pretty much forced /e/ cloud was a total turn off.

I went the “real” security / privacy way and switched to grapheneos. Very happy overall, already went thought with 2 major os updates, no issues whatsoever. Only issue would be if you want Google pay (won’t work on graphene). You’d need a pixel phone if that’s in your budget. The pixel phones are great at photos, but pretty “meh” otherwise