calendar.xyehr.cn/share/177280...
calendar.xyehr.cn/share/177280...
My birthday, tomorrow.
See you.
Fixed
Weβre currently experiencing issues
calendarstatus.xyehr.cn/incidents/01...
Hello, March.
P.S. Any questions? Just contact us via email!
Click the Question button and then choose the feedback
We got a new bluesky profile banner!
Our calendar project has a built-in countdown function!
You can now choose to delete all events under a calendar category when deleting that category! π π
Our database is located in Sweden πΈπͺ
Added a sync status button
Merged @danielmorrisey.com 's pull request to main branch!
added tangled link on footer
We hit 20 stars on GitHub!
i think so
Updated landing pageπ
Closing the atproto login channel.....
It will open when we find a security way to store your data
wow so many stars!
The second approach is to store the encrypted data in our PostgreSQL database. This approach can change the visibility of your encrypted data, but it also deviates from decentralization, so ATProto becomes useless (it's only used for OAuth authorization login).
We currently have two atproto integration solutions.
The first approach stores ciphertext in the atproto repository, which we currently use. While strong keys make the data theoretically secure, the ciphertext is public, and the official docs advise against it.
Since I wasn't aware of the Permissioned PDS approach, I figured that as long as the ciphertext had a strong password, it would be secure enough.
Thanks for the feedback! I missed the Permissioned PDS section at the time, so I overlooked it. Iβll look into it and update accordingly
The ciphertext in the ATProto repo can be accessed by anyone, but only clients with the decryption key can read it. Itβs like an encrypted USB on a desk: anyone can take it, but without the password, itβs unreadable. This follows standard end-to-end encryption principles
Yes, we store your encrypted data in your atproto repository. *In theory*, if your encryption keys are secure enough, it won't be cracked.
Yes, we store your encrypted data in your atproto repository. *In theory*, if your encryption keys are secure enough, it won't be cracked.
We don't have any better ideas at the moment.
Yes we will!
Thank you for your valuable suggestions!
Account management
sign in with atproto page
Today we launched One Calendar v2.2.0
what's new?
- Login with ATProto
- Store your calendar data in your atproto account repo
- Share event with ATProto
oh thats a bug we will fix later
Here's our GitHub repo link:
github.com/EvanTechDev/...