topher200

This article is from mid-October.

I have a preempt-able workload for which I could use Spot instances or Savings Plans.

Does anyone have experience running Spot in 2025? If you were to start over, would you keep using Spot?

  - I observe with pricing that Spot is cheaper
  - I am running on three different architectures, which should limit Spot unavailability
  - I've been running about 50 Spot EC2 instances for a month without issue. I'm debating turning it on for many more instances

It didn't last 3 days -- the repo now 404s

Also https://audioread.com/. I love that you can forward emails to audioread and they'll be transcribed into podcasts. Thank you AI-voiced Matt Levine!

I occasionally ponder on how frustrating it is that the deceased don't get to hear their eulogies. It would have been amazing for Bram to have been able to experience all the outpouring of support and love from people he is interacted with during his life. Especially in a context where the speakers aren't considering him as an audience -- they're sharing their deep and true feelings.

No one can really be sure how their acquaintances feel about them. Eulogies are the closest we get. Imagine if he were able to hear all these great things said about him... It would be such a joy.

tig is great for a read only operations. Looking at the tree, peeking at diffs, finding specific commits. It's quicker to get in and out of. I reach for it instead of `git log`.

lazygit makes it super easy to make modifications. Reorder commits, revert specific hunks from commits. I find it easier to use if I need to look at a really big diff. I reach for it instead of `git rebase -i`, and it can do things no native tool can do easily (such as revert or extract specific hunks from commit earlier in the tree.

I use both multiple times per day. tig if I just want to look at stuff (fewer keystrokes to look at diffs in the tui!) and lazygit if I want to modify stuff (more powerful!).

If you click through to the Project Zero blogspot it says the Mar 2023 security update fixes the issue for the Pixel devices.

My Pixel 7 didn't show an update was available (last checked 30 minutes ago) but when I manually checked it found it and downloaded it.

I've watched those videos, and they're always super upfront with "this video was sponsored by the Gates foundation." I don't see a problem here.

RDS Proxy is very specific with which versions it supports. If it says it doesn't support it, it doesn't support it.

Postgres 14 is supposed to have built-in connection pooling. If you're on it, do you still feel the need for RDS Proxy? We're using pgbouncer and can't decide if we should switch to RDS Proxy or upgrade to Postgres 14 and drop the external connection pooler.

Congrats team!

The one I use the most is `vipe`.

vipe: insert a text editor into a pipe

It's useful when you want to edit some input text before passing it to a different function. For example, if I want to delete many of my git branches (but not all my git branches):

  $ git branch | vipe | xargs git branch -D

Constantly

shameless self-promotion

Three ex-Pebblers went on to found Memfault(YC W19, https://memfault.com), taking what they learned about managing a fleet of IOT devices and building a suite of monitoring and OTA tools to support other hardware companies.

Answering questions like "did fleet battery life get worse with yesterday's update?" get really really hard when you start managing thousands of devices. Memfault is all about making it easier to create the next Pebble.

We're hiring! https://www.workatastartup.com/companies/memfault

Congrats on launching!

How mature is this? We have a 20 person team and we're prototyping different pipelines for our next CI/CD pipeline (currently Heroku). Is this ready for production workloads?

There's some code examples in their docs: https://docs.dagger.io/1202/plan

I wrote a "smart" random clicker. It iterates through all the shapes and clicks their locations in a double-for loop. I added some jitter because it can't tell when it succeeds (so sometimes it starts in the "middle" of a loop and get stuck).

Paste this in the console and go! https://gist.github.com/topher200/aead3fd53b0f26bf880e7752eb...

I got a score of 33 on the first full run, which seems to be the highest in the thread (just barely beating the manual brute-force 31 run from @chungy[1]). I think it could be improved by being smarter about the when to click a random guess (or figuring out a way to remove the random clicking completely).

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

From the beginning of TFA:

An extreme example which proves the point: the cryptocurrency enthusiast community largely believes that code is law, “not your keys, not your coins”, etc. Many crypto enthusiasts would say that the Bitcoin protocol does not prohibit reversing transactions but provides a security guarantee which suggests that the likelihood of a reversal after an hour is infinitesimal.

And yet: someone sent $70 million worth of Bitcoin in 2016, and that transaction was partially voided, with the reversal being worth slightly more than $70 million due to Bitcoin volatility. This didn’t happen an hour later; it happened in 2022. How?

The answer is nowhere in the Bitcoin whitepaper or any codebase. A full recounting of it is outside the scope of this anecdote, but it rhymes with “If you and the United States federal government disagree whether a transaction is final, you are wrong.” That is true for notorious Bitcoin thefts, but also true for wire transfers, conveyances of real estate, credit card payments, and graverobbing. “Possession is nine-tenths of the law,” so the saying goes, but the state can conjure as many tenths as required if it is motivated to.

I agree with this take. I've used a Freestyle 2 for years and _loved_ it. I tried the Advantage 2 and it gave me headaches -- I couldn't deal with the keys being in different spots.

Switched back to Freestyle 2 and I couldn't be happier.

The pricing was updated today: https://gitlab.com/stavros/imgz/-/commit/7bdac35c8bc397bf829...

@jpgrayson (since I see you lurking around here) Thanks for maintaining stgit! I've been a recent convert and it's a great workflow improvement. I used to be a big `git rebase -i` user and stgit works so much more fluidly and fits great with my mental model of how I want git to behave. Thanks!

I'd love to add functionality that mimics `git rebase -i`. That is, you would open an editor and be able to select which patches you want on your stack as well as possibly designate patches as 'squash' or 'fix' from your editor. Think of it as `stg sink`, but able to operate on multiple patches at once.

Prior art: this script[1] already performs a re-ordering of commits but in a pretty hacky way. I'd like to productize it!

I'd love to have this new `stg rebase --interactive` be part of the main repo to enjoy the benefits of the existing test suite. My question for you is around how to include the new command with the rest of the tools. Would you want it to integrate with the existing rebase command (`stg rebase --interactive`) or is it something more appropriate for `contrib` (so a new independent command like `stg-rebase-interactive`)?

[1] https://github.com/da-x/misc-gitology/blob/master/stg-rebase...

I quit Google last month specifically because I didn't want to move back to MTV in September.

I don't believe that a system reboot is a symptom of this issue, just app crashes. Also, the bug started yesterday afternoon. I doubt this has anything to do with your system reboots.

Interestingly, the Google SRE book[1] mentions scenarios where they practice exactly this:

The solution to this Chubby scenario is interesting: SRE makes sure that global Chubby meets, but does not significantly exceed, its service level objective. In any given quarter, if a true failure has not dropped availability below the target, a controlled outage will be synthesized by intentionally taking down the system.

I doubt there are any customer-facing systems that practice this technique. Just super interesting that it exists.

[1] https://sre.google/sre-book/service-level-objectives/#xref_r...

Suggested alternate title:

Replit Dotcom: 'repl.it' moves to 'replit.com'

I'm a huge fan of tig. It maps really well to my way of thinking about git repos and it is super quick way to see the graph of everything that's going on. In the Top 5 of command line tools for me.

My advice would be to add more milestones. "People seem to indicate everything is OK until the end of the sprint." Ok -- have them show it off. Have a milestone in the middle of the week (ie Wednesday morning) and have the dev showcase that they've completed it. That'll get UX/QA eyes on the feature earlier and it's harder to just say "yeah, I'm working on it."

My personal favorite solves the same problem but attacks it differently.

Make JSON greppable!

gron[1] transforms JSON into discrete assignments to make it easier to grep for what you want and see the absolute 'path' to it. It eases the exploration of APIs that return large blobs of JSON but have terrible documentation.

  ▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page=1" | fgrep "commit.author"
  json[0].commit.author = {};
  json[0].commit.author.date = "2016-07-02T10:51:21Z";
  json[0].commit.author.email = "mail@tomnomnom.com";
  json[0].commit.author.name = "Tom Hudson";

I've found their API to be the best part of the product, especially for hobby apps. I was very impressed at the work put into the suite of API docs.

A great video on the different theories of the Lost Colony: https://www.youtube.com/watch?v=iTOKRWgjOlg

The author is based in Taiwan. I believe he would have good insight into developments and trends in Asian regions generally.

That's a very interesting list of absent economies that you posted though. We don't hear much from the telecom/internet backbone from those areas... perhaps they don't have as much local development and rely more on US/China based developments and infrastructure.