• 0 Posts
  • 95 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle







  • according to the lemmy docs, it’s all done in the same way, through the 3 dots button on posts and comments.

    however, i think the term used is different: sticky instead of pin. the screenshot on the docs show the 3 dots button on a comment, so no sticky button there. perhaps someone who is actually a moderator here can provide you with screenshots if the 3 dots button for posts (just below the title, in between title and contents) doesn’t work for you.

    scheduling on the other hand, is done with a bot, contact @Naomikho for that.










  • don’t scare our admins 😱

    monyet already has a dev instance, so they can import the db from the main instance there, and do the db migrations to see if that’ll succeed.

    precautionary measures can be taken on the dev instance so it doesn’t attempt to federate with all the data from here.

    i can think of (for testing out db migrations on the dev instance):

    • run lemmy_server with the --disable-scheduled-tasks cli flag, which will prevent background federation tasks from running (so federation events will only be triggered by actual interaction, like posting, voting, subscribing, and of course such things should not be done on the dev instance)

    • if that’s still not enough and we want to be extra sure the dev instance doesn’t federate with data from over here, then just block outgoing http/https connections at the firewall while doing the db migrations try-out (also don’t run lemmy-ui and just watch the docker logs for it to say migrations completed successfully)

    i think the lemmy.zip admins said they’re still trying to work out a way to spin a dev instance on a dedicated server, but monyet already has a dev instance, so the db migrations can be tried first to ensure safety.


  • there will be at least 5-10 minutes of downtime for db migrations though (more if the db size is huge). of course, after the long migrations the db size is reported to shrink significantly.

    anyway, there’s already been at least 2 easily triggered/discoverable bugs:

    • view context for comments does not work properly (i heard it may even crash jerboa)
    • all software versions in the instances list are displayed as 2.0

    hopefully they will release a 0.18.4 quickly with fixes for that.