41–47 of 47 posts
So, it's not even that the SQL state is distributed, it's that every change to the SQL state has to be "validated" and appended to a blockchain? At a 1M DAU traffic level? How often are blocks/writes written? Who pays for all that data storage? How "decentralized" would it really be, considering the incredibly onerous requirements to run a validator at the target scale?
Earlier quoted context omitted.
This is difficult to handle without some centralized authority. One example I can think of is Aether [1], which has a non-decentralized blacklist for illegal content [2] that they can use to handle these instances. It could also be possible to broadcast some kind of signed take-down message that could be propagated through all of the nodes. If I remember right, Aether said that the centrally hosted json file was need…
Decentralized systems that use append-only logs (which includes but is not limited to blockchain stuff) need the equivalent of a 'git rebase' to purge history. Like lwalton says, this is very difficult to do without centralizing authority, as a rebase is a fork, and so you need the whole community to rebase/fork simultaneously. This is a big deal if all data is in the same place. One approach is to break these logs a…
Earlier quoted context omitted.
> why is extrajudicial punishment allowed? In some cases it is common sense. For instance: a pedophile shouldn't be allowed to be a school teacher.
in that case, there should be a court order that prevents them from exercising such occupations.
What if someone posted false claims about you? Would you like recourse in that event?
Write actions that can take seconds to minutes to validate. This doesn't seem like a trade off any application I can think of would make.
Let's say you implement a Facebook-like social network (think something like Elgg). If you really need the benefits of decentralization, is waiting a few minutes for your post, profile update, file upload, etc. to go through that big of a deal?
Earlier quoted context omitted.
Let's say you implement a Facebook-like social network (think something like Elgg). If you really need the benefits of decentralization, is waiting a few minutes for your post, profile update, file upload, etc. to go through that big of a deal?
Even if you don't need it, people are going to want their posts to go out "now". Seconds of latency is tolerable, but your average person is not going to be happy waiting minutes.
You just have to sell it. Market it as "this decentralized network has delays to ensure dark and addictive patterns don't overrun the network - our network is more than just trying to see who has the most likes in the shortest amount of time."
Earlier quoted context omitted.
Even if you don't need it, people are going to want their posts to go out "now". Seconds of latency is tolerable, but your average person is not going to be happy waiting minutes.
See, in the 90's when everyone was on dial-up, people really did wait minutes for stuff. I waited HOURS for a single MP3. You just have to sell it. Market it as "this decentralized network has delays to ensure dark and addictive patterns don't overrun the network - our network is more than just trying to see who has the most likes in the shortest amount of time."
Earlier quoted context omitted.
Even if you don't need it, people are going to want their posts to go out "now". Seconds of latency is tolerable, but your average person is not going to be happy waiting minutes.
See, in the 90's when everyone was on dial-up, people really did wait minutes for stuff. I waited HOURS for a single MP3. You just have to sell it. Market it as "this decentralized network has delays to ensure dark and addictive patterns don't overrun the network - our network is more than just trying to see who has the most likes in the shortest amount of time."