HN user

gerwim

94 karma
Posts0
Comments30
View on HN
No posts found.

That would work for a single instance, but when running multiple (e.g., you are horizontally scaled) it would not be ideal.

Is it possible to mimic "subtrace.dev"? There's the 'SUBTRACE_ENDPOINT' environment variable which can be used to set the target endpoint, but is the server side open source too? And does the license grant permission for self hosting the full stack?

Looks great! Reading through the docs it seems the subtrace process sends all data to your server. I'm reluctant to do that on a production environment, where API keys and personal data are being handled.

Is there any way to run it completely self hosted? If not, are there plans? And how will you monitize self hosted options (if it's possible)?

Core only has the "full backup". Incremental and other types are available to enterprise. I run the Core edition (with full backups) for my personal projects.

Wyze blamed "a third-party caching client library that was recently integrated into our system" for the trouble.

Yes, of course. Blame a third party library which was probably created by an open source maintainer instead of testing your own systems.

Another fun fact about .dev which I recently found out while working on a side project:

You NEED to use https when visiting any .dev domain. Google has put it on the HSTS preload list.

It took me a while to find out why my browser kept redirecting me to https when I wanted to use http (local development). Curl worked fine…

What is this post ranting about? Pushing your keys to big tech? There is no difference if you use Chrome’s password manager for passwords or passkeys.

You can save passkeys on your own network if you use Bitwarden or if you want, write your own solution.

For 99% of the internet users, passkeys are much better than passwords.

I didn’t know they needed developers. I’m an avid Plex user but C# developer by trade. Cloned the server and web projects and worked on my first issue!

Which is funny, because I own an iPad from 2018. Which has the A10 chip (which was used in the iPhone 7). Guess what, the iPhone does not get iOS 17 but the iPad does get iPadOS 17.

I did some geekbench tests.

4 GB, 3 CPU AMD [1]

8 GB, 4 CPU AMD [2]

8 GB, 2 CPU (dedicated) AMD [3]

So even though the dedicated CPU option has stable performance, the shared CPU is almost 4x as fast. Sure, the shared results would fluctuate but given they are similar priced. Or maybe I was just lucky and got on an empty node.

[1] https://browser.geekbench.com/v6/cpu/2360706

[2] https://browser.geekbench.com/v6/cpu/2360698

[3] https://browser.geekbench.com/v6/cpu/2360730

Looks great! I see your tool uses Hetzner block volumes for storage. How do you manage your data backups (as Hetzner does not offer anything for their block storage volumes as far as I know).

My current setup is also on Hetzner. 1 master and 3 worker nodes. Managed by Rancher and I use Longhorn (also from Rancher Labs) for storage. It runs stable for two years now. But looking for a simpler solution, so I looked into k3s and k0s last week -- will also look into your tool ;-).

Looks great! I currently use Auth0 for my projects. One specific feature in Auth0 prevents me from switching to any other IAM: rules (or their new version: actions).

It’s basically running some JavaScript upon logging in (or signing up, or when a machine to machine token is created). It allows me to extend the created JWT with custom properties and perform backend logic (e.g. perform an API call upon user registration).

Is this something Logto will eventually support?

> The obvious conclusion is Apple will start to scan photos kept on device, even where iCloud is not used.

Wrong [1]. It's even in the first line of the document which you apparently didn't even read:

  CSAM Detection enables Apple to accurately identify and report iCloud users who store
  known Child Sexual Abuse Material (CSAM) in their iCloud Photos accounts
This doesn't mean I'm supporting their new "feature".

1. https://www.apple.com/child-safety/pdf/CSAM_Detection_Techni...