rgrove
I've had varying degrees of success over the years with various monorepo approaches, and have so far been most happy with pnpm workspaces plus TypeScript project references (plus Changesets when it's necessary to manage changelogs for published packages). oneRepo looks like it combines the things I like best about these tools and solves some additional headaches, so I'm looking forward to trying it out.
(I worked on Yahoo Search — and search.yahoo.com — from 2007 to 2010)
While the default SmugMug experience emphasizes publicly sharing your photos via a personalized photo site, you can just set everything to private, leave the website empty, and use the private Photo Library and Organizer features to manage your photos. The Photo Library provides a great UI for browsing and searching on the web (including mobile devices), and the iOS app offers a fast native iOS browsing and searching experience.
Full disclosure: I work for SmugMug!
The 28 million ballots in question aren't "missing"; they're ballots that were mailed to voters and weren't used.
In some cases the voters in question likely didn't bother voting (common in local elections) or simply forgot (I've done this when I accidentally stacked other mail on top of a ballot and then didn't find it again until too late). In other cases, voters may have moved and failed to update their voter registration. This situation isn't unusual or alarming, and the opportunities for fraud aren't nearly as plentiful as the article tries to imply.
The article cites a 2008 report by the CalTech/MIT Voting Technology Project as recommending that states abolish absentee voting due to fraud concerns, but that report contains only a single paragraph proposing a theoretical _potential_ for fraud due to "unsecured" mail channels. It provides no evidence that this is common or has even occurred, and in fact devotes significantly more space to discussing the inconvenience of mail-in punch-card ballots with Styrofoam backings — something I had never heard of despite having voted by mail for almost two decades.
The article also cites a 2008 Reed College study, which again raises theoretical concerns about fraud but offers no substantive evidence that it's an issue, and in fact states that "A report commissioned by the federal Election Assistance Commission, authored by Tova Wang and Jed Seberov, concluded, on the basis of interviews with experts in the area, that there was little evidence of voter fraud."
But these aren't the same thing.
The set "all vehicles in the US" contains both ICE vehicles _and_ hybrid/battery-powered EVs. But Tesla is explicitly only talking about ICE vehicles, and Tesla doesn't specifically indicate whether they're talking only about US ICE vehicles or all ICE vehicles worldwide.
I'm not sure what the source is for Tesla's number, and it's entirely possible it's inaccurate, but The Drive's counter-argument makes an apples vs. oranges comparison.
When you send an email that you don't want to be collapsed into any previous thread on Gmail, include an `X-Entity-Ref-ID` header with a random value.
I don't remember where I learned this. I can't seem to find any official documentation mentioning it. But it works.
The "Start free trial" button on the website literally did nothing. If I clicked it enough times, I eventually got a poorly worded error asking me to try again in 24 hours. This happened in multiple browsers. I tried many times over the course of several days with no success. I had coworkers try in case it was something specific to my machine or network. They got the same error.
I opened a support request and asked if they could help me manually open a Dropbox Business account. No, they couldn't. The best advice they were able to give me was to try clearing my browser cache and cookies (I did; it didn't help).
Finally I dug around and managed to find a link directly to a billing form, and was able to sign up by having them start billing me immediately instead of going through a free trial. I signed up for annual billing, naively assuming the per-user annual fee would be pro-rated (like Slack and most other good per-user services do) if our small company hired or lost any employees.
During the course of that year I did end up removing two users from our Dropbox Business account. Since we had already paid for the full year up front, I expected the next annual charge to reflect a pro-rated charge. But nope! The automatic renewal paid no attention to the _actual_ number of users on our account, and Dropbox charged us as if those users still existed.
Turns out the number of licenses you're billed for has to be managed manually. If you have 10 licenses and 10 users and then remove two users, that doesn't affect the license count. You have to remove two licenses manually. And if you pay up front for a year but remove two licenses halfway through the year? Too bad. No pro-rated reduced charge next year. Better be sure to predict your exact staffing numbers a year in advance next time.
Want to add a user halfway through the year when you're already at your license limit? It'll just fail with a cryptic error until you finally realize you need to first go to a different page and manually add a license. And sometimes (like literally as I type this) the Billing page you need to visit to do this is completely broken and just serves up an error that says "Oh hello. Sorry for this little hiccup."
Dropbox's core functionality works well and I have no complaints about it, but everything related to billing is so unintuitive and so frequently broken that I wonder whether they even care about it.
So yeah, I guess it doesn't surprise me that canceling is hard too.
tl;dr: I covered ~600 miles a day and it was a lovely trip.
I stuck to major highways and interstates for most of the route, though there were a few long legs in Colorado, New Mexico, and Texas that were on minor highways off the beaten trail.
It was a really fun trip and I'm dying to take more long road trips in the car. My experience definitely wasn't anything like the one the author of this article had.
SmugMug will generate a zip file containing the original, unmodified images and videos in the gallery, and will email you a download link when it's ready.
This is likely to confuse people, and it's also likely to cause people to reach out to me when they need help with rawgit2.com.
It'll scan all your pens and try to suggest jsDelivr URLs wherever you've used RawGit.
It came down to a simple equation: fighting abuse on RawGit will _always_ take more time and effort than spreading abuse via RawGit. One persistent jerk working a few hours a day could do so much damage so quickly that mitigating it would require multiple people working full time.
There's just no good way to scale that and retain the functionality that actually made RawGit useful.
I talked about this a little more here: https://github.com/rgrove/rawgit/pull/191#issuecomment-42831...
HTTP/1.1 200 OK
Date: Fri, 12 Oct 2018 17:56:30 GMT
Content-Type: application/json;charset=utf-8
Transfer-Encoding: chunked
Connection: close
X-Content-Type-Options: nosniff
X-Robots-Tag: none
Access-Control-Allow-Origin: *
ETag: "9c153866d0cad7024c0f31eb7b65be11582a6737"
Cache-Control: max-age=86400
Vary: Accept-Encoding
RawGit-Cache-Status: HIT
Server: NetDNA-cache/2.2
Strict-Transport-Security: max-age=31536000; preload
X-Cache: HITIn the shutdown announcement I committed to keeping the site running in sunset mode for at least a year. Hopefully that's plenty of time for everyone who's aware of the shutdown to migrate, but I expect there will be stragglers.
My unofficial, subject-to-change plan for dealing with that is that at the end of the sunset year, if there's still a significant amount of traffic, I'll start throttling requests to make RawGit slower. Hopefully people will notice their websites are slow and will investigate. I'll also try to notify stragglers individually by filing issues against their GitHub repos if possible.
I've actually never accepted donations. I paid the meager cost of the $10/month DigitalOcean droplet for the origin server, and StackPath (formerly MaxCDN) sponsored the CDN, which handled the majority of RawGit's traffic.
Once, I worked out how much the CDN bill would have been if StackPath hadn't sponsored me and my head nearly exploded. So yeah, I definitely couldn't have done it without them!
I have a Model 3 and so far haven't had any problems with updates. Installed the most recent one (2018.32.2) last night.
I wonder how significant the difference is between pupil dilation while looking at a bright phone in a dark room and while looking at a bright phone in a bright room.
Can someone explain why it would be worse to look at a cell phone in the dark? It's emitting the same blue light (or less, if the display gets dimmer) as it is in a bright environment. Why is that light more harmful in a dark environment?