HN user

cuu508

2,798 karma

I'm Pēteris Caune, founder of Healthchecks.io

my-hn-username-here@monkeyseemonkeydo.lv

Posts85
Comments878
View on HN
infinite-battery.com 4mo ago

Infinite Battery Cargo (Repairable Battery Pack)

cuu508
2pts0
www.androidpolice.com 6mo ago

The Click Communicator combines Blackberry function with modern smartphone form

cuu508
2pts1
github.com 7mo ago

Real World Django Applications

cuu508
1pts0
www.politico.eu 9mo ago

One-man campaign ravages EU 'Chat Control' bill

cuu508
767pts258
github.com 1y ago

MeshCore, a new lightweight, hybrid routing mesh protocol for packet radios

cuu508
101pts36
status.hetzner.com 1y ago

Mainboard Replacements for Hetzner's AX42, AX52 and AX102 Servers

cuu508
1pts0
news.ycombinator.com 2y ago

Twilio Notice of Security Incident with 3rd Party Carrier

cuu508
6pts6
github.com 2y ago

Cloudflare DDNS, a feature-rich and robust Cloudflare DDNS updater

cuu508
2pts0
old.reddit.com 2y ago

The Immich core team goes full-time

cuu508
5pts0
blog.netdata.cloud 2y ago

New Streamlined Plan Structure (Netdata)

cuu508
2pts0
www.bleepingcomputer.com 2y ago

Denmark orders schools to stop sending student data to Google

cuu508
3pts0
blog.codinghorror.com 2y ago

I Fight for the Users

cuu508
3pts1
www.nordiskbil.com 2y ago

Sweden could be a new nightmare for Elon Musk

cuu508
6pts11
news.ycombinator.com 2y ago

Braintree password reset for non-SSO users with passwords older than 6 months

cuu508
3pts0
commission.europa.eu 3y ago

Adequacy Decision on the EU-US Data Privacy Framework

cuu508
3pts0
mrshll.com 3y ago

Self-Hosted Mastodon

cuu508
2pts0
www.bloomberg.com 3y ago

Configuring UWSGI for Production Deployment (2019)

cuu508
1pts0
blog.healthchecks.io 3y ago

I Found a Vulnerability in Croniter

cuu508
1pts0
medium.com 3y ago

I Used GPT-3 to Find 213 Security Vulnerabilities in a Single Codebase

cuu508
5pts1
github.com 3y ago

Dodo – Synchronize your Twitter timeline to a local database

cuu508
1pts0
joshmock.com 3y ago

Personal Backups and File Archival

cuu508
2pts1
blog.sucuri.net 3y ago

Uceprotect: When RBLs Go Bad

cuu508
1pts0
simme.dev 3y ago

Observability is becoming mission critical, but who watches the watchmen?

cuu508
45pts10
www.citusdata.com 3y ago

Distributed Postgres goes full open source with Citus: why, what and how

cuu508
2pts0
twitter.com 3y ago

Dear SEO experts, I need your help with Bing (site not indexed, detects malware)

cuu508
1pts0
ohdear.app 4y ago

Building Oh Dear’s new design: Creating a color system, why and how

cuu508
1pts0
github.com 4y ago

Favonia/Cloudflare-ddns – A small and fast DDNS updater for Cloudflare

cuu508
2pts0
github.com 4y ago

Privacy-Respecting Software

cuu508
162pts51
wtfutil.com 4y ago

WTF – The Terminal Dashboard

cuu508
2pts0
old.reddit.com 4y ago

Protests grow in Russia where they are being arrested for holding blank signs

cuu508
15pts1

I have fond memories of Flash 5 in early 2000s. At the time I knew BASIC and Pascal. I could figure out how to draw things, how to animate them using keyframes and motion tweening, and how to make things interactive with ActionScript, all by poking around and reading the help manual (F1) on our underpowered offline PC.

I've realized this as well, the bigger the company the worse the experience.

The more customers they have the less they care about any individual customer.

The more products they have the less they care about any single product.

The more employees they have the less they care about each individual employee doing a good job. And there's no they any more, there's a big, soul-less profit glutton.

Oh, interesting, I stand corrected!

I was investigating this 5 months ago and the answer their slop machine gave was:

Does Mollie retry failed payments (dunning) and track subscription states? Mollie does not currently provide automatic dunning or retry logic for failed subscription payments. Subscription states like active or past due are tracked, but you need to implement retry and notification logic in your system. This is a common feature request and may be on the roadmap, but no official release date is available.

From your link, note though:

If your subscription payment does not succeed, Mollie may attempt it again up to 5 times (once a day), depending on the failure reason. After all retries have been exhausted, the subscription will be cancelled.

If there's a payment issue, I would not consider cancelling the subscription 5 days after the first failure as reasonable. I would expect the subscription to go into "past due" state, and to keep retrying.

Do you know of any EU payment processor that supports recurring payments like a SaaS would need (subscriptions, subscription state tracking, automatic retries of failed payments)?

I looked but couldn't find any. Adyen does not do this on its own AFAICT, only with 3rd party addons that implement recurring payments on top of it. Mollie claims it does this but is woefully incomplete (no failed payment retries for example), and appears to be all in on slop.

Immich 3.0 20 days ago

I just don't get it!

This is open source, volunteer developers often focus on doing things that are fun to them, or that scratch their own itch. I can't imagine dealing with Google Photos semi-broken exports is fun to anybody, and you only deal with the pain of the import once, afterwards there's no itch to scratch.

I add a note in the password manager's notes field for sites where I've added Yubikeys as the second factor. I can get the list of the sites using search, and from time to time I go through them to check if a backup key needs to be registered. I create new accounts infrequently.

A little nice thing the cars could do is automatically calibrate the speedometer from GPS when on a long stretch of a road. You would get the accuracy of GPS and the reliability of speedometer even when in city jungle, underground, during slow speed manoeuvres etc.

A dumb and simple solution is separate physical routers for the home stuff and for the homelab stuff. Each group of clients is behind its own NAT.

The argument assumes that unassisted PR authorship is what builds trustworthy contributors, and that LLM assistance prevents that growth.

No, I don't think that was the argument. As I understood it, unassisted contributions have higher chances to grow a trusted contributor. Not 100% vs 0% chances, but statistically higher. So, given limited resources, it makes sense to prefer unassisted over assisted contributions.