tams

Also, there was qdb.us:

https://web.archive.org/web/20190802095853/http://www.qdb.us...

The UI reminds me of CrashPlan of old times.

What's the unique selling point?

The key to using org-mode effectively is ignoring most of the features and using only a tiny subset that you actually need.

You aren't going to look like a wizard, but you are also not going to need to maintain anything ever. These kinds of cookbooks are nice to have around, but it's best to treat them as references, not guides.

If you're on AWS you can use Performance Insights [1] from PostgreSQL 10 and up.

[1] https://aws.amazon.com/rds/performance-insights/

Even with cloud specific technologies still have to option to use locally running alternatives for development with a little abstraction.

Unless your core business specifically targets the capabilities of chosen cloud specific tech, you can get away with developing on a supplemental solution and rely on CI plus staging environments to uncover and fix the edge cases that you miss this way.

This is especially true with low-level stuff like databases and queues. I've worked like this for years and never had to worry much about it.

In the light of this, it's much more obvious why they stared exposing the Facebook brand in their Instagram and WhatsApp properties.

What environment and config produces that result for you? I can definitely tell the difference under KDE, libinput and good old X.

With RSS/Atom, the history so far is that any use case of open feeds that gets popular enough is eventually consumed by platforms, with the feeds discontinued.

Same with podcasts: the current open golden age always felt like was going to be temporary and so far Spotify looks like the most likely player to eat the mainstream.

It's a great podcast app which gives the user a ton of freedom and tweaking possibilities, but it's also set and forget.

If this is the first time you hear about it, the safest place to obtain it is the author's Google Drive: https://twitter.com/PodcastAddict/status/1262047866614247425

You don't get much in terms of performance and capacity in the free tier preventing you from testing anything beyond the tiniest workloads.

If you need to pre-arrange expenses with the finance department, it's much faster to test drive with credits.

> Examples are now downloadable. We’ve added a script to zip up and offer all our Examples as their own download from the docs.

Nice. This could become the primary documentation for a lot of folks.

So now that the IDE is on the web, it would be pretty neat to be able to automatically launch interactive debugging sessions when breakpoints are hit in CI jobs.

Does any CI solution already offer something like this?

There are lots of tools you can use to back up to Backblaze, including their comsumer backup service.

If you want to sync to B2 specifically with a lightweight tool, check out https://rclone.org/

To avoid sync issues it's important that Emacs is set up for both autosaving and reloading on external changes.

If you add Orgzly to the mix for mobile access, you also want to configure Orgzly to auto-save whenever you open it or make changes.

With these two adjustments this becomes a pretty good setup.

I'm using the fork after having issues with the sync stopping and restarting only after device reboots with the original version. So far so good.

> Listening to new music is hard.

It's harder if getting familiar with a piece of music also makes it boring to you for a while.

I enjoy threads like [1], [2] about strategies for discovering new music.

[1] https://news.ycombinator.com/item?id=22194107

[2] https://news.ycombinator.com/item?id=1161002

Air gapping only means lack of network interfaces, so sneakernet is used to transmit data.

And sneakernet (floppies back then) was the primary delivery medium for computer viruses before it was common for personal computers to have internet access.

> And you can live without a car, it is about structuring your life better.

While that's certainly holds true for some metro areas, it's certainly not a rule for sprawling US cities built for cars. Opting out of car ownership limits your employment options, social mobility, and so on.

Spacemacs is great, albeit slow at times.

On the evil front there is also Doom Emacs (https://github.com/hlissner/doom-emacs) which is better optimized and is still pretty full-featured.

Last time I touched Lightsail it looked like a t2 instance rebrand without the option to pay for extra CPU credits.

It grinds to a half if you use up your compute stipend and you cannot do anything about it. That's a big risk for a VPS-like use-case.

True, and it's a shame. But it might not matter that much in this accessibility context as Google is also an advertising company.

Startpage.com, a Google proxy, still works fine in lynx.

What is the advantage of using Fargate instead of Batch for this use case?

With the sunset date passing, Python 2 is going to become a niche while still having a massive install base.

There's a lot of money to be made doing migrations and keeping the beast itself alive.

Been there, self-hosted my email for more than half a decade, gave up on it a few years ago for a couple for reasons:

If you are self-hosting the most important authentication fallback for your online identity, an ill-timed downtime or deliverability problem really hurts.

Your reputation can be affected by neighboring bad actors you have no control over. For example, SpamRATS punishes full subnets without an actual appeals process.

From the point of view of a major provider, the same email from your tiny server is going to have a lower score than one from their system. Encountered this a lot against Gmail.

And it's a commitment. If you go the self-hosted route, you will need need to keep up on new security and filtering practices, even if you use a turnkey solution. You might get bored with this after a while.

I found Peppa Pig a great resource to start grasping a new language.

The dialogs are repetitive enough to be gentle practice for recognizing words through speech, and the characters' struggles in learning new concepts also lead to some helpful descriptions that can supplant a dictionary.

SQS was introduced before S3, but the analogy might still be valid.

That's some hacker spirit.

Technical debt is a wonderful ally when building prototypes.

Imagine you are building a prototype and you are clever enough to only focus on validating an idea. Having this focus you ignore all best practices and maintainability issues you might tend to out of habit.

What you are likely to end up with is a functioning application that resists change beyond its original goals.

And this is good. It lets you declare technical bankruptcy early enough to avoid painful rewrites on a software that was not meant to exist for long anyways.

Poetry is definitely an improvement.

Anyone considering it for production usage should note that package installs in the current versions are much slower than pip or Pipenv. This might affect your CI/CD.