In Canada we have these refillable prepaid VISA cards https://www.koho.ca/. Not a plug, but it's honestly solved money management for us.
Every week, my wife and I load some amount into the 'joint' card, and a smaller onto the personal cards. The joint card is for necessities, the personal cards are for fun. It's much more convenient than the cash envelopes we were doing before.
Credit cards don't work for us because it's too easy to cheat, and you only have to feel guilty when you square up the tracking. With the prepaid cards, you get a much harsher signal when you're over budget.
I've been using AWS Route53 DNS for my domain for many years, very cheap and easy to automate a DDNS setup if desired (e.g. https://crazymax.dev/ddns-route53/)
> Someone donating large amounts of money to charity just to write it off on their taxes isn’t doing so altruistically
I mean, it's still altruistic because they're going to 'lose wealth' by donating. You're never going to earn back in tax write-offs as much as you spent by donating.
Disclaimer, I like the snap packaging format, and I'm not familiar with the history of launchpad.
Operationally:
- I can trivially host and control my own apt repository, either as a mirror of some upstream repository, or with bespoke packages.
- I can't do the same with snaps.
So launchpad and snap store isn't quite apples-to-apples. It would help of course if a snap store could be statically hosted or re-implemented, but the full API is quite complex.
Hear hear. I imagine for dogfooding, LXD is only packaged in snap, so we can't use apt as the source anymore. After migrating, an upstream push to a 'stable' LXD snap channel introduced a regression that borked our environments, and there was no way to:
1. prevent machines in the fleet from pulling the broken LXD update
2. rollback broken machines to the previously working LXD version on the same channel, since it no longer existed in the Snap Store™.
Foundational seems like a strong word here - this is a thin wrapper on top of two popular components from ROS (Navigation and MoveIt), and bringup for a specific robot (LoCoBot).
I appreciate the effort here though - ROS feels like it's become harder to use due to stale documentation, and there's value in providing a simple python API that abstracts the underlying bringup.
However looking through the wrapper and its documentation, it doesn't feel like it's making it much simpler by hiding away standard ROS tools.
Every week, my wife and I load some amount into the 'joint' card, and a smaller onto the personal cards. The joint card is for necessities, the personal cards are for fun. It's much more convenient than the cash envelopes we were doing before.
Credit cards don't work for us because it's too easy to cheat, and you only have to feel guilty when you square up the tracking. With the prepaid cards, you get a much harsher signal when you're over budget.