How do you handle the context? As in: you have a forum like system as you say, how are agents finding the correct "posts"? How do you handle drift or specs that change over time?
95 karma · joined June 17, 2021
How do you handle the context? As in: you have a forum like system as you say, how are agents finding the correct "posts"? How do you handle drift or specs that change over time?
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?
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)?
There seem to be a lot of projects in this space -- including my own tool (https://github.com/gerwim/tunnlr). Still working on it though! ;-)
Yes, of course. Blame a third party library which was probably created by an open source maintainer instead of testing your own systems.
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…
In screentime you can set a different code, so when anyone else can access your phone, they can’t change the code and lock you out of your phone.
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.
[0]: https://phind.com
firefox -new-instance -P "Another Profile"
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
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 ;-).
[1]: https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-...
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?