Could you share why?
302 karma · joined February 4, 2023
Could you share why?
If the re-minting happens transparently with a user interaction then you spread out some of the request velocity that can come with that (if you're operating at a large enough scale for it to matter for this to be a concern).
Calendar Versioning (CalVer, YYYY.Release.Patch) fulfills the same need and you can see it in practice with Jetbrains (e.g. the latest version of IDEA is 2025.3.6).
The only difference is Jetbrains uses YYYY.R for marketing, see: "What's new In 2025.3"[1]
Is it not a rage-bait argument to say that not having types implies less stability?
Is the focus on density around performance, visualization, or something else?
I was curious to see if there was a video of it being done and this seems to be it. Incredibly delicate is an understatement.
My original comment wasn't intended to indicate that there is an obligation to provide support. The deliberate choice to: a) not offer paid support for open-source deployments, and b) sunsetting the Kubernetes deployments in favor of their cloud version, is a signal that shows PostHog doesn't /really/ want you to be running the software in a self-hosted manner.
Just look at the "Open-source hobby deploy" (from the README in git) which calls out that it "should scale to approximately 100k events per month" but their cloud offering gives you 1 million events per month for free. What is the point of the hobby "deploy"?
Back to OP -- my answer is yes, this is a source-available service that you can modify and play around with locally. The source and documentation behind the operations of PostHog aren't available.
"We no longer support paid, open-source deployments and it is no longer possible to buy licenses for self-hosted versions - we instead recommend migrating to PostHog Cloud." - from: https://posthog.com/docs/self-host
I use the 32" Odyssey G7 which is 2560x1440@240Hz.
List price of Backblaze:
$0.005/GB - Base Storage
$0.01/GB - Egress (Use a data partner to bring this down to $0)
$0 - PUT API Requests
$0.004/10,000 - GET API Requests
No delete penalties a/k/a minimum storage
List price of Glacier Instant Retrieval:
$0.004/GB - Base Storage
$0.09/GB - Egress
$0.02/1,000 - PUT API Requests
$0.01/1,000 - GET API Requests
Billed for 90 days of storage
For the third point, what I've suggested in the past to push your artifacts into the region (since that's free) and then pull it down from S3. This lets you only incur S3 costs which tend to be cheaper then NAT data transfer costs (assuming you're using a VPC endpoint or equivalent).
It feels that half of my inbox is people yelling "we've been running this in production", the other half yelling "this is this worst thing to do in the cloud next to leaving S3 buckets open".
I'd love to know your sentiment if you have one as I didn't expect to hit such a nerve.
A huge step in the right direction to no longer have to use the API to get around training the underlying models -- including ChatGPT4.