Content
@
https://opensea.io/collection/neynar-1
0 reply
0 recast
0 reaction
artlu š©
@artlu
strong opinion, weakly held: client devs should not run Hubs (they should run a Replicator) - Hubs are expensive - point Replicator to nemes, StandardCrypto, Neynar - Replicator is copy of all (verified) data, without overhead of CRDT, syncing, network spam - SQL is more flexible+expressive than Hub HTTP API or gRPC
1 reply
0 recast
2 reactions
artlu š©
@artlu
@alexgrover.eth @haardikkk and @rish comments have convinced me to turn my perspective 180 degrees
1 reply
0 recast
1 reaction
artlu š©
@artlu
tagging @vrypan.eth for more obs about Hubs utility. Reading from Replicator, writing to Hubs may result in unavoidable async nastiness
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
1. It's ok, if you don't mind about censorship resistance and self-sovereignty. 2. Replicator is ok for reads, but you will need one more integration to change the state. 3. "Async nastiness" is the beauty of decentralized hubs: at any given point in time, most hubs are not 100% in sync, but they eventually converge.
2 replies
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
I rushed to reply, and I have to clarify: If you have a fc client that requires me to install a backend to run it on my own, that's fine with me. So, if I need a replicator, or even your own custom backend, great, as long as I can install it on my own server.
1 reply
0 recast
0 reaction
alex
@alexgrover.eth
How many people do you think would be willing to set something up like that? Given the current scale of FC I think most apps are better served building more compelling use cases to bring in new users
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Answer: https://freedomhouse.org/explore-the-map?type=fotn&year=2023 That's not to say that we should all work to help people who would need this type of feature. But there's value in raising the issue, and having it in mind when we make decisions as devs.
1 reply
0 recast
0 reaction
