afaik you just listed features that the printer I mentioned (or if I am wrong, other similar printers) supports
it’s my bad for not mentioning all possible workflows, I was just a bit lazy and thinking of my personal documents only, which do not work well with further smart automation, because my batches are highly irregular. So the more manual approach is the best for me currently. Maybe possible with some future AI integration.
please elaborate
Epson WorkForce DS‑730N
put 100 sheets on the tray, it scans them all and either puts them all into a single pdf or multiple pdfs. Then you split / merge them in software.
You could buy an automatic scanner that takes a stack of docs and dumps the files to a network share.
afaik I’m on an older version of https://github.com/distribution/distribution/pkgs/container/distribution
my compose somehow doesn’t have much info … i should have made more notes
image: registry:2
i selfhost a pullthrough docker repository, so every container I use is stored in there and can be pulled offline.
a budget oriented one
It’s the other way around. You can get modpacks for a client super easy with a one click install, but adding them to a server is manual and you have to read on how to set that up. Not worth the effort if you want to quickly play with 2 people on LAN.
There is one more catch: you can’t play LAN games either without a valid session ID. (start singleplayer world -> ESC -> open LAN multiplayer)
You have to properly start a server so that you can change the conf to allow offline accounts.
The godot docs have their bad parts though. For example when it comes to godot shaders, at the time when I tried it, the docs were out of date. The doc listed some tokens that didn’t exist anymore and others where the functionality I observed differed from what the doc said and sometimes the doc didn’t document anything meaningful at all like “TIME - this is the time” without explaining the unit, format or interval or anything.
Get one of those learning kits that come with most of MCUs, which have a lot of random stuff (like LEDs, motors etc.) that you can hook up to the pins and write C programs to control them. Learn the different protocols that are used to talk to other devices, like i2c, uart, spi etc. and then buy some hardware that you can talk to via this protocol. Like a sensor, a gps module or an IMU or EEPROM.
It’s conceptually pretty similar to how computers and device drivers do it. There is some communication protocol and you can write or read some values over it to use any device. It’s just way easier to start small and build up experience from there.