• 6 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: December 1st, 2023

help-circle









  • I don’t think Lemmy or Mastodon would be a good place to start necessarily. Don’t be discouraged, I just mean that I think this should be something separate, like a library,

    True. I meant suggesting this idea for generally any website that uses tagging. Will update post to show this better.

    As a code library it could be maintained elsewhere and let these folks keep working on their projects.

    We would need a group like the Wiki Foundation to set this up. Though I wouldn’t know how to pitch this.




  • That is more of an argument involving the implementation of tags in general within the federation. But to answer your question:

    Let’s say a group of people were to make a post on Mastodon with the tag #girls_night. How will all instances agree on the tag being correct?

    The simple answer is they won’t. If a tag is contentious, it will be like any other drama between instances.

    It’s the same for implementing tag hierarchy. Let’s say there is a default setup. Then if a tag or a tree of tags is contentious, each instance can include or exclude as they see fit.


  • Two new tables for “tags” would be required. One for instance wide tags and one for community tags.

    a curated list of tags users can attach to their posts. The list of tags can be maintained by both admins and moderators allowing for each community to tailor tags to their specific needs.

    It’s not what I was suggesting, but this should definitely be implemented for Lemmy.

    I’m talking about how some tags should directly relate to one another, and how this should not always be the case in vice-versa. The system I’m suggesting is less useful when you limit the scope of tags (as the RFC does), but you can’t really do that for user-centric websites like Mastodon.

    I think I’ll make an edit to clarify this in post.



  • Actual@programming.devOPtoLinux@lemmy.mlHelp on BTRFS setup
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 months ago

    “subvolume - cannot be snapshotted if it contains any active swapfiles”

    Make a subvolume only for the swapfile.

    has a chance to fragment

    This is true for all files. Is it a bigger problem for swap?

    has issues with hibernation (that I’ve personally encountered multiple times)

    This one I can’t refute. How long ago did you have these issues?