#TIl about reddit alternative #piefed
Just Flask with sprinklings of vanilla JS and htmx.
https://join.piefed.social/2024/01/22/an-introduction-to-the-piefed-codebase/
PieFed · An introduction to the PieFed codebase - PieFed
More from 
piefedadmin
Recent searches
Search options
#linkaggregation
0 posts0 participants0 posts today
Ab sofort hat mein 
Federated link aggregators should not own individual topics. Topics should belong to the entire fedi.
Instance owned topics is just another form of centralization.
We should not only discourage topic diaspora (e.g., a "gaming" topic on beehaw is separate from a gaming topic on another instance) but engineer solutions to *allow* and default unification of content by topic across the fedi for link aggregation (but not force this).
(De)federation then becomes how we keep topics safe for our communities: blocking posts and comments from demonstrably unsafe instances.
This is a CAP distributed system problem. My instincts say that federated link aggregation is a different enough problem from federated blogging (mastodon) that we need federated instances to share content via a consensus algorithm and not the mastodon style of federation.
I wonder about the practicalities of making this work in the truly heterogenous system of the #fediverse.
Perhaps by having the federation members/instances themselves share capability and capacity metadata with the cluster so as to load balance intelligently? The alternative could be an unintentional DDOS due to a massive instance going offline, shedding traffic to instances too small to handle the load.
which one do you prefer more: #kbin, #lemmy or some other #Fediverse #LinkAggregator? What are their strengths and weaknesses? #LinkAggregator #LinkAggregation
haxadecimal 
She's got LAGs
Knows how to use them
