Link to Original Source
Slashdot videos: Now with more Slashdot!
Link to Original Source
I am a photographer myself, this is what I do: I store all my photos (both RAW+JPEG) in a Subversion repository (I guess Git could be used as well, however, I started doing this way back, before Git existed). I have a workstation on which I do post-processing of my photos. The photos I work with are in a Subversion Working Copy. I "commit" the photos to the Subversion Repository which runs on a small server with some external USB 3 harddrives on my local network. I also have a two spare external hard drives that I periodically copy the Subversion Repository onto. One of these drives is always stored at my parents' place. My parents live a few hundred miles away. Every time I visit them, I bring the other extra hard drive with me and switch it for the one at my parents. This way, I always have an off-site backup at my parents'.
My workflow is this:
This gives me several advantages:
- Automatic versioning of photos. I can edit a picture and save it and if I weeks later regret my editing, I can always restore it back to the original. Without me having to manually manage multiple copies of the same picture.
- A guarantee that nothing will ever be deleted -- even if I delete something and commit, I can get it back by checking out a previous revision without having to resort to backup
- A multi-level backup strategy: Files exist in the working copy on my workstation, in the Subversion Repository, and in the backup. It is extremely easy to get files back from the first level "backup" (the repository).
- I can easily check out (a portion of) my photos everywhere if I want to via Subversion.
I notice the following disadvantages:
- Performance: Subversion is not particularly fast on large binary files. This is not a problem on modern hardware though. My current Subversion server is an Intel Atom and it handles it nicely while at the same time doing SSL encryption + LUKS encryption. My old server had a very small AMD Geode embedded CPU that did have hardware support for AES, but choked on the Subversion. This, however, was an extremely slow CPU. Most modern, low-end smart phones will run circles around it.
- Disk usage: Subversions working copy format is not very space efficient. The working copy will use about 2x the actual size of the photos. In practice, this is easily solved though by having a working copy by year. So that you would normally only keep 2012 and maybe 2011 folders in your working copy. When you need to work on older photos, checkout the relevant part in a new working copy. Another option is to use a non-standard working-copy format. I forgot the name, but there is a working copy format that allows for 1x disk usage. This means the your working copy will not take up more space than the original files. Only if you change a file locally, it will take up more space.
2.50 for a movie?
40,000 dollars per year / 0.02 dollars per song = 2,000,000 songs / year
This is misleading. A musician does not live off of just selling *one* song multiple times. The musicians today primarily live off of concerts. Also, as the parent to your reply said: think of this as promotion. Selling a copy of a song for 0.02 will increase chances of the listener going to (and paying for) a concert.
And every OS should be installable directly into the motherboard SSD chip. It should be as fast as the motherboard allows. 60GB of SSD cache ought to be enough to install any OS.
Problem is what to do if the SSD breaks? You have to replace your motherboard as well. Also, if some component on your motherboard breaks, you risk losing your data on SSD.
Really, it's so great that you believe things. I'm glad you have belief. Back in the real world, facts matter, not belief. What percentage of authorized tappings were abused? (Note we are not talking about warrantless wiretapping, which is bad, but not the topic here).
The problem is, there is no way of knowing what percentage of authorized tappings that were abused. I have no way of checking whether I have been legally (or illegally) tapped. Much less if such tapping was abused.
For me the ultimate file manager in KDE is Krusader. Give it a go if you like two-pane approaches.
Thanks for the tip. Just tried Krusader. It is really nice.
It might be stolen property.
So might dollars? I do not see your point.
The slashdot crowd of course is going to lambast this decision. But if you take time to think about it rather than reply with a knee-jerk reaction, it really isn't that unreasonable.
Yes, it really is unreasonable.
What is required to host thousands of emails online? - A web server. Presumably they have one of these, but is it just a simple website at some hosting company and not very easy to configure or mass-upload to, and perhaps with a limited storage quota? Is it their same server they had in the late 90's that might choke on 24,000 files in one directory?
Put it in a zip-file or tarball. As for bandwidth, you make it available via bittorrent.
- How do you convert the emails to individual files which can be hosted? Convert to PDF perhaps? File -> Save As? Either way, it is going to be very labor intensive. Perhaps the email system is old enough that it is even more difficult and time consuming?
How do you print them? You automate the process. If you can print the to a printer, you can print them to a PDF printer. Same amount of work.
- How long do you have to store the online files? Every day they store the files on the server costs them extra $. And every person who downloads the files costs them extra $.
How long do you store the paper versions? As for bandwidth, se above.
- What type of technical knowledge is required to put all of the pieces together? To a slashdotter it might seem trivial, but a town of 30,000 reachable only by water and air is not the type of place who will employ public servants with the technical expertise of a slashdotter. Their IT staff might consist of a guy who knows how to replace a monitor and reformat Windows XP. They may outsource all of the rest of their IT functions at an hourly cost to the state. All of these email requests are probably going to some poor secretary who has a hard time opening her own email.
I would assume the IT guy is capcabable of taking backups. What would he do, if an user comes to him and says she need him to recover all her e-mails from backup. He would extract the e-mail (in maildir format or some other storage format) from the backup archives. Now, he should just do the same. Instead of putting the backup back on the server, he should just tar or zip it and put in online via torrent.
- Who should have access? IANAL, but this is a foia request so I presume anybody in America, but is Alaska required to make government documents readily available to the governments of North Korea and Iran? If not, who is going to setup the security to prevent unauthorized access?
If everyone in USA has access to the docs, then there is not much difference if the rest of the world has access. If every US citizen has a copy, it would be trivial for any foreign person to obtain a copy as well.
Remember, this is a foia request which Alaska has to respond to, but they have no incentive to make it easy at their own taxpayer's expense. It is far cheaper and easier for a small town government office to tell people to come and get the information than it is for them to make it easily accessible over the internet.
Yes, and as I has explained above, the chosen method of printing the e-mails is hardly cheaper or easier. It is a blatant attempt to make it more difficult to obtain a copy.
"What happened here was the gradual habituation of the people, little by little, to being governed by surprise; to receiving decisions deliberated in secret; to believing that the situation was so complicated that the government had to act on information which the people could not understand, or so dangerous that, even if the people could not understand it, it could not be released because of national security. And their sense of identification with Hitler, their trust in him, made it easier to widen this gap and reassured those who would otherwise have worried about it.
"This separation of government from people, this widening of the gap, took place so gradually and so insensibly, each step disguised (perhaps not even intentionally) as a temporary emergency measure or associated with true patriotic allegiance or with real social purposes. And all the crises and reforms (real reforms, too) so occupied the people that they did not see the slow motion underneath, of the whole process of government growing remoter and remoter.
From "They Thought They Were Free -- The Germans 1933-45": http://www.press.uchicago.edu/Misc/Chicago/511928.html