To the sibling comment: It's in case you wish to acquire citizenship in another country that does not recognise dual citizenship.
I.e. that [new] country will not allow you to become a citizen of it unless you renounce your original one.
What that might actually mean practically, or if you can un-renounce it later, I don't know. [Edit]: Turns out, according to that page, yes, you can do that with some kind of bureaucratic shuffle. Daft - but sometimes these things are.
I run vibed apps on my iphone just fine - you have to register for a developer account and pay the annual fee, but I have an agent app running that can improve itself and push new versions over wifi just fine.
I even have realtime watch complications which no shipping app can have because of apple restrictions - developer mode lets you push complication updates realtime if you want.
I'll probably consider something more open next time I buy but just pointing out that right now with a developer account you're not actually _that_ restricted on iOS, the experience is better than you might think if you're making an app you never intend to ship.
I already have an account so I use that regardless, but AFAICT you can in fact build for your own device without paying at all. I haven't tested this though.
I am not arguing Apple's restrictions are a good thing, if I were in charge I would in fact make allowing installing your own software on your own device a legal requirement of selling hardware, yet here we are.
There are many ways to do this without using mcp, for example one of the many proxy servers that inject the token into requests. I use a custom solution that redacts all secrets to agent transcripts before the agent sees them in a hook.
I find it way better to be able to confidently tell agents to use CLIs than worrying about partially implemented mcps that need configuration and are often yolo’d with npx @latest anyway
This copies arbitrarily sized DBs sub-second - I use it on dbs larger than 1TB regularly - and has the advantage of being copy-on-write - the new db doesn't take up any extra disk space until you start writing to it in which case only the differences are used.
I assume it's only fast for large databases when running on a filesystem that supports copy-on-write? In particular, I assume it won't benefit from CoW on a tmpfs?
I do know that if it's not supported by the underlying filesystem if falls back to the default.
What I don't know is if it's faster to copy than a regular copy on a ram tmpfs - since it may be essentially be doing "nothing" - updating some pointers instead of copying stuff in ram.
So if your workload is limited by copy not execution speed it might be worth testing.
However at that point you're running on a regular FS so if you're trying to benefit test speed by having all your regular postgres operations on a ramdisk, that part will end up being slower.
I'm actually curious if this is faster than a tmpfs clone, I suspect it might be as depending on how many underlying files it's copying, it might effectively be doing "nothing" for each file.
Obviously operations after that will be a lot slower reading / writing to a normal disk
reply