nostr:nprofile1qqsyt3qly8su7u2l5mvu5g9cuqp22axm0w6fa9hw3xp5cek6c4zxk7sprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy28wumn8ghj7un9d3shjtnwdaehgu3wvfnszxnhwden5te0dehhxarj9ehhyctwvajhq6tvdshxgetkqyw8wumn8ghj7atwd9mx2unnv5hxummnw3exjcmg9ekxzmnylwag87 So why does flycat has this platform.twiiter thing?
Also, why cookies? So Flycat is not a pure client side application?
Does it mean that Flycat also stores my events in private servers in a non-relay way?
1. flycat use Next.js framework and host it on vercel. almost everything is client rendering, excecpt for two things: (1. we render article title in server-side so when you share url link of long-form, other people can see the url's title there is no way to do this on client-side. (2. long-form article RSS api, it is also provided in nextjs server-side 2. as for the cookies/platform.twiiter, I once asked a frontend to do twitter url embed rendering I guess it is related to that 3. of course not. I don't even have time to store events on localStorage to help improve the performance. and btw, it is all open-source so feel free to check the code https://github.com/digi-monkey/flycat-web
flycat wrap async iterator on websocket and use it to fetch event from relay, mostly like all the nostr-sdk do, nothing special. but there is indeed one difference, which is that flycat relies on shared-worker to fetch events from relays, so if you open multiple tabs/page in the browser, each page/tabs still use one single connection pool to data
these questions are good for our saturday talk hahahahhahahaha nostr:npub1ghzp7g0peac4lfkeegst3cqz546dk7a5n6twazvrf3nd432yddaqa3qtwq be prepared!
Cookie has a bad reputation for being used to track users.
it may comes from the embed tweet rendering function as I say before. I will take sometime to investigate it later. We didn't wrote codes to try tracking users and it is all open source.
