Vincent Cloutier @vincent@librem.one

Looks like all the time I spent this week optimising bird.makeup was useful: we managed to hit the performance target of processing every account at least once every hour.

3749 twitter accounts followed by 1985 fediverse users, and with so much space to grow now!

@sandhu mastodon.social banned bird.makeup. They have a policy that doesn't allow forwarders from other networks

@smallsco No problem! I just did the most frequent queries, so it's still leaking, just way more slowly

We just crossed 1900 users on bird.makeup 😲

Really excited about how far I can take this project this year!

@DevWouter @smallsco Thanks for the compliment! But the credit goes to @BirdsiteLIVE .

I think I figured it out. I took a memory dump, and noticed large allocation related to SQL queries. When I removed Dapper and used vanilla npgsql the problem when away. It's really not obvious to me what was happening there, but it might be related to your number 1

@condalmo That could work, thanks! If someone post again, it will break a test, but that looks good enough

Ok I have a weird request to help me build bird.makeup:

Do you know twitter accounts of dead people, ideally famous? They have to not be taken over by someone else too.

I'm using them for integration testing, and I only have kobebryant right now

Anyone working on a equivalent of Yo for the fediverse?

https://en.wikipedia.org/wiki/Yo_(app)

@smallsco Yeah, there is a memory leak somewhere... I'm hunting for it!

In the same vein, I'm thinking of giving priority to the accounts above, so that they are always posting to the fediverse in a timely fashion, at the expense of smaller account.

The main bottleneck I have right now is fetching tweets, but not posting them, so if you follow the accounts that are the most popular, it won't slow down things at all 👇

@jay I would recommend having a whitelist at your reverse proxy that only allows for your mastodon instance's IP.

Also whitelist for accounts are probably going away eventually