Not a single one of those explain the endorsement in OP of the completely-new "highly bizarre raccoon army conspiracy theory"
4,075 karma · joined October 26, 2011
However, the chart settings were actually modified to hide/deemphasize the earlier decline: the the index date was changed. 2025-02-20=100 in their graph, default of 2020-02-01=100 would have the chart start at 64 and rise to 71.44.
In light of recent developments, I thought it would be interesting to ask again.
The second reference -- https://www.hrsa.gov/hansens-disease -- shows cases in the entire US bouncing from around 160 to 220 since _2011_ up through 2020: "Most (95%) of the human population is not susceptible to infection... Treatment with standard antibiotic drugs is very effective." The Florida dashboard which is the third reference shows 14 cases in that state total in 2021.
Also, what is this about judges starting the amendment process?
The mean in the very first row is 102.9 cm (the 40.5 inches in the OP), while the 50th percentile is actually lower at 101.8 (39.7 inches).
"States and territories by customers out Maine 110,693 New York 38,041 Virginia 19,038 New Hampshire 18,056 Pennsylvania 13,040"
* 2022 French Presidential Election Markets (I haven't looked at these too closely that maybe there's a reason they're still listed as "current" on the IEM site, but wasn't this election back in April?)
* 2022 U.S. Congressional Control Markets (3 Markets: Senate, House, and Overall)
If you're trying to use prediction market prices as a gauge of the state of the world, IEM is missing dozens of countries, does not give visibility into US state-level elections, and does not include the result of primaries or political events besides elections that nonetheless impact elections. The 2024 US Presidential election is not even on the radar yet there.
Credit where credit is due for the trailblazing, they're worth a look when they do have a market on an event going, and it's notable for being sort-of a proof of concept for prediction markets. But while IEM may now be the best fit within a particular niche in light of what's happened to PredictIt, it's not in the same league.
"Once sales start dying and a minimum time has passed, I will release the game source code as some kind of open source. I'm not very happy with the draconian nature of (L)GPL, nor do I believe the other licenses have much merit other than to boost the egos of the original authors, so I might just possibly release it all as public domain."
https://web.archive.org/web/20120614004339/http://www.minecr...
https://www.imdb.com/list/ls026560159/
By comparison, entries for the 2010s include MCU franchise films, Star Wars Sequels, Jurassic World (a sequel), The Lion King (Remake), etc:
https://www.imdb.com/list/ls026040906/
Going year-by-year doesn't really change things very much: https://en.wikipedia.org/wiki/List_of_highest-grossing_films...
It's interesting that this downside wasn't even on the radar of this article in 2011, and indeed no serious consideration of possible downsides was presented at all, just a snide dismissal that "anyone who has tangled with the anti-fluoride campaign will realise that lithium lobbyists will have a long, hard road to travel."
The recurrence system is listed as an "advanced topic" in the documentation. I gave up on trying to make heads or tails of recurrence in TimeWarrior after fighting with it for years and having way too many times where I had meant to make a change to just a particular single task, and then having unexpected changes to several tasks in a series, or to the template task, or having just that particular instance changed but then the recurrence ends up creating new tasks in a funny way, etc. I once had a particular edit to a reoccurring task create hundreds of instances the next time I looked at the task list.
Continuing on with recurring tasks, The Taskwarrior documentation notes "you never directly interact with... the template task. It is hidden for a reason. Instead, you interact with the recurring task instances" Hope you don't want make a change to future instances without changing any current instances. You can do it, but it's unnecessarily cumbersome.
Ultimately, I've actually found it easier to run a script outside of TW on an hourly basis that checks for the last completed task with a particular user defined field for each task that I want to recur, then creates a new instance if needed. This works nicely as there's no longer any linkage within TW between individual tasks in a "series", preventing a change from copying from from one to the others, and it's impossible to accidentally make a change to the "template" since the template is no longer a record within TW at all. I do note that the facts that there are python (and other) libraries that make this trivial and that it's possible to define fields on a task this way are notable strengths of TaskWarrior. Nonetheless, the fantastic CLI ergonomics for one-time tasks are just missing for things that happen more than once. That a template for a task is itself a task record seems like some really bad conceptual confusion in the design, and extremely kludgy.
A quick look at sibling comments or a general web search for discussion about TaskWarrior recurrence issues will show problems with recurrence are not uncommon.
The units used for the length of time in the urgency calculation for things like task age, due date are unintuitive and there is no explanation of this rather important point in the documentation (https://taskwarrior.org/docs/urgency.html for reference). As a specific example, I have a task entered 5 weeks ago which task info tells me is an age of 0.107, while a task entered 23 hours ago has an age of 0.003. This kind-of looks like 1 per year, but why? Also, time to due date is definitely not 1 per year. It also looks like age has a ceiling of 1 since this value appears for very old tasks, and that time to due date is similarly limited, but again, not documented.
The built-in reports are kind of nice, and the fact that you can define your own "reports" (really task lists with custom columns) is also nice, but it'd be even better to be able to be able to just throw SQL directly at it. There's a TaskWarrior-inspired utility "Tasklite" that does just this by storing tasks in SQLite, although I haven't tried it myself yet. The Tasklite criticism of TaskWarrior is also worth considering: https://tasklite.org/differences_taskwarrior.html
You can get tasks out of Taskwarrior in JSON format with "task export" and there are scripts to further transform this into other formats, but you need to do an extra step to import this into another tool for any analysis you might want to do.
Reports like ghistory.daily and ghistory.weekly can get long and unwieldy. There are ways to deal with this, but it's annoying, and makes me question if the developers themselves are using these reports on a list of completed tasks going back several years or not.
Taskserver is another area that seems poorly thought-out and over-engineered, similar to recurrence, and I'd caution anyone considering using Taskwarrior on more than one computer to look over the Taskserver Setup guide at https://gothenburgbitfactory.github.io/taskserver-setup/ while noting the following:
* Just copying the files around between Taskwarrior instances e.g. with Syncthing or something like that mostly works, but a lot of tools/attempts at mobile apps for TaskWarrior rely on having TaskServer. The sync issues noted in various places by using a file-level sync like this are definitely possible, but the practical implication for a task list that most likely belongs to a single individual is questionable.
* Per the guide, "There are two 'D's in TASKDDATA, and omitting one is a common mistake" in reference to an environmental variable defined, as far as I can tell, entirely within this document. Naming things is hard and this is admittedly a small detail, but why not remove the pitfall rather than just warning about it?
* You will need a CA certificate to "to sign and verify the other certs" -- "The command below will generate all the certs and keys for the server, but this uses self-signed certificates, and this is not recommended for production use. This is for personal use, and this may be acceptable for you, but if not, you will need to purchase a proper certificate and key, backed by a certificate authority."
* "Certificates coming from Let's encrypt have not been successfully used by anyone. Please remember that Let's encrypt only generates servers, but we need a client certificate as well."
* This is rather a lot of work just to be able to _add tasks on your phone_ while you're away from your desk or even just to sync tasks between what might be two or three desktops, and it's pretty clear they had more of an "enterprise environment" or a hosting service like InThe.AM in mind when they wrote it. Regarding that particular service, it is open-source but "Setting this up locally as a clone of Inthe.AM is, unfortunately, not supported" - https://intheam.readthedocs.io/en/latest/
By contrast, there's another project dstack which is also Taskwarrior-inspired but "uses git to synchronize instead of a special protocol" at https://github.com/naggie/dstask -- this is also something I haven't tried it myself yet but it looks interesting, although doesn't itself help with getting tasks on/off a phone as far as I know.
The labeling on the horizontal axis on the chart is terrible, but roughly this is a change from 20% to 95% in about 2 or 3 hours. It doesn't look like they ever had it at less than 15% (again, give or take a few points due to bad infographic-esque picture).
"The main reason I don't like this theory is kind of an efficient-markets reason: there are literally billions of men who are concerned about hair loss. The most popular preventative treatment for hair loss carries the risk of nasty side effects, like depression or erectile disfunction. If we could prevent hair loss and even regrow hair by breaking the causal chain "upstream" of hormones, why isn't this totally common knowledge? Why aren't anti-hair-loss subreddits like /r/tressless constantly advocating for botox injections as a supplement or replacement for hormonal treatments?"
"Retirement End Year - Time to get real grim here… this is when you’re expecting to not need your retirement fund anymore. Put in a different way, it is when you expect to die. There are a number of factors that play into this, but I would suggest looking at the Social Security Administrations chart here. As of the date that I wrote this post, I am a 39 year old female, and that chart tells me that on average I can expect to live 43.41 more years. So, I personally would set the Retirement End Year to 2072 (2021 + 43.41 = 2062.41 + 10 years of padding just to be sure)." -- https://www.cfiresim.com/tutorials/