Context is this toot, which I dunno if it's still accurate since it was 3 months ago. But you can see the _resizeComponent() call in there, even if it's not the majority of the trace. https://nulled.red/@flussence/102122451948261638
@notwa LineageOS doesn't wipe after an update, correct. Sometimes though you may need to update the firmware. In my experience though you can just install the OxygenOS update zip immediately followed by the LineageOS update zip, then it works.
In theory you can fix this by using a <div> instead of a <textarea>. Then you can use CSS to actually make it fit its content. Some web-based text boxes use this solution.
The problem is that this comes with huge accessibility problems - now you need to make the <div> act exactly like a <textarea> in every way, including for screen readers, copy-paste input, etc. Theoretically it's possible, but it would be a ton of work to get everything right.
Part of the reason there is input lag in both Mastodon and Pinafore is because of the auto-resizing textbox. Believe it or not, there is no way in HTML/CSS to make a <textarea> that automatically expands or contracts to fit the content. (Believe me, I've looked.)
The best solutions are all JavaScript-based, which requires recalculating layout every time a character changes (e.g. you press a key). In Pinafore I mitigate this by syncing layouts to frames, but it's not a perfect solution.
My only major critique of LineageOS is that I still think it's largely inaccessible to non-techies. But it definitely works well for me as my daily driver (on a OnePlus 5T).
And of course, Pinafore has a "wellness" setting where you can just turn off boost/fav/follower counts entirely. I don't personally use this feature, though.
I've always liked Mastodon's design where the likes/boosts aren't shown until you click a toot. It helps me focus on reading the content without immediately trying to gauge its social approval.
The part about open-source burnout really struck close to home for me. Sometimes I feel like you put something out there that solves your problem, but then you get a bunch of issues/PRs solving someone else's problem, and after a while it's hard to muster the will to care.
The best projects are indeed those that are tiny and maybe only matter to a small group of people. That's why I like working on Pinafore these days more than databases, libraries, etc.
@rra Thanks for sharing your tips! Cleaning the yarn cache is a helpful one for me (especially since I run multiple instances on one server).
Also: switching from local media storage to an S3-compatible server was a big help for me. Disk doesn't grow nearly as fast now (just the Postgres database, not the media files).
I'm also curious how other #MastoAdmins are dealing with the memory growth. I have to restart every month or so, or it reaches my server's max of 8GB (running 3 instances).
I know there are quite some #mastoadmin struggling with the disk space usage of the mastodon instance they maintain. The issue is not acknowledged enough and there are very few ways you can mitigate this using the official mastodon tools etc. Even better, often the proposed 'solution' is to 'get more disk space lol'.
Here's a compilation of recipes on how we try to deal with this for post.lurk.org as we learn by doing.
Windows Performance Analyzer is actually an amazing tool, and something I miss from my days at Microsoft. Also I'm not surprised to see that right-clicking the taskbar is super slow in Windows. Maybe it's just my bias, but every OS interaction just *feels* slow to me on Windows, which is partly why I switched to Ubuntu.
websites: if you click "keep me logged in", it will never work ads/trackers: know exactly who you are at all times with zero effort required on your part