Feeling so behind on #pixeldev since I started my job π
Local and Network/Federated Timelines really shouldn't exist if you think about it.
Centralized platforms have solved content discovery and I think it's about time we do too.
Also, pixelfed.social is using 12G of ram just for redis. Seems like I'll have to take the title from pleroma for most ram heavy implementation π #pixeldev
The discover page is taking 14 seconds to load (on pixelfed.social) due to an inefficient SQL query. Refactoring now, times like these I'm glad I run the largest instance so I can identify issues before others have to π
#pixeldev
Just wrapped up my first week at my new job, it went great! Now Iβll be spending a few hours on #pixeldev π
Pixelfed.social 55 minute outage yesterday was caused by low disk space, which we mitigated by moving to a larger server.
Our automated backup service triggered dangerously low disk space which caused other services to fail, had we used S3 for media this would not have happened.
I am prioritizing cloud storage support and it should be released later today. #pixeldev
Verified accounts could work in a local context, especially considering we use usernames and not display names everywhere.
Each instance could set its own criteria for getting verified or disable this. Not sure if I will proceed, what do you think?
Pixelfed now tracks status views for the new discover algorithm (available soon).
We just store the status_id & profile_id so we can display posts you haven't seen yet on Discover. #pixeldev
Working on a new pixelfed related project, having lots of fun!
Can't wait to share more π #pixeldev
Pixelfed DMs are a bit different.
You will only receive direct messages and notifications from users you follow unless you opt-in to public direct messages.
The filtered tab will show messages from users that are muted or that you don't follow.
You can mute DM notifications.
You can customize UI/UX settings.
Full stack developer from π¨π¦
Creator of @pixelfed, admin of https://pixelfed.social