HN user

lucw

93 karma
Posts0
Comments54
View on HN
No posts found.

Very honest question: One of the use cases I had with OpenClaw that I'm missing now that I don't use it: I could tell it (via Telegram) to add something to my TODO list at home while I'm in the office. It would call a custom API I had set up that adds items to my TODO list. How can I replicate this without the hassle of setting up OpenClaw? How would you do it?

What you are looking for is an orchestration platform such as n8n or windmill.dev. You can still have a telegram bot and still use LLM for natural language interaction, but it's much more controlled than OpenClaw. I do exactly what you describe, add todos to my todoist account from telegram.

Microsoft came up with some objectively good products both for consumers and developers in the recent decade. For consumers, Xbox would be the biggest one, and for developers, VSCode, WSL/WSL2, Azure.

IPv6 adoption will take place overnight when either google chrome, Android or iOS start showing a warning on IPv4-only networks. ISPs and tech companies will start to get flooded with support calls asking about it and will choose to roll out IPv6 to make the problem go away. Chrome forced the web to go 100% https, the same thing will happen eventually with IPv6.

I went through this around a year ago. I wanted to postgres for django apps, and I didn't want to pay the insane prices required by cloud providers for a replicated setup. I wanted a replicated setup on hetzner VMs and I wanted full control over the backup process. I wanted the deployment to be done using ansible, and I wanted my database servers to be stateless. If you vaporize both my heztner postgres VMs simultaneously, I lose one minute of data. (If I just lose the primary I probably lose less than a second of data due to realtime replication).

I'll be honest it's not documented as well as it could, some concepts like the archive process and the replication setup took me a while to understand. I also had trouble understanding what roles the various tools played. Initially I thought I could roll my own backup but then later deployed pgBackrest. I deployed and destroyed VMs countless times (my ansible playbook does everything from VM creation on proxmox / hetzner API to installing postgres, setting up replication).

What is critical is testing your backup and recovery. Start writing some data. Blow up your database infra. See if you can recover. You need a high degree of automation in your deployment in order to gain confidence that you won't lose data.

My deployment looks like this: * two Postgres 16 instances, one primary, one replica (realtime replication) * both on Debian 12 (most stable platform for Postgres according to my research) * ansible playbooks for initial deployment as well as failover * archive file backups to rsync.net storage space (with zfs snapshots) every minute * full backups using pgBackrest every 24hrs, stored to rsync.net, wasabi, and hetzner storage box.

As you can guess, it was kind of a massive investment and forced me to become a sysadmin / DBA for a while (though I went the devops route with full ansible automation and automated testing). I gained quite a bit of knowledge which is great. But I'll probably have to re-design and seriously test at the next postgres major release. Sometimes I wonder whether I should have just accepted the cost of cloud postgres deployments.

Does anyone have any thoughts on what motivates people to play sudoku or write solvers for sudoku ? I have trouble finding motivation to solve artificial problems. That said I sink hundreds of hours into factorio.

With stripe, the testing environment is sufficiently powerful that you don't need to test in production. With the test environment, you should have enough confidence that the integration will work. If you feel the need to do a payment after going live, ask a friend to do it, not someone from your household.

Stripe knows your name, which you had to submit to go live. If your first payment is with a credit card in your name, particularly if it's a large amount (which the fraud system flags as money laundering), you will get banned with 100% certainty. Ask a friend who doesn't share your last name.

The article should start with more context, what is a notebook ? I know what it is, but the author is particularly bad at introducing his article.

Right Lago could be used as replacement to Stripe Billing. And one attractive feature is that it decouples your tech stack from Stripe (could use another payment processor and still handle the subscription lifecycle the same way). This is going to be more and more interesting to businesses who are getting increasingly wary of Stripe account bans.

Usage based billing is tough. I took a long hard look at lago and ultimately it wasn't for me (B2C API based business). I couldn't do without the customer portal which is a premium feature, and premium was at least $1,500 USD/month. My revenue couldn't justify this. To Lago's credit, they are purposefully staying away from percentage pricing. So they have to charge a lot on the base price. Stripe Billing charges a percentage and guess what, with a growing business it's only a matter of time before your Stripe bill tops that $1.5k.

I also looked at Stripe Billing for usage-based and it didn't meet my requirements either. (though I am using Stripe Billing with flat charges).

My exact use case is:

- I want to sell API credits upfront including for subscriptions (i.e. user signs up for $10/month of credits, they pay $10 upfront, and can spend $10 worth of credits). Stripe billing doesn't support charging upfront, for usage-based, they only bill after the billing period is finished. Some of my users have been gaming the system, canceling and not paying so that doesn't work for me. I believe Lago did support billing upfront.

- I want to freely mix subscription based and pre-paid credits. My users go over their quota one month, they don't want to upgrade their subscription to the highest tier, they prefer a one-off top-up. I need to control over which credit gets consumed first. Stripe billing and Lago both had issues with this, I can't remember exactly what.

- I wanted to support as many payment methods as possible, and particularly Chinese wallets for pre-paid credits (Alipay, Wechat). Lago has no plans to implement this, I was half considering implementing it myself inside Lago. I don't think Wechat and Alipay will matter much for B2B businesses.

- I'm also a huge fan of massively regression tested code, and Stripe Billing with its test clocks blows Lago out of the water here. Lago has no ability to walk the clock forward for subscription lifecycle testing. Though maybe this matters less if you have faith in the product, you can just expect to get the right callbacks on time.

I did notice that the Lago devs on slack took time to answer questions down to the deepest technical level. If I was running a B2B startup, I would probably try really hard to fit Lago in the picture, particularly at at time when stories of Stripe account bans are so prominent.

I'm currently managing development VMs (mostly Fedora Cloud) using Ansible on a Proxmox hypervisor and i'm mostly happy with how it works. I'm interested in experimenting with immutable OS's , the most immediate difference I see is that I'd have to start using Butane instead of CloudInit. Can anyone with experience comment on the pros and cons ? Right now, I really do everything in Ansible, including creating the VMs from a proxmox clone template.

This is good advice, if you haven't experienced the pain of doing it yourself, you won't know what the framework does for you. There are limits to this reasoning of course, we don't reimplement everything on the stack just for the learning experience. But starting with just docker might be a good idea.