In this context of a conspiracy to control the media as a stepping-stone to control political systems, the word "elites" is a dogwhistle to deniably say "jews".
https://en.wikipedia.org/wiki/Antisemitic_trope#:~:text=one%...
3,967 karma · joined April 8, 2008
In this context of a conspiracy to control the media as a stepping-stone to control political systems, the word "elites" is a dogwhistle to deniably say "jews".
https://en.wikipedia.org/wiki/Antisemitic_trope#:~:text=one%...
The outlet's snarky responses to reader letters are also available: https://www.theregister.com/2007/01/09/apple_iphone_letters/
http://marionrecord.com/dispatch/police_raid_newspaper_offic...
Previously she had accused the newspaper of obtaining the information illegally.
http://marionrecord.com/dispatch/restaurateur_accuses_paper_...
There's also a headline from their last week's issue, "Media ejected from open forum" that seems likely to be related. Google's cache of the article is at: https://webcache.googleusercontent.com/search?q=cache:http%3... so I'll give a relevant quote for when that expires:
> Two representatives of the news media were ordered by Marion police chief Gideon Cody to leave a public reception Tuesday for U.S. Rep. Jake LaTurner.
> Cody’s directions came at the behest of Kari Newell, proprietor of Chef’s Plate in Marion’s Historic Elgin Hotel and its coffee shop across the street, Kari’s Kitchen, where the event was taking place.
> Cody said that Newell asked that Record publisher Eric Meyer and Record reporter Phyllis Zorn be evicted before LaTurner arrived.
> Moments before Cody ordered Meyer and Zorn to leave, Newell had told Zorn: “I will not have members of the media in my establishment. You have to leave.”
Tarsnap is technically impressive and was reliable software, but the billing system requires an unpredictable manual process requiring two credentials held separately in most orgs. Colin has told me in private email that customer deletion is a manual step not taken lightly, but I didn’t feel that one unscheduled manual process was fixed by epicycling on another one.
I migrated away several prod installs to pay more for predictable and automated billing. Even with usage billing that’s not easy to predict, the date of next intervention is printed on the back of the credit card. (Though really, it does cost less - the engineer time it takes to manually add funds costs significantly more than a picodollar.)
Lobsters has had serious problems with users who try to exploit the site for self-promotion, and it's more serious for us than HN when a few votes is enough to move something to our homepage. As part of addressing it, we have a bright-line rule prohibiting new users from submitting stories from new, unseen domains in their first 70 days on the site.
Five hours after jart invited woodrush, at 2022-01-12 02:26, they tried to violate the rule and got this error message:
> woodrush.github.io is an unseen domain from a new user. We restrict this to discourage self-promotion and give you time to learn about topicality. Skirting this with a URL shortener or tweet or something will probably earn a ban.
At 2022-01-12 02:40, jart submitted the exact same link to break the restriction, and woodrush submitted several posts from that domain. After that, jart started submitting stories from all of her invitees to circumvent this rule, which anyone can verify by comparing timestamps on her submitted stories at https://lobste.rs/newest/jart to creation dates for her invitees at https://lobste.rs/u#jart.
On top of repeatedly breaking a rule that has a big red background and explicitly warns of a ban, two of jart's invitees were manually warned and banned for other inappropriate self-promotion. Finally, when another of her invitees started obvious sockpuppeting, I looked at the invite tree, saw this pattern of abuse, and cleaned up after it.
To rebut another claim repeated a couple times elsewhere in the comment tree, all banned users get an email notifying them of a ban with the Reply-To header set to my email: https://github.com/lobsters/lobsters/blob/master/app/mailers... None of the users banned in this action have clicked reply to explain how I've made a mistake enforcing an unambiguous rule of ours.
> In the Northern Hemisphere, the switch to daylight savings time in March results in most people losing an hour of sleep opportunity. Should you tabulate millions of daily hospital records, as researchers have done, you discover that this seemingly trivial sleep reduction comes with a frightening spike in heart attacks the following day. Impressively, it works both ways. In the autumn within the Northern Hemisphere, when the clocks move forward and we gain an hour of sleep opportunity time, rates of heart attacks plummet the day after.
I don't see a specific study cited, but my ebook copy doesn't seem to have all the footnotes.
I pulled up the article you linked on sci-hub: https://sci-hub.se/https://pubmed.ncbi.nlm.nih.gov/18971502/ The only use of the number "24" refers to hours in the day, and its summary doesn't seem to match your claim:
> The incidence of acute myocardial infarction was significantly increased for the first 3 week-days after the transition to daylight saving time in the spring (Fig. 1A). The incidence ratio for the first week after the spring shift, calculated as the incidence for all 7 days divided by the mean of the weekly incidences 2 weeks before and 2 weeks after, was 1.051 (95% confidence interval [CI], 1.032 to 1.071). In contrast, after the transition out of daylight saving time in the autumn, only the first weekday was affected significantly (Fig. 1B); the incidence ratio for the whole week was 0.985 (95% CI, 0.969 to 1.002
It's not a CLI reference. Slashdot was named for how it sounds read aloud: https://slashdot.org/faq/slashmeta.shtml
> "Slashdot" is an intentionally obnoxious URL. When Rob registered the domain http://slashdot.org, he wanted a URL that was confusing when read aloud. (Try it!)
If you don't read much exercise science, it's worth noting the paper says "It is important to note that volunteers in Experiment I (Table S1) were typically sedentary (verified with an objective tracking device), and none of them had a high aerobic cardiorespiratory fitness (determined by treadmill VO2max or the maximal oxygen consumption test)." A common pitfall of exercise science is that almost anything works wonderfully on untrained sedentary subjects. Wait for replication.
> Because if you accept your fate joyfully, as a Stoic sage should, you’ll never try to change it.
This is a common criticism. To pick one of many convenient rebuttals, here's William Irvine's book A Guide to the Good Life: The Ancient Art of Stoic Joy, chapter 5:
> To the contrary, they were fully engaged in daily life. From this, one of two conclusions follows: Either the Stoics were hypocrites who did not act in accordance with their principles, or we have, in the above argument, somehow misinterpreted Stoic principles. I shall now argue for this second alternative.
> Remember that among the things over which we have complete control are the goals we set for ourselves. I think that when a Stoic concerns himself with things over which he has some but not complete control, such as winning a tennis match, he will be very careful about the goals he sets for himself. In particular, he will be careful to set internal rather than external goals. Thus, his goal in playing tennis will not be to win a match (something external, over which he has only partial control) but to play to the best of his ability in the match (something internal, over which he has complete control). By choosing this goal, he will spare himself frustration or disappointment should he lose the match: Since it was not his goal to win the match, he will not have failed to attain his goal, as long as he played his best. His tranquility will not be disrupted.
(And: if you think this archive may be inauthentic, perhaps you should've chosen another for your evidence.)
It doesn't? The archive he links to includes a copy of the whitepaper, but this repo is one archivist's collection of files, not an official distribution. The whitepaper is not in the nov08 distribution or the bitcoin-0.1.0.tgz, and the document doesn't include a license statement. I'd believe it's MIT licensed, but this post doesn't establish that fact or sound like he presented more compelling support of the idea to Amazon.
As a practical matter, it's vanishingly unlikely that Satoshi Nakamoto is going to file suit. But as a legal matter, he hasn't shown that the whitepaper was released under a license permitting redistribution or that he has permission from the author. Amazon gave him several options and opportunities, then declined to participate in apparent copyright infringement.
Amazon has a huge problem with people republishing others' books via KDP and their marketplace, even getting fake versions added to or replacing authentic listings. This process seems like it might be a pretty good way of addressing that. The inconvenience comes from not wanting to give the well-practiced scammers a guide to defeating the process, which is a common tradeoff.
You're also welcome to use the Lobsters code: https://github.com/lobsters/lobsters