/me cringes in fear of a left-pad moment -- what distros can't be built now? Only half joking. ;)
With openSUSE, we store a copy of the source code in our own repos in OBS[1]. And all users can download the source RPMs.
Libtiff goes offline
61–70 of 121 posts
Re: Libtiff goes offline
#62Earlier quoted context omitted.
Which is why a DVCS is important, the history goes with every copy.
A history goes with every copy. You still need a protocol for determining the history.
If you have a maintainer who signs their commits, you trust their signatures and call it a day. Go with the latest commit and that tells you the history that they have cryptographically claimed is "correct".
Re: Libtiff goes offline
#63Thankful for libtiff's role in the PSP exploit community many years ago. :)
also one of the original iPhone 1 jailbreaks
To my knowledge this was the original iPhone jailbreak (JailbreakMe). I was on IRC whilst the author was seeking donations before releasing it ;) Ran it on my trusty iPod Touch 1g only minutes after it was released.
This was for iOS 1.1 though, not iOS 1.0, as it was not encrypted and was never really locked down. It was Apple's choice to release iOS 1.0 without the security enabled that made further jailbreaking efforts much more straight-forward, because there was extensive knowledge of the file system.
This was all well before there was an App Store, and when Apple's public position was that they'd never allow third-party software on their platform ;)
Re: Libtiff goes offline
#64Earlier quoted context omitted.
Tiff is very useful because it lets you do almost anything. A tiff image is just several arrays of numbers, you decide how many bits, signed, unsigned, float, int, etc. This is very helpful for processing which treats each pixel as a sample of the scene, such as computational microscopy or remote sensing. I've always wondered if that had something to do with why it was hosted at remotesensing.org.
See my edit. Also, when you are doing image processing, operating in scanlines is usually the least performant way of doing things, hence whey we have texture compression formats (even lossless ones) which do block encodings. TIFF has no reason for existing in my opinion.
TIFF supports many useful features for processing very large images. Tiled compression, storing channels in contiguous hyperplanes or on a single image plane, multiple levels of detail, custom compression codecs (lossless or lossy), sparse images, arbitrary bit widths, and permits storing arbitrary metadata with the data.
Viewers of libtiff often treat it like PNG/JPEG, but good Tiff viewers can leverage this functionality. Typically few batteries are included.
Tiff is kind of a cross breed between structured portable formats (HDF5/NetCDF) and imagery.
Re: Libtiff goes offline
#65Earlier quoted context omitted.
GitHub will rot some day as well. (I think we're already seeing it start to decline.) This is simply a permanent problem. Archive.org and to a lesser extent IPFS are viable solutions for archiving, but _contingency_ plans are I think the missing component here. Pray for the best but prepare for the worst.
You know, come to think of it, Archive.org is sorta kinda the right place to store these things. If they offered source code control they would both get the source as well as the path to the latest version all at once, which could be an invaluable historic record.
A git HTTP archive can be crawled and archived in principle. They might well be doing this already with github and elsewhere just through the normal course of their operation.
Re: Libtiff goes offline
#66Earlier quoted context omitted.
A potentially brilliant idea. I wish I had a clue how to follow up on it. Perhaps someone else here might!
The Internet Archive would be the perfect group of folks to archive code.
Indeed. Updates in Github (which can create a webhook) should trigger an archive operation.
It has been on my list to integrate https://github.com/joeyh/github-backup with https://github.com/ArchiveTeam/ArchiveBot.
Re: Libtiff goes offline
#67Re: Libtiff goes offline
#68Seems like we've had organizations that house ideas for the public good for centuries now. Why not involve libraries in the effort? They could keep a "master" copy and github.com, gitlab.org, SF.com, or whoever else comes next can host development versions.
Re: Libtiff goes offline
#69Earlier quoted context omitted.
You know, come to think of it, Archive.org is sorta kinda the right place to store these things. If they offered source code control they would both get the source as well as the path to the latest version all at once, which could be an invaluable historic record.
A git HTTP archive can be crawled and archived in principle. They might well be doing this already with github and elsewhere just through the normal course of their operation.
Re: Libtiff goes offline
#70For important projects like this (libjpeg, libpng and others) it would make sense if there was sort of place to get all of them apart from mirrors. What am I saying, that place[0] exists. Developers shouldn't have to shoulder the burden of hosting their code if they don't want to or don't wish to weather the expense. It certainly seems in this case they couldn't pay for self-hosting (or friend-hosting or whatever thi…
> What am I saying, that place[0] exists One day, this will have only existed. Until then, they should host the repository on Google Code.
Google Code is dead.