i don't think so - the most important property of federation is that the experience still works even if any particular entity goes away or tries to stop it. the feedgen is displayed by the appview, so i don't think it gets there (but it's good! and in the right direction!)
1 6Samuel
@samuel.fm
sure, the main appview is the entrypoint in a sense - it's the backend to the app you're using. but in a multi-appview world you essentially have a constellation of mini-appviews to pull lenses of the network from
bsky.app/profile/samu...
Samuel@samuel.fm· 3 Nov 2024so, imo the network (with multiple AppViews in play) looks like this. when you use a client, you ask an AppView to give you an opinionated view of the whole network. It acts as a cache in front of any number of hosts, which unlocks stuff like global search and accurate like counts (wild, right!)
v buckenhamsure - in a multi-appview world, then the feedgens give more choice and resilience to the experience. but they aren't a replacement for multiple (meaningfully separate) appviews, in terms of choice and resilience.
1 1v buckenhami don't know how idiosyncratic my definition of "federated" is - for me it is: the network is operated by a variety of entities who have differing aims and motivations, and if any of them go away then the network as a whole still meaningfully exists.
1 2
imaxThat pretty much is the well-established meaning of the word "federated" in computer science.
Natanael, Tech janitorI describe this as cross-layer federation between components, versus the peer-like federation between monoliths in Mastodon
1 3
Dario Castañé 🏴☠️I like the concept "cross-layer federation". It does capture the idea that the federated actors aren't full nodes/peers but a constellation of different actors, each one serving a specific purpose.
From the gigantic AppView and relays, to the smaller labelers and feeds, through different-sized PDS.
1