> a 256GB SSD with 16GB RAM is quite useless for a home server
Not that I would buy it new, no, but 16GB for a home server can be quite fine. If I didn't have the 2x3 TB NAS disks (sounds ridiculously small now, right) - that would actually be enough.
First of all, hardly anyone cares (default email signatures etc.pp even if the people don't want that - but you said legally bindign, and I think that just usually never happens.).
And second, at least in Germany it's also somewhat of a bullshit situation that 80% of the people who do a "normal" Computer Science degree don't have that (Diplom-Informatiker/M.Sc), but the 20% who happen to study at a certain uni in a certain degree (that is mostly related, but not the default Computer Science/Software Engineering one) are/were getting their "Diplom-Ingenieur".
This is kinda topical for me as I just scanned some barcodes off some CDs and my results were: 90-95% detection rate on MusicBrainz, and for the rest it ranged from "yeah, this is clearly the same thing with 10 tracks" to "oh my, there are 7 different regional versions with 10, 11, 12, 13, 13 tracks and I need to pay attention to grab the correct one so the last 3 songs are not wrong" and "this is some 5 EUR sample from an unknown label and really hard to find. Or their docs are not great, I had wished for something like "artist of track 1 = X and artist of track 2 = Y" that probably would have narrowed it down the most.
When digitising my collection and using MusicBrainz as the main source of metadata, I had to add about 50 albums nobody had entered before. It has a huge amount of stuff - it already had 95% of my collection - but it's not perfect.
The best way to distinguish an album (after barcode or name/artist, and medium) is number of tracks, and if that's not enough, release year/country. I got my metadata by using their Picard tagger and the CD TOC (as it contains the number and lengths of tracks, it's much less ambiguous), but of course opening every case and putting every CD in the drive is a lot more effort than barcode scanning.
You can use the advanced search syntax if you need to look up multiple fields at once. https://musicbrainz.org/search -> Type "Release", method "Indexed search with advanced query syntax"
The difference if you can film out on the street (random people walking by) or just your property (my own fault if I approach your door).
Some countries have laws for this, as in you can only point the camera so that you don't catch everyone. This can have downsides, e.g. if you have no (even short) front yard and your (organization's) door is directly on the curb - but I completely agree that this is just tough luck, the privacy of random people walking on public property past private property should not be filmed.
I have OpenBSD running on my old 2004 Centrino notebook (I might be lagging 2-3 versions behind, I don't really use it, just play around with it) and it's fine until you start playing YouTube videos, that is kinda hard on the CPU.
Yes, NetBSD and OpenBSD work fine on the 2005 T42 but as you say video performance is low. Recent OpenBSD versions have had to reduce the range of binary packages (i.e. outside of the base and installed with pkg_add) on i386 because of the difficulty of compiling them (e.g. Firefox, Seamonkey needing dependencies that are hard to compile on i386, a point the poster up thread made).
Not as elaborate a story, but in a former office we had special office chair that, when you sat down with a bit of force it would switch off one or two specific monitors.
That also took a few minutes to debug why this one coworker came back from lunch, plummeted down into his chair, and someone else's screen went out.
I have relatively good experience with both Rust and Go here. It still works and maybe you need update 2-3 dependencies that released an incompatible version, but it's not all completely falling apart just because you went on a vacation (looking at you npm)
Not that I would buy it new, no, but 16GB for a home server can be quite fine. If I didn't have the 2x3 TB NAS disks (sounds ridiculously small now, right) - that would actually be enough.
reply