News for hackers. Stuff that matters.

A comment on When imperfect systems are good: Bluesky's lossy timelines. Parent comment

Re:When imperfect systems are good: Bluesky's lossy timelines by nightpool on Wednesday February 19, 2025 @01:40PM (#43105687)
That's the frontend code, it doesn't include the backend API services, which are closed source.
[ Parent | on HN ]
Re:When imperfect systems are good: Bluesky's lossy timelines by half-kh-hacker on Wednesday February 19, 2025 @01:42PM (#43105720)
the backend (the AppView) can be found here:

https://github.com/bluesky-social/atproto/tree/main/packages...

there are various supporting services written in Go as well

https://github.com/bluesky-social/indigo

[ Parent | on HN ]
Re:When imperfect systems are good: Bluesky's lossy timelines by verdverm on Wednesday February 19, 2025 @01:42PM (#43105717)
Which is what I said in the second sentence
[ Parent | on HN ]
Re:When imperfect systems are good: Bluesky's lossy timelines by nightpool on Wednesday February 19, 2025 @01:46PM (#43105773)
AppView is a specific term of art within the Bluesky federation architecture: https://atproto.com/guides/glossary#app-view, you were incorrect in identifying the public frontend repo as the AppView.
[ Parent | on HN ]
Re:When imperfect systems are good: Bluesky's lossy timelines by verdverm on Wednesday February 19, 2025 @01:49PM (#43105802)
A frontend is (can be) part of an App View. It is quite literally the app you view the network through. There can also be headless app views and app views which have no backend
[ Parent | on HN ]
Re:When imperfect systems are good: Bluesky's lossy timelines by half-kh-hacker on Wednesday February 19, 2025 @04:50PM (#43108209)
this is not correct
[ Parent | on HN ]
Re:When imperfect systems are good: Bluesky's lossy timelines by verdverm on Thursday February 20, 2025 @07:37PM (#43122612)
The glossary specifically calls out the UI as part of an app view. Can you explain why it is not according to you?
[ Parent | on HN ]