Posts by efertone@slippy.xyz
 (DIR) Post #Aad4VNg3QnTHf3O6aW by efertone@slippy.xyz
       2023-10-10T12:25:53.502Z
       
       0 likes, 0 repeats
       
       It's mentioned in the changelog tho:アップデートを行うと、タイムラインが一時的にリセットされますGoogle Translate: Updating will temporarily reset your timeline
       
 (DIR) Post #AadfQFEn4y6MLG388e by efertone@slippy.xyz
       2023-10-10T20:55:52.884Z
       
       1 likes, 0 repeats
       
       @emma@niscii.xyz I would like to notei restored the db from a backup that i did just before the update, and then undid the update on gitYou can't hold back forever, one day you have to update, it's not a bug, it's in the release notes, it will not be fixed. I see no reasons to roll back and wait, yes it's painful, but you have to do it one day and it will be painful that day too, maybe even more applying more then one patches.
       
 (DIR) Post #AadfWQHAx2a6JZ6wWu by efertone@slippy.xyz
       2023-10-10T20:57:02.762Z
       
       1 likes, 0 repeats
       
       @emma@niscii.xyz @Cocoa@mocha.hoto.rocks @meowski@fluf.club @verita84_uwu@poster.place @miscbrains@misc.brainsoap.net you don't, it's redis 😆 just roll with it.
       
 (DIR) Post #AadfhCQqlNEYZ0m6Lo by efertone@slippy.xyz
       2023-10-10T20:58:36.079Z
       
       0 likes, 0 repeats
       
       @emma@niscii.xyz wasn't the last update the one said "your notif will be reset, deal with it"? There was an update where we lost notifs and it was known from release note.
       
 (DIR) Post #Aadg4hMzu2sNAzB680 by efertone@slippy.xyz
       2023-10-10T21:03:16.796Z
       
       0 likes, 0 repeats
       
       It's so annoying, I don't want to block the whole @seal.cafe instance, but I get reports from users all the time about @yesbot@seal.cafe (it's annoying as hell) 😞 So whoever manages that bot, go and f* yourself, thank you.
       
 (DIR) Post #Aadg8LkuCsHlIa6Nlo by efertone@slippy.xyz
       2023-10-10T21:03:37.899Z
       
       0 likes, 0 repeats
       
       @emma@niscii.xyz you will see future notes
       
 (DIR) Post #AadgC5zSlNmRYuhHfc by efertone@slippy.xyz
       2023-10-10T21:04:31.957Z
       
       1 likes, 0 repeats
       
       @emma@niscii.xyz I agree with you, but I can't do much about it, and it's not like it goes forever and you never see them back.
       
 (DIR) Post #AadgJyJBCzVs3Nfv9c by efertone@slippy.xyz
       2023-10-10T21:05:34.701Z
       
       1 likes, 0 repeats
       
       @emma@niscii.xyz Oh and now it loads previous notes too, when I checked after update it was empty everywhere :(
       
 (DIR) Post #AazZFWoc2adAwWYBo8 by efertone@slippy.xyz
       2023-10-21T09:20:37.721Z
       
       1 likes, 0 repeats
       
       @emma@niscii.xyz That's gorgeous ❤️ (but agree smaller would look a bit more "natural", now it's feels a bit more like a flower)
       
 (DIR) Post #Ab1WIcAifdLQsWaggC by efertone@slippy.xyz
       2023-10-22T08:19:02.128Z
       
       1 likes, 1 repeats
       
       Traceback (most recent call last):  File "/home/efertone/slippy-maintenance/clean-old-remote-files.py", line 57, in     files = list_old_files()  File "/home/efertone/slippy-maintenance/clean-old-remote-files.py", line 40, in list_old_files    cursor.execute(query)psycopg2.errors.UndefinedColumn: column "createdAt" does not existLINE 2: select "id", "createdAt", "userHost", "accessKey", "thumbnai...                     ^ffs, they removed the createdAt column from the table, i checked and  they replaced it with nothing :( we don't know how old is a file from the database so I can't clean up old files to prevent growing it to over TBs.#misskey @syuilo@misskey.io  :(
       
 (DIR) Post #Ab1WLk8HWsfMR8wToW by efertone@slippy.xyz
       2023-10-22T08:44:40.640Z
       
       0 likes, 0 repeats
       
       @syuilo@misskey.io That would require to select all rows and manually parse the aid timestamp part and compare it.Previously it was a simple:select "id", "createdAt", "userHost", "accessKey", "thumbnailAccessKey"    from drive_file    where "userHost" != '' and "createdAt" < NOW() - INTERVAL '2 months'    order by "createdAt" descand I made an API call to all of those files to be deleted.With parsing from AID i would have to select all, parse aid and make api call if required.misskey=> select count(1) from drive_file;  count--------- 1654924(1 row)with the simple query on timestamp the result on the select was around 15-20k running daily.
       
 (DIR) Post #Ab1WLlsl1ZR7rZh6tU by efertone@slippy.xyz
       2023-10-22T09:04:16.856Z
       
       1 likes, 0 repeats
       
       @syuilo@misskey.io I don't manipulate the database manually :P That's why I delete with the API call, I just query it and that's read only.I'm not going to create a github issue as it will never be resolved really (yes I lost all hope in github issues on the repo already), and recently every version breaks something and it feels like "compatibility" as a word doesn't exist anymore. :(As a user I love misskey, but as a maintainer in the last half a year or a year, it's really a pain in the ass. And I'm not the only one because in the last few months more and more people had issues with upgrades, config changes.
       
 (DIR) Post #Ab1Ym6MngZFUpfQhf6 by efertone@slippy.xyz
       2023-10-22T09:19:56.835Z
       
       1 likes, 0 repeats
       
       @Maholmire@shitpost.cloud @emma@niscii.xyz trying to figure out how the hell typescript/japascript toString() with radix works. I hoped it's a simple "int to string with baseN" but no, numpy.base_repr(t, base=32) gives a different result. I guess I'll be super lazy and just ask node through a Popen call ​:boomer_laugh:​
       
 (DIR) Post #Ab1tNK2xmhVN3fB0nA by efertone@slippy.xyz
       2023-10-22T13:15:21.460Z
       
       1 likes, 0 repeats
       
       @Maholmire@shitpost.cloud @emma@niscii.xyz Well I was stupid, it's base=36 ​:picard_facepalm:​and done, here is the patched script that uses ID: https://gitea.code-infection.com/efertone/snippets/commit/e845bd41f08906928125b30577639d868d273dfe(it needs numpy, so you may need to install that with pip or your package manager)
       
 (DIR) Post #Ab1txdVUuQpnq0q5Hk by efertone@slippy.xyz
       2023-10-22T13:29:44.397Z
       
       1 likes, 0 repeats
       
       @emma@niscii.xyz I assume yes. They removed createdAt from notes too :/
       
 (DIR) Post #Ac68k8avPCDpr3KXke by efertone@slippy.xyz
       2023-11-23T10:30:21.203Z
       
       1 likes, 0 repeats
       
       @protonmail@mastodon.social Linux please, the only feature prevents me to drop my Syncthing.
       
 (DIR) Post #AchpFYe6sMLR9TF95k by efertone@slippy.xyz
       2023-12-11T16:36:27.908Z
       
       0 likes, 0 repeats
       
       fancy new shoelaces
       
 (DIR) Post #AcuNiVoFLJqaa0nZ68 by efertone@slippy.xyz
       2023-12-17T18:02:22.325Z
       
       0 likes, 1 repeats
       
       
       
 (DIR) Post #Ad7Qp1GVsigjlTCLzM by efertone@slippy.xyz
       2023-12-24T01:17:29.946Z
       
       0 likes, 1 repeats
       
       With #Misskey 2023.12.0 The emoji settings to be pinned and displayed in the emoji picker have been divided into "for reactions" and "for emoji input". The previous settings are used as "for reactions".Impact:As a result, you may feel that the pinned emoji in the emoji picker displayed from the submission form has been reset (as the newly established "Pin (General)" setting will be used).To return pinned emojis for posts to their pre-update state, follow the steps below.- Go to the "Settings" menu and select the "Emoji Picker" tab.- Select the "Pinning (General)" tab.- You can return to the state before the update by pressing the "Overwrite from reaction settings" button.Source: Google Translate from release note: https://github.com/misskey-dev/misskey/releases/tag/2023.12.0
       
 (DIR) Post #AdFpyVl5vi5J3wnx4a by efertone@slippy.xyz
       2023-12-27T23:45:54.031Z
       
       0 likes, 1 repeats
       
       Heads up, #Misskey 2023.12.1 has some security fixes, but they are not marked as security fix in the patch notes, but I think they should be and they feel serious issue not just a  "yeah put it at the end of the list" kind of bugs:Fix: サードパーティアプリケーションがWebsocket APIに無条件にアクセスできる問題を修正Fix: サードパーティアプリケーションがユーザーの許可なしに非公開の情報を見ることができる問題を修正Google Translate:Fix: Fixed an issue where third-party applications could access the Websocket API unconditionally.Fix: Fixed an issue where third-party applications could view non-public information without user permissionSo if I understand correctly, everyone should apply this patch asap.There is a 2023.12.2 too, but that's only docs and docker related.