🥳 🥳 🥳 ssb-postgres module is out and it's here🥳 🥳 🥳
This is a part of fixing some issues mentioned here or there:
fix any scalability issues at server side ?
to fix multiple device issue, i suggest this workflow:
before publish, i createHistorystream(self.id,self.index.last) so I'm always up to date regarding sequence
flowchart TB
client --> relay
relay --> client
Planning to use this with delog + ssb-postgres
Would fix also the data backup issue (mnemonic i/o as in delog solve the backup issue)
Regarding the key rotation issue, I wonder if that could not be adressed with a webfinger RFC 7033 thing, or maybe with something like described in fep-c-390
That would also adress the "mynameisanb64keyissue" :
sequenceDiagram
actor Bob
actor alice
Bob ->> Alice: What is your identifier?
Alice -->> Bob: it's @alice@alicefamily.com
Bob ->> Alice: You can also follow me at @bob@ssbfans.com
Pseudonym verification is provided by posting a simple request to the server associated with the alias for verification.
🥳 🥳 🥳
ssb-postgresmodule is out and it's here🥳 🥳 🥳 This is a part of fixing some issues mentioned here or there:before publish, i createHistorystream(self.id,self.index.last) so I'm always up to date regarding sequence
Planning to use this with
delog+ssb-postgresWould fix also the data backup issue (mnemonic i/o as in delog solve the backup issue)
Regarding the key rotation issue, I wonder if that could not be adressed with a webfinger RFC 7033 thing, or maybe with something like described in fep-c-390
That would also adress the "mynameisanb64keyissue" :
Pseudonym verification is provided by posting a simple request to the server associated with the alias for verification.
Would be very please to have your feedback regarding thoses issues/solutions.
Best regards
Emmanuel