g1n016399 | 10 years ago | on: Deciding on which ideas to pursue
g1n016399's comments
g1n016399 | 10 years ago | on: EFF: Tell Us Your DRM Horror Stories about Ebooks, Games, Music, Movies and IoT
g1n016399 | 10 years ago | on: DRM Non-Aggression on the Table at W3C
... and support the GPL compliance efforts of organisations like Software Freedom Conservancy:
g1n016399 | 10 years ago | on: Harmful software, and less harmful alternatives
g1n016399 | 10 years ago | on: Distribution packages considered insecure
Ack on the version stuff.
g1n016399 | 10 years ago | on: Distribution packages considered insecure
apt-get -t unstable install $(debsecan --suite sid --format packages --only-fixed)
g1n016399 | 10 years ago | on: Distribution packages considered insecure
Ubuntu Snappy packages are based on the normal Ubuntu packages so they will be at the same versions.
g1n016399 | 10 years ago | on: Distribution packages considered insecure
g1n016399 | 10 years ago | on: Ask HN: Does this old horse have a few years of useful work left?
http://www.fsf.org/resources/jobs/embecosm-compiler-engineer
g1n016399 | 10 years ago | on: ZFS is the FS for Containers in Ubuntu 16.04
Debian uses the compile-at-install-time workaround but Ubuntu ships binaries, which is a GPL violation.
g1n016399 | 10 years ago | on: TP-Link begins router firmware lockdown due to FCC proposed regulation
g1n016399 | 10 years ago | on: ZFS is the FS for Containers in Ubuntu 16.04
g1n016399 | 10 years ago | on: TP-Link begins router firmware lockdown due to FCC proposed regulation
g1n016399 | 10 years ago | on: YouTube change served lower-quality video to Firefox 43 for 2 weeks
g1n016399 | 10 years ago | on: File format wiki
http://fileformats.archiveteam.org/wiki/Dendrochronology
http://fileformats.archiveteam.org/wiki/Quantum_computer
http://fileformats.archiveteam.org/wiki/TLD_.mobi
http://fileformats.archiveteam.org/wiki/Endianness
How is any of these things a file format? Because the definition of a file format in the FAQ (<http://fileformats.archiveteam.org/wiki/FAQ:File_Format>) is so broad that it can be made to encompass basically everything. The manifesto that started this site is a rambling sermon that doesn't clarify anything in this respect: it just repeats "let's solve the problem" without even properly defining what the problem is.
There are also other issues. The classification scheme is often Procrustean and confused. Error messages were until recently mixed up with error detection codes, which conflates two different meanings of "error". Similarly FUSE shares a category with HFS+, even though the former is an API, and the latter a disk format; distinct things which just happen to share the name of "file system". The pages are rather short and consist mostly of lists of links. Given the above-mentioned lack of clearly defined scope, I suspect many pages seem to be created about topics just because they're in the news and/or just to have a place to put a link to a "neat" blog post: see for example <http://fileformats.archiveteam.org/wiki/Facebook#Links>.
Last but not least, the whole site is rather ugly, and the logo is awfully non-descriptive of what it's supposed to contain; what am I supposed to do with this thumb, stick it up my arse?
It's a shame, really, because documenting file formats is a hard and valuable endeavour. But I don't think these people are going to do a good job of it.
g1n016399 | 10 years ago | on: Glowforge launches consumer-grade laser cutter
g1n016399 | 10 years ago | on: Ad Blocking Irony