Pretty decent is what we were aiming for!
-
-
-
And I'm aiming for helping you on that.
-
I'm thinking heavily about implementing the thin server model for fritter soon (https://pfrazee.hashbase.io/blog/achieving-scale …) which I think will do a lot for the experience
-
Couldn't we just increase the degrees-of-freedom we sync with and make Beaker automatically also share those dats?
-
Yes indeed, in fact the server is mainly the same logic as the client (and will share the same code). The purpose of the server is simply to be higher performance and always on, therefore offloading sync from the client and increasing the processing potential
-
If I really nail the design here, the client should be able to gracefully fallback to local sync if the server is down
-
Just dropping a broad idea here: - Set the option for the client to choose how many degrees of freedom he wants to sync. - Have this service to just be a follow-back (like a SSB pub) with a higher degree of freedom. - People who want to be discovered follows the pub.
-
That's not far off from how this will work, though I'm not sure yet whether I'll externalize the config through following. That use of follows is more natural for SSB because the SSB protocol uses the follow graph in its sync protocol. Here, it's not 100% necessary, so not sure
- 1টি আরও উত্তর
নতুন কথা-বার্তা -
-
-
Following you now!
ধন্যবাদ। আপনার সময়রেখাকে আরো ভালো করে তুলতে টুইটার এটিকে ব্যবহার করবে। পূর্বাবস্থায়পূর্বাবস্থায়
-
লোড হতে বেশ কিছুক্ষণ সময় নিচ্ছে।
টুইটার তার ক্ষমতার বাইরে চলে গেছে বা কোনো সাময়িক সমস্যার সম্মুখীন হয়েছে আবার চেষ্টা করুন বা আরও তথ্যের জন্য টুইটারের স্থিতি দেখুন।