Dr Ian Preston
Dr Ian Preston
The 2nd and 3rd issues seem to be solved in the latest Safari!!!!! This means custom peergos apps now work fully in Safari on MacOS and iOS!!!!
It seems like the 3rd issue was not actually fixed yet. But 2nd was the main issue for Peergos. Custom apps now run on Safari for public domains.
Apparently the 3rd issue is fixed as of MacOS 26 Tahoe: https://bugs.webkit.org/show_bug.cgi?id=160504#c19
No one is working on this at the moment.
Do you mean client side (i.e. in your Peergos space encrypted)? The server doesn't have access to this information.
We're hoping to add an optional version history per file. Would that suffice, or do you want a more general log including things like deletion/rename?
I guess the next question is would a sync client remove your need for this?
Which version is this? What does http://localhost:8000/api/v0/id return? What command are you using to run it? The password won't matter, and the if you try to signup with an invalid...
Ah right, sorry on localhost you will need to POST an empty body to that url with curl or similar.
Yep I want to see it, it is the public key hash of your server. (Trying to confirm a hunch)