71–80 of 87 posts
Earlier quoted context omitted.
What baby? DNS doesn't have the double spend problem. Why is the blockchain good for this?
The double spend problem for domains is the double domain purchase problem. I claim example.com and you also claim it, who wins?
Sort of on a tangent to the actual content of the page, but what documentation system/CMS is this particular web page UI? It seems very fast and relatively uncluttered for the menu on the left side, content pane, top horizontal menu bar.
No sure I agree on fast. At least on mobile the sidebar has an show/hide slide animation that takes a sizeable fraction of a second. In fact is one of the slowest animations for this I have seen. I disable animations entirely on devices I use where possible. They just waste time and that adds up if you use something regularly.
Great. My map application* has a place review system that was built on Atproto, we don't hold user's reviews, they're public, reusable by others. In case of data loss, replaying the jetstream was not possible. This v2 with history is perfect. * https://cartes.app
Chrome Windows, zoomed in on paris, france. Click the restaurant filter for search. The tab froze, tried multiple times. :3
Google's task is much easier on this one : they only show those who've paid ads at high zoom (well at least, that's what we can guess). We're trying to be exaustive, but it's too much in this case.
Great. My map application* has a place review system that was built on Atproto, we don't hold user's reviews, they're public, reusable by others. In case of data loss, replaying the jetstream was not possible. This v2 with history is perfect. * https://cartes.app
Earlier quoted context omitted.
Whoever buys it first. With a centralised database, this is trivial. Usernames are the same. Who gets @example.bsky.social ? Whoever registers it first. Problem solved.
If you have a central database why do you need atproto?
Earlier quoted context omitted.
If you have a central database why do you need atproto?
To stream dns changes from site owners to dns servers. If you want to change a record, you post the change on atproto. DNS servers everywhere just subscribe to the jetstream. That way anyone can run a fast, local dns server which is kept up to date automatically.
Earlier quoted context omitted.
If you have a central database why do you need atproto?
To stream dns changes from site owners to dns servers. If you want to change a record, you post the change on atproto. DNS servers everywhere just subscribe to the jetstream. That way anyone can run a fast, local dns server which is kept up to date automatically.
Earlier quoted context omitted.
The double spend problem for domains is the double domain purchase problem. I claim example.com and you also claim it, who wins?
I'd like to see DNS ownership combined with the time range and an owner-unique key so you can go to the website you intended to visit rather than whoever happens to own the domain at the moment.