it is necessary to tag rapidly-debasing currencies with a date when using as a unit of account

 It makes no sense to talk about (for example) EUR from one year and EUR from another year, as though these units are the same.  A 2005 EUR is a much more valuable item than a 2021 EUR, because the currency is continually debased.  The same for USD, GBP and so on.  The fiats operate as short-term liquidity only, not as a unit of account across time.  Therefore, they should not be used as a unit of account across time.

If you bought a house for 300k 2005-USD and sold it for 600k 2020-USD, and USD has been reducing in value by 5% a year, you made a loss (and you may have to pay tax on the fake gain).  A 2020-USD is worth less than half a 2005-USD because of debasement.

For these second-tier fiat currencies, a granularity of one year has recently been more or less adequate.  Debasement ran at roughly 5-7%, with official debasement ("inflation") stats around 1%.  As debasement accelerates, it may be necessary to include the month as well as the year in the unit name, at which point some kind of collapse is imminent.

Comments

Post a Comment

Popular posts from this blog

the persistent idiocy of "privileged ports" on Unix

TCP and UDP have ports.  These are 16 bit; there are 65535 or so per IP address. These protocols don't care to differentiate between the ports.  Elsewhere, IANA presumes to operate a process to allocate "well-known" ports in the range 1-1023, "registered ports" in the range 1024-49151, and to reserve the remainder, 49152–65535, for "ephemeral" ports.  The caller end has to have a port, which is how replies get back within the virtual connection, and these are conventionally picked from the ephemeral range by the OS's networking stack. The whole idea of ports is ridiculous, because it allows ISPs to arse around presuming to decide which services they will "not allow".  Anything that allows IPSs to do anything other than shift opaque packets will allow ISPs to meddle and break things, and due to the Law of Meddling, if they can, they will.  I am currently working around an issue with Claro, a pretend ISP, blocking port 5060, allocated to SI...
Read more

JT "their my" nonsense

Image
Another example of the "your my" nonsense produced by corporations calling customers' things "my" things. Let's mark this for pronouns: In total, I've identified 12 correct pronouns, 6 incorrect pronouns, given from the wrong perspective, and one direct clash between a correct one and an incorrect one, in the form of "their my JT account".  This should be a dead giveaway that something is wrong. As well, observe this perfunctory, bossy, yet passive tone that they take.  "all customers are required" to such and such.  Let's try this.  "All telecoms providers are required to provide ipv6 service".  Oh, that didn't work.  "All entities are required to desist from calling other entities' things 'my'".  Oh, that didn't work either. This is the real pronoun crisis.
Read more

easyjet: repeated entry of information they already have

Image
As I observed earlier today, airline web sites are obsessed with making people re-enter information, apparently arbitrarily. The following seems to be required for Easyjet, for an "existing" customer relationship, every time: country of residence selected from big list, involving skidding around on the screen that makes the victim feel sick should be remembered. If it has to be changed, should be type-and-choose victim is taunted with the text "tell us about you", when they thought they had logged in form with the following on one page: business / leisure title, first name, last name, age there is a button to "copy from contact details", but this doesn't do the "age" field.  Since they have my date of birth, they are of course able to calculate my age.  As well, the only values for this field are "18+", "17", or "16".  Is it a deliberate decision, to not fill this field based on the customer data, and to make the...
Read more