Notices by Mikoto BSD (mikoto@akko.wtf)
-
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Monday, 28-Oct-2024 03:28:31 JST Mikoto BSD nheko keeps having text jumbled up randomly every now and then, forcing me to restart it to get it back to normal -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Monday, 28-Oct-2024 00:49:04 JST Mikoto BSD more platforms should have custom emoji :maid_nod: -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Monday, 28-Oct-2024 00:48:32 JST Mikoto BSD source: https://logos.fandom.com/wiki/Microsoft_Windows/Logo_Variations -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Saturday, 26-Oct-2024 07:43:16 JST Mikoto BSD some risc v is designer saw the AVX* specs and thought
seems like a good idea to copy their naming conventions
RE: https://mastodon.online/@ezhes_/113349521022612339In conversation from akko.wtf permalink Attachments
-
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Friday, 25-Oct-2024 12:09:40 JST Mikoto BSD https://x.com/death_rouser/status/1846550009254473870 In conversation from akko.wtf permalink Attachments
-
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Friday, 25-Oct-2024 09:50:29 JST Mikoto BSD In conversation from gnusocial.jp permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Friday, 25-Oct-2024 08:57:44 JST Mikoto BSD @ezio slackware In conversation from gnusocial.jp permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Friday, 25-Oct-2024 03:33:11 JST Mikoto BSD which old tech do you wish didn't die or fade into obscurity? In conversation from akko.wtf permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 22:26:01 JST Mikoto BSD awaken In conversation from akko.wtf permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 10:50:11 JST Mikoto BSD that's it, no more yuri shipping in those 5 countries In conversation from akko.wtf permalink Attachments
-
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 00:45:13 JST Mikoto BSD @sun @kura I mean part of the problem with indices is that it makes inserts slower which has been a major problem for me in the past (though it's been better for me after I helped the akkoma project identify and remove unused ones)
but ultimately the problem with storing full json is that there's a lot of redundant data in there which adds up quite quicklyIn conversation from gnusocial.jp permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 00:45:12 JST Mikoto BSD @sun @kura add things like edits, deletes, etc and the O2N MVCC model that postgres uses and you can see it can go out of control if you aren't careful In conversation from akko.wtf permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 00:45:11 JST Mikoto BSD @kura @sun the other major problem I can tell is that pleroma loves to keep transient activities and other similar things around even if they won't be needed after a short amount of time In conversation from gnusocial.jp permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 00:23:07 JST Mikoto BSD @sun @kura it does still have jsob objects in their db, but it's only for things like certain config options or their minigames In conversation from akko.wtf permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 00:23:07 JST Mikoto BSD @sun @kura it's been a while since I worked with the codebase so I might not be up to date with their current practices, but I do remember they do normalize posts and recipients years ago In conversation from gnusocial.jp permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 00:17:04 JST Mikoto BSD @kura it's the classic "db rot" thing. Pleroma has (from what I can tell) has these issues with its db design:
- Stores full JSON objects instead of normalizing them
- Stores every activity it receives, including Delete and Tombstone
- Doesn't really have any mechanism of auto-expiring stuff. There is an MRF that can auto expire objects globally, but I don't really like that solution.In conversation from akko.wtf permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Thursday, 24-Oct-2024 00:17:03 JST Mikoto BSD @kura also there's been a tendency to slap on indices whenever there's a db-related performance issue, which ends up causing the database size to bloat up and is really only a bandaid solution In conversation from gnusocial.jp permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Wednesday, 23-Oct-2024 12:11:32 JST Mikoto BSD man does the akkoma schema require tons of garbage collecting to keep it from going out of control, some of which isn't made into tasks In conversation from akko.wtf permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Wednesday, 23-Oct-2024 01:11:44 JST Mikoto BSD Ok think I'm gonna use moshidon instead of subway tooter from now on, this feels much more polished In conversation from akko.wtf permalink -
Embed this notice
Mikoto BSD (mikoto@akko.wtf)'s status on Wednesday, 23-Oct-2024 01:05:19 JST Mikoto BSD lol one of the pictures on the moshidon google play store page is the wetdry.world timeline In conversation from akko.wtf permalink