amark on master
Improve user.recall() Wrap JSO… improve sea.js Removed the sma… Fix user.create() BEFORE: - us… and 5 more (compare)
[D] fade: Without authentication and between two instances, I do see changes being written to local storage (and also replicated as properties are set), so that's cool.
Digging into user.create, it seems like the act.a callback isn't being fired, unsure if this is deferred based off of replication, but my breakpoints aren't being hit (called from
.ok, from SEA::User.create
root.get('~@'+alias).once(act.a);, I guess, not familiar with the code obviously.. (running from master)
osslshim that had problems, that is all WebCrypto now. Or another issue is build steps sometimes try to build the WebCrypto shims into the browser which already has WebCrypto so you need to tell them to ignore that - there's a couple webpack configs out there that help with this. Could that be it? Or are you doing all things plain script tags no build?
"so therefore it is a string, not a JS object? Also, internally I'm getting rid of
node.isin rewrite 😛 pretty much all the utility functions are getting thrown out to save few bytes of space - however, I'll provide them all "again" as a module/library you can include, so if you use them, just add that and things shouldn't break.
520, I was moving apartments last week and haven't been able to touch/look/fix that at all, which is embarrassing cause that means the tutorial everybody runs thru is ... failing. Meanwhile, can you rollback to maybe 2019? (2019 has some storage bugs at scale, but more reliable user system for testing) 2020 is live experimental migrations :/ maybe I shouldn't do that in-prod >.< thanks for having patience, this is totally my fault, sorry for a bad first experience.
[D] fade: <@178314946201780224> Thanks for the follow-up, I'll pop back to an older rev and see if that clears it up. As long as the API docs are still mostly relevant, I don't see a problem with that at all.
Thanks for the welcome! I found GUN from a stack overflow post, was looking for an orbitdb alternative (which I was having trouble implementing due to broken components/docs/incompatibility/etc). I like the direction of the API and, tbh, my little dive into the code today was a positive experience. I'm still unclear on some things but look forward to filling the gap. Project-wise, I'm hoping the centralized web dies and decentralized databases are an integral component to that end; the fediverse is nice but the massive single point of failure that are the domain registries is problematic, so getting away from that is my goal.