iyn

Agreed 100%.

What's "worse" is that today we have access to (basically) real-time videos/evidence of the crimes and yet so many people claim that's all fake.

Israel is conducting a genocide in Gaza. The least we can do is be vocal about the reality.

It's shocking that so many people don't have any problem with that idea. "Never again"?

Agreed — came here to say exactly that. I like that this is not yet another tailwind template (nothing wrong with them, I use them all the time) but something with its own identity. I especially love the illustrations/icons. Well done!

https://xkcd.com/87/ this one?

Can you provide more info? Use-cases, how would it work, where will you publish it?

"I will support and defend the Constitution and laws of the United States of America against all enemies, foreign and domestic" [0]

[0] https://en.wikipedia.org/wiki/Oath_of_Allegiance_%28United_S...

I've too been thinking along these lines lately. A month ago I would think it's an alarmist/overblown to frame the situation in such a way but simply looking at the actions and ignoring the "justification"/propaganda must result in updating the model - it's indeed oligarchic takeover.

What's happening is a destruction of institutions, under the guise of efficiency.

If your goal was to establish authoritarian system and/or oligarchy in the US within a year and without firing any bullets, what would you do differently to what's happening now? Honest question I've been thinking about lately. My current answer is that the diff is not that big.

Yes, there's much to be done about efficiency/productivity on the government part, but this is not what's being done.

I am not sure if Elon is deliberate (similar to how "X is about free speech", DOGE is about "government efficiency" i.e. fake ideology to push some agenda) or an useful idiot (believes that all he's doing is improving efficiency, without realizing the consequences of destroying the institutions), but that's not the main point. The point is that fundamental institutions are being destroyed very, very quickly, without real oversight. This has important and negative consequences to democracy.

Thanks, I appreciate the additional context. Now all of it makes sense :)

Thank you, this is it!

Brilliant idea (moving the found item to the location you first looked at)! If you ever write a blog post about your org system/such tricks I'd happily read it :)

Thanks, I appreciate the detailed explanation.

I'm familiar with Vault and been using that at work — but we tend to fetch values from Vault and export them as env variables in the end anyway. Obviously we don't want to hardcode these values in the code either. So env vars are not good for secrets, hardcoding is terrible — what's good/secure then?

Ok, this sounds like a plausible direction — thanks!

It seems that Cursor is using Electron. I don't know about its internals (tried it a couple of times years ago), but after a quick look at the docs I've found this: https://www.electronjs.org/docs/latest/api/utility-process#u... which is a section describing `utilityProcess.fork(modulePath[, args][, options])`:

    env Object (optional) - Environment key-value pairs. Default is process.env.

I don't get why some unique-looking prefix/suffix would be needed there, though.

That's the thing, though — trying to understand the reason with this limited info. I imagine that I could perform some reverse engineering but I wondered if maybe someone has some ideas/suggestions. Serializing the env vars is one thing, the other is the fact that they prefix/suffix it with (what appears like) a random identifier.

I'm confused too :). The LuLu alert says [0]:

    process id: 54279
    process args: -p "<some id>" + JSON. stringify(process.env) + "<some id>"
    process path: /Applications/Cursor.app

The alert showed up right after I installed the app and clicked on the Cursor icon [1]. I understand that processes can access the entire environment by default (which was always a bit too "open"/strange for my taste, but I get the reason) but then I don't understand why you need to use `JSON. stringify(process.env)`

[0] <some id> was some 12 character hex string

[1] Note that this was like a month ago; I have a cold, so finally have time to catch up on such questions

> you could look into using something like “env” to spawn the process with a reduced environment

Can you elaborate/show an example?

I agree in general to limit sensitive data stored in env vars, but often it's not feasible. One might have e.g. AWS keys loaded when using Terraform. The problem in this particular case is that Cursor is not selective in what env vars are loaded, it serializes _everything_. That seems like an odd choice to me.

Clickable link to the screenshot: https://i.imgur.com/47UeNAw.png

Thanks, I’ve read the first part, it’s interesting that there’s no difference between selected candidates and dropouts. Also, pretty nice example of typist :)

Out of curiosity, what was the thesis about? Can you share the PDF?

Yeah, I've been in the same (amazing) rabbit hole, can recommend.

Are there any public sources about SM being written in Pascal? TIL

Can you give/point me to an example for how to do this (preemptive + cooperative combination)? What are the use cases? I’m new to embedded programming (and intermediate in Rust).

Thanks for guidance on sizing the instance(s), I'll experiment with that in the coming weeks.

Thanks for reaching out! Just to be clear, from what I can tell, both PeerDB and Temporal are great (and I’ve been hoping to learn Temporal for a while). At some point I considered self-hosting PeerDB but my impression was that it required multiple nodes to run properly and so it wasn’t budget friendly - this is also based on your pricing plans with $250 being the cheapest which suggests that it’s not cheap to host it (I’m trying to minimize costs until I have more customers). Please correct me if I’m wrong! Can you give me an example of a budget friendly deployment, e.g. how many EC2 instances for PeerDB would I need for one of the smaller RDS instances?

Given the acquisition by ClickHouse (congrats!), what can we expect for the CDC for sinks other than CH? Do you plan to continue supporting different targets or should we expect only CH focus?

Edit: also, any plans for supporting e.g. SNS/SQS/NATS or similar?

Yes, I think NATS is reasonable — I don't have operational experience with it but based on my earlier reading it seems that it can be run on a smaller budget. Is this "regular" NATS or the Jetstream variant?

Yeah, I've looked into PeerDB but in terms of self-hosting it's not really lightweight, as they depend on Temporal [0]. I'm currently optimizing for less complexity/budget, as I have just a few customers.

[0] https://docs.peerdb.io/architecture#dependencies

Thanks for the suggestion. I've seen it on GitHub but haven't really looked into operating it. I was under the impression it's more focused on the real-time aspect than CDC. Do you have any experience managing it? I'm curious how easy is it to self-host it and integrate with rest of my system.

I have these use cases:

1. Syncing data in Postgres to ElasticSearch/ClickHouse (which handle search/analytics on the data I store in PG)

2. Invoking my own workflow engine — I have built a system that allows end-users to define triggers that start workflows when some data change/is created. To determine whether I need to start the workflow, I need to inspect every CRUD operation and check it against triggers defined by the users.

I'm currently doing that in a duck-tape like way by publishing to SNS from my controllers and having SQS subscribers (mapped to Lambdas) that are responsible for different parts of my "pipeline". I don't like this system as it's not fault-tolerant and I'd prefer to do this by processing WAL and explicitly acknowledging processed changes.

Looks interesting, I’ve been investigating Postgres CDC solutions for a while, so I’m curious if this could help my use-case.

Can you elaborate on failure modes? What happens if e.g. NATS server (or worker/replicator) node dies?

In principle, how hard is it move data from Postgres not to another PG but e.g. ElasticSearch/ClickHouse?

Thanks for clarification, that makes sense.

Just to give you a bit more context, I've been evaluating CDC (change data capture) tooling and Prisma Pulse was one of the options. My primary data storage is Postgres but I have a need to react when data in some tables is changed (depending on some user-provided filters). I'm currently handling that with naive message push to SQS, because Debezium/Kafka setup is too expensive/complex. Prisma Pulse looks great, but that CDC part of my app is crucial and I need an option to be able to host it myself/on premises for some customers.

However I totally understand the need to build a moat — good luck on your journey!

Congrats on the launch, this looks very interesting!

Will it ever be possible to self-host Prisma Postgres (or Pulse)? It's great that I can use your platform, but if I adopted e.g. Pulse, that's a non-trivial vendor lock in. I'd feel _much_ safer/confident building my app around the Prisma stack (besides the ORM, which I like).