When imperfect systems are good: Bluesky's lossy timelines
1–10 of 315 posts
Re: When imperfect systems are good: Bluesky's lossy timelines
#2Re: When imperfect systems are good: Bluesky's lossy timelines
#3Note that all of this reflects design decisions on Bluesky's closed-source "AppView" server—any federated servers interacting with Bluesky would need to construct their own timelines, and do not get the benefit of the work described here.
Another notable component that is closed source is the discovery feed generator, where at least there is some reason.
Re: When imperfect systems are good: Bluesky's lossy timelines
#4[stub for offtopicness]
Re: When imperfect systems are good: Bluesky's lossy timelines
#5Re: When imperfect systems are good: Bluesky's lossy timelines
#6[stub for offtopicness]
Re: When imperfect systems are good: Bluesky's lossy timelines
#7[stub for offtopicness]
I don’t understand the infatuation with blue sky. The minute they need money it’ll go the way of the Reddit and twitter.
Re: When imperfect systems are good: Bluesky's lossy timelines
#8Re: When imperfect systems are good: Bluesky's lossy timelines
#9Re: When imperfect systems are good: Bluesky's lossy timelines
#10Note that all of this reflects design decisions on Bluesky's closed-source "AppView" server—any federated servers interacting with Bluesky would need to construct their own timelines, and do not get the benefit of the work described here.
What reason does Bluesky give for not opening up their AppView code? Another notable component that is closed source is the discovery feed generator, where at least there is some reason.
if they gave it away (which used to be unfeasible until the digital era) they feel they’re loosing their valuable effort which they’re wont on concentrating, not diluting.