downshift
@downshift.eth
lately, i’ve been quietly working on data infra for dealing with flaky data sources (like Farcaster data and blockchain data…this isn’t a dig at Farcaster by any means; it’s just the nature of consensus-based protocols in general) this stuff is non-trivial to get right because intermittent and complete failures of data providers are guaranteed, especially in times of massive usage and network congestion we are and will continue experiencing robust data access patterns and thorough fallback strategies are absolutely essential to have any chance of creating reliable systems in these sorts of environments, especially if your goal is to minimize latencies
6 replies
18 recasts
74 reactions
alex
@proxystudio.eth
its actually a huge deal, getting my first big boy taste of it today just checking data that is easy to pull from the chain against data that is simply too hard to get from the feed. need to bring these realms closer together, extremely important
3 replies
3 recasts
20 reactions
big tone 🎩🧾
@bigtone.eth
curious if either of you have considered /arweave 👀 cc @downshift.eth
1 reply
0 recast
2 reactions
downshift
@downshift.eth
right up my alley! followed 🫡
1 reply
0 recast
5 reactions
alex
@proxystudio.eth
would be curious to learn more @bigtone.eth obviously familiar in general but not specifics
1 reply
0 recast
3 reactions
big tone 🎩🧾
@bigtone.eth
tl;dr back to @downshift.eth’s OP - Arweave data is immutable because it incentivizes replication. uploaded data is chunked & hashed, ensuring data integrity. data can be retrieved through the nodes directly but is more easily retrieved through gateways that can index/cache data that is most important to that app/community
1 reply
1 recast
4 reactions
big tone 🎩🧾
@bigtone.eth
sent you both DMs if you want to chat more about Arweave, no pressure 🫂 @proxystudio.eth @downshift.eth
0 reply
0 recast
2 reactions
