You should read up on the Bitcoin protocol/architecture. "Mining" isn't arbitrary, it's how the system verifies transactions and prevents double spending - you need mining for the whole system to work.
The fact that new coins can be gain from mining is not arbitrary either: first, it encourages people to mine, and therefore strengthens the network. Second, a big part of the Bitcoin appeal is that nobody can just inflate away the value of the coins one owns.
You may disagree with it, but it's definitively not arbitrary.
Go is fine for writing daemons. It's not particularly good for writing interactive processes. For once, Mozilla wants to be able to do away with the GC for certain components of the system.
They're orthogonal; IMAP is just a protocol, not a storing mechanism. You can just add an MBOX mailbox to the IMAP server's configuration if you have one.
I'm not depending on any specific program, I'm just giving the easiest way of doing it. Manually transforming the filenames is easy anyway, and even that is only important under the assumption that I'm working with a broken filesystem.
The file names aren't cross system compatible in the first place - changing them won't automatically make Maildir software work with the new file names.
If the Maildir software is running on a system which doesn't support colons, it necessarily has to support some colon-less format. If the Maildir software is running on a system that supports colons, why the hell wouldn't I extract the files there?
No; Google's data mining algorithms will have a permanent searchable archive. You'll just have a temporary archive, until they decide to retire the service or ban you for some offense perceived by their automated "police".
But why would I waste time manually finding and copying individual emails, when I can just let the backup script archive them all for virtually no cost?
How large can a personal email archive really be? Even if you're storing the equivalent of a copy of War and Peace per day, for ten years, that's just a couple dozen gigabytes. Nowadays, it's hardly any trouble archiving that.
Directories or folders may seem primitive, but they're not necessarily going to stick around.
Abstracting the underlying storage (which differs anyway between systems), a directory is just a set of files. They'll exist for as long as files themselves exist, even if they have different names, and they'll certainly be here long after the SMTP headers (used by both Maildir and mbox) is long dead and buried.
I agree with that for new emails, but for an archive file, none of it really applies. File system corruption and fat fingers should be handled by just restoring from backup, and merging / marking as read / etc is not really applicable for old mail, which should be accessed by either viewing it readonly or making a disposable copy.
mbox might have its problems, but I don't think there's any good reason to spend time converting old files to Maildir.
I'm afraid the practices aren't the same at all. Here I can never draw money from people's accounts just by promising I have their permission. I need those persons to tell the bank, "yes, icebraining can take money from my account" by using some special codes I generate and give them.
The entity that is to be paid gives me two codes (Entity and Authorization). I can either go to an ATM or login to my bank's website and set up the direct debit authorization using those codes.
The difference is that I, the payer, need to directly authorize the payment with the bank.
Frankly, payee issued direct debits and credit cards are stuff that just baffle me in the brokenness of their design. That taking money from people's account (even if they can report it and not be liable) uses a much less secure system than one design to let apps post Tweets on behalf of users (OAuth) is insane to me.
"Now, of course, Reader and Keep aren't that critical of a service" "A somewhat contrived analogy would be"
I think it's asinine when applied to Google Wallet as well, and calling it a contrived analogy is an understatement. You're free to disagree.
If I were to run a service, I would probably feel a moral obligation to keep it running, much like I did in the past feel an obligation to keep my open source extensions up to date and available.
So you agree with me
No, because you're judging others, while I don't feel I have the right to do that in this case. I would feel a moral obligation to do so, but that doesn't mean I think Google (or anyone else) does.
So you're a kid who gets angry if someone tells you you should do something.
No, it depends on what, who said it and for what reasons. And I wouldn't really feel angry, but I would feel some schadenfreude after cutting them off.
Let me tell you, in society, society expects all sorts of things from you, some reasonable, some unreasonable, and if you're going to get angry every time someone tells you you should do something, you're going to have a lot of problems.
Considering I've been criticized for not getting angry enough, I don't think I'll have such a problem. But hey, thanks for the psychological lesson derived from reading 122 words. Unfortunately, I lack such skills and can't assess your personality even though I've already read two full posts.
In your analogy there's a moral obligation because people would fucking die otherwise. To compare this with using another RSS reader (even if somehow worse) is asinine.
If I were to run a service, I would probably feel a moral obligation to keep it running, much like I did in the past feel an obligation to keep my open source extensions up to date and available.
But if some entitled fuck had come and whined that I had that moral obligation, I'd cut him off immediately. There's stuff that may be morally imperative to one own conscience, but that no one else has any right to demand, and this is one of them.
Don't like it? Get a service with a contract/agreement.
Regarding 1), Google has full access to the Reader accounts. This isn't desktop software, they know full well who and how much people use it. The "fuss" is nothing but a storm in our little bubble of technologists. There's a whole world that uses Google products and doesn't even know Reader exists.
Slashdot Mirror
You should read up on the Bitcoin protocol/architecture. "Mining" isn't arbitrary, it's how the system verifies transactions and prevents double spending - you need mining for the whole system to work.
The fact that new coins can be gain from mining is not arbitrary either: first, it encourages people to mine, and therefore strengthens the network. Second, a big part of the Bitcoin appeal is that nobody can just inflate away the value of the coins one owns.
You may disagree with it, but it's definitively not arbitrary.
The Google founders still control the majority of the votes (because they have special, private stock which gives ten votes per share).
Both positions are defended by libertarians. Claiming that libertarians only have one position is a clear no-true-scotsman fallacy.
https://en.wikipedia.org/wiki/Libertarian_perspectives_on_abortion
Go is fine for writing daemons. It's not particularly good for writing interactive processes. For once, Mozilla wants to be able to do away with the GC for certain components of the system.
I like Go, but it wouldn't have worked for this purpose. They want to be able to do manual memory management, for example.
No, it's not because it's a common word, it's because it describes the product, or in this case a main part of it, its GUI.
And Windows is still trademarked, the court just "raised questions" over its validity, but it was never struck down.
They're orthogonal concepts. Most atheists are agnostic.
They're orthogonal; IMAP is just a protocol, not a storing mechanism. You can just add an MBOX mailbox to the IMAP server's configuration if you have one.
I'm not depending on any specific program, I'm just giving the easiest way of doing it. Manually transforming the filenames is easy anyway, and even that is only important under the assumption that I'm working with a broken filesystem.
The file names aren't cross system compatible in the first place - changing them won't automatically make Maildir software work with the new file names.
If the Maildir software is running on a system which doesn't support colons, it necessarily has to support some colon-less format. If the Maildir software is running on a system that supports colons, why the hell wouldn't I extract the files there?
Having the same design flaw is good, it means it's easier to avoid and fix it. Random errors are much harder to prevent.
man tar
--transform, --xform EXPRESSION
use sed replace EXPRESSION to transform file names
No; Google's data mining algorithms will have a permanent searchable archive. You'll just have a temporary archive, until they decide to retire the service or ban you for some offense perceived by their automated "police".
But why would I waste time manually finding and copying individual emails, when I can just let the backup script archive them all for virtually no cost?
Better hope the algorithmic overlords don't decide you're a spammer and lock you out. Remember not to keep your eggs in a single basket.
How large can a personal email archive really be? Even if you're storing the equivalent of a copy of War and Peace per day, for ten years, that's just a couple dozen gigabytes. Nowadays, it's hardly any trouble archiving that.
If you want a single file, you can just use tar.
Directories or folders may seem primitive, but they're not necessarily going to stick around.
Abstracting the underlying storage (which differs anyway between systems), a directory is just a set of files. They'll exist for as long as files themselves exist, even if they have different names, and they'll certainly be here long after the SMTP headers (used by both Maildir and mbox) is long dead and buried.
GMail doesn't even use maildir.
They don't use mbox either.
I agree with that for new emails, but for an archive file, none of it really applies. File system corruption and fat fingers should be handled by just restoring from backup, and merging / marking as read / etc is not really applicable for old mail, which should be accessed by either viewing it readonly or making a disposable copy.
mbox might have its problems, but I don't think there's any good reason to spend time converting old files to Maildir.
You can get much of that if you add LVM to ext4, though.
I'm afraid the practices aren't the same at all. Here I can never draw money from people's accounts just by promising I have their permission. I need those persons to tell the bank, "yes, icebraining can take money from my account" by using some special codes I generate and give them.
How is the authorisation done?
The entity that is to be paid gives me two codes (Entity and Authorization). I can either go to an ATM or login to my bank's website and set up the direct debit authorization using those codes.
The difference is that I, the payer, need to directly authorize the payment with the bank.
Frankly, payee issued direct debits and credit cards are stuff that just baffle me in the brokenness of their design. That taking money from people's account (even if they can report it and not be liable) uses a much less secure system than one design to let apps post Tweets on behalf of users (OAuth) is insane to me.
"Now, of course, Reader and Keep aren't that critical of a service" "A somewhat contrived analogy would be"
I think it's asinine when applied to Google Wallet as well, and calling it a contrived analogy is an understatement. You're free to disagree.
If I were to run a service, I would probably feel a moral obligation to keep it running, much like I did in the past feel an obligation to keep my open source extensions up to date and available.
So you agree with me
No, because you're judging others, while I don't feel I have the right to do that in this case. I would feel a moral obligation to do so, but that doesn't mean I think Google (or anyone else) does.
So you're a kid who gets angry if someone tells you you should do something.
No, it depends on what, who said it and for what reasons. And I wouldn't really feel angry, but I would feel some schadenfreude after cutting them off.
Let me tell you, in society, society expects all sorts of things from you, some reasonable, some unreasonable, and if you're going to get angry every time someone tells you you should do something, you're going to have a lot of problems.
Considering I've been criticized for not getting angry enough, I don't think I'll have such a problem. But hey, thanks for the psychological lesson derived from reading 122 words. Unfortunately, I lack such skills and can't assess your personality even though I've already read two full posts.
In your analogy there's a moral obligation because people would fucking die otherwise. To compare this with using another RSS reader (even if somehow worse) is asinine.
If I were to run a service, I would probably feel a moral obligation to keep it running, much like I did in the past feel an obligation to keep my open source extensions up to date and available.
But if some entitled fuck had come and whined that I had that moral obligation, I'd cut him off immediately. There's stuff that may be morally imperative to one own conscience, but that no one else has any right to demand, and this is one of them.
Don't like it? Get a service with a contract/agreement.
Regarding 1), Google has full access to the Reader accounts. This isn't desktop software, they know full well who and how much people use it. The "fuss" is nothing but a storm in our little bubble of technologists. There's a whole world that uses Google products and doesn't even know Reader exists.
Try setting Search Tools -> All Results to "Verbatim". It doesn't fix all the issues, but it often helps, in my persona experience.
So he can get the retailers to indirectly pay his insurance, or he can "help them" and get nothing, and he should choose nothing?
Sheesh, retailers must be something else where you live, if you have that kind of loyalty to them.