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.
Whoops, I probably should have known better than to mention specific pricing since it can vary based on local taxes (such as VAT), and because we test different plans from time to time. But if you're interested in the lower tier plan I mentioned and you're not seeing it on the site, feel free to email [email protected] and ask for Jennifer, one of our Support Heroes. She'll take care of you!
SmugMug will give you unlimited photo storage for as little as $6.25 US per month (if you pay yearly). There are official apps for iOS and macOS (as well as other platforms) that support auto upload. You can easily share your account with your wife.
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.
The article's title is misleading, and it misrepresents the content and conclusions of some of its sources.
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."
The article claims Tesla is incorrect when they say that "the average ICE vehicle gets around 22 MPG", and counters with EPA stats showing that the average fuel economy of all vehicles in the US is 24.9 MPG.
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.
A little over a year ago I spent days and days trying and failing to sign up for a Dropbox Business account.
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.
Last summer I took a road trip from Oregon to Texas and back in a Tesla Model 3. I covered about 600 miles a day over the course of 8 days, for a total of nearly 5,000 miles. I never had a problem finding a supercharger along my route, never had to wait to charge, and rarely had to spend more than 30 minutes charging before continuing.
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.
Log into your SmugMug account and open the Organizer. Browse to the gallery (or galleries) containing the videos you want to download, click the "Download" button in the toolbar (downward pointing arrow with a flat line underneath), and select "Download Gallery".
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.
I did consider this, and several people have offered to take over, but ultimately I feel that the thing that was most useful about RawGit — it made serving HTML at scale dead simple for anyone with a GitHub repo — is also the thing that made it most prone to abuse.
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'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.