Conversation

Notices

1. Embed this notice
   Flanker (flanker@decayable.ink)'s status on Friday, 04-Apr-2025 20:00:19 JST Flanker
   ok so im working on an ebooks bot and i'm writing it myself because im ganster as shit but unfortunately im retarded and the best way i could think to not accidentally ddos ryona.agency every time i want to update the list of posts is this. this seems stupid i think.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 04-Apr-2025 20:00:18 JST 

     in reply to
     @Flanker You could maybe record the date of the last post and fetch posts (with reasonable intervals, like 1-2 req/s) until you hit one with a created_at earlier than recorded date. Shouldn't be a problem unless there happen to be some posts out of order. Or do the same with flake IDs like AskGA7mLKPPzGh6uK8 (which while semi-random are still generally sequential).
   • Embed this notice
     Flanker (flanker@decayable.ink)'s status on Friday, 04-Apr-2025 20:08:16 JST Flanker

     in reply to

     • 
     that would require me to know what programming is, unfortunately.
     
     That said, with the way mastodon.py deals with fetching statuses (20 item "pages" all the time every time (unless theres a way to reduce the size or something i haven't seen)), comparing it to like the 40 newest lines in the corpus should hopefully be enough to reduce un-necessary fetches to at most like 2 in the worst case scenario. fwiw i'm only planning to update it like once a month and im def gonna do it manually least i fucked something up lol
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 04-Apr-2025 20:27:54 JST 

     in reply to
     @Flanker I also advice you to make it post unlisted so that it won't clog up the public timeline too much.