Now that Pawb.Social has forked Lemmy, I thought it would be appropriate to go ahead and compile a list of changes or additions that have been suggested, or that have been spotted by others or myself. This is hardly a comprehensive list, and down below will be two comments by me, one for changes to back-end changes or additions and one for the front-end suggestions as well.

A quick note before I start

One important thing I do want to stress is that any changes or additions made should not render our fork incompatible with other Lemmy instances, the apps that allows for easy usage of Lemmy (Jerboa, Thunder, etc), nor cause issues for interacting with, or interactions from, the rest of the Fediverse. To take a quote from Linux Kernel development: Don’t Break Userspace!

Now, let me specify for any who aren’t in the know about the differences between back-end and -front-end are:

  • Front-end: focuses on the user interface, designing the visual elements, and ultimately the UI elements that a user will interact with on the web page.

  • Back-end: deals with the server-side functionality, handling data processing, storage, and communication with databases and external systems (The rest of the Fediverse) using server-side programming languages and frameworks. For Lemmy, this is done with the Rust language.

Now, with that summary done, here is a (still WiP) list of changes:

Back-end

  • Addition: Individual community blocking (as opposed to the current instance and user-only blocking).
  • Addition: Ability to follow entire instance (or at least follow all communities on an instance).
  • Addition: Allow for individuals to block instances and communities, instead of requiring instance-wide action to block them.
  • Addition: Give instance admins better moderation tools (hashed IP address, etc. Needs to be GDPR compliant)
  • Change: Better support for automatically linking other communities (and instances) back to your primary instance for easier following and interaction.
  • Change: Better cross-compatibility between Lemmy and the Mastodon/Pleroma side of the Fediverse.
  • Change: Better cross-compatibility with KBin.
  • More to come

Back-end & Front-end

(For things that will require changes on both ends to function properly)

  • Addition: Post flaring - To allow for better post management, sorting, viewing, and moderation.
  • Addition: Ability to sort communities into groups (similar to multireddit).
  • Addition: 2FA during login/sensitive actions like password changes.
  • Addition: Mark servers and people as “friends” so they display a marker by their name elsewhere.
  • Addition: Better nsfw post handling, more specific viewing settings, etc.
  • Addition: Adding notes to users (for moderation purposes)

Front-end

  • Addition: Add more themes/theming support to the UI.
  • Addition: Add better support for widescreen displays.
  • Addition: Ability to pick a default sorting method (perhaps per community).
  • Change: Refresh and organize some of the UI elements for Lemmy (somethings are just a bit outdated looking…).
  • Change: Alter donation button at the top to point to the donation portal for the/an instance (this should be the default tbh, the prominent button shouldn’t direct to the Lemmy devs to begin with…)
  • Change: Move all information about Lemmy and the Lemmy devs to one, out of the way location, potentially as a citation in the footer.
  • Change: Add link pointing to the GitHub fork for Pawb.Social
  • More to come.

Please see below for the two threads to add your own thoughts or comments on things you want added, changed, or even removed. All comments and thoughts are welcomed!> ability to sort communities into groups (similar to multireddit).

    •  Sev   ( @SevYote@pawb.social ) 
      4•1 year ago

      Adding notes to users (for moderation purposes)

      Honestly would be cool if that could be done for anybody, not just admins / mods, like Reddit with RES. It lets you add something sort of like a flair to any user that only you can see. You can pick from a list of font colors and just add a short thing, it’s very handy.

    •  KoboldCoterie   ( @KoboldCoterie@pawb.social ) 
      4•1 year ago

      Addition: Allow for individuals to block instances and communities, instead of requiring instance-wide action to block them.

      Don’t we already have the ability to block individual communities on an user level? We certainly have a ‘Block Community’ button available, and it seems functional from what I can tell.

      I’d love the ability to better filter and sort the communities list. In particular, I’d like to be able to filter (or sort) by communities I haven’t subscribed to, or by communities by instance. I get that we can go to another instance and see their community list, but it’s a bit of a PITA to subscribe or unsubscribe from there; ideally, we’d be able to do this within this community, so the sub/unsub links are present and functional.

      •  liquidparasyte   ( @liquidparasyte@pawb.social ) 
        1•1 year ago

        To expand on this; introduce some functionality like browse.feddit into the site itself, to show a list of communities that Pawb has federated with or is federating with, breaking that down by local/all, grouping similar subs together with a multi-reddit style collection of sorts, and gathering similar links/posts together in the interface in a manner like: discussions in (x) other communities/threads, so that regardless of where something is being posted/talked about, it doesn’t show up excessively on the front page (i think part of that is already here, but these would add refinements).

    •  dakerDraws   ( @dakerDraws@pawb.social ) English
      3•1 year ago

      Addition: Ability to follow entire instance (or at least follow all communities on an instance).

      Does there currently exist a way for one instance to poll another instance for their list of communities? I thought that an instance wouldn’t even know a community exists unless someone specifically searches for it.

      I know it’s listed under backend, but wanted to ask about the front end plan for this feature. Let’s say I search for Lemmy.world. Is the plan to output a checkbox list of communities and have us deselect any and confirm?

    •  Laurentide   ( @Laurentide@pawb.social ) 
      2•1 year ago

      Change: Better support for automatically linking other communities (and instances) back to your primary instance for easier following and interaction.

      Does this mean that finding and subscribing to communities on other instances will be streamlined? If not, that definitely needs to happen. The current process of going to another instance to search for a community there, copying a link, then going back to your home instance and searching for the community where you already know it doesn’t exist is just mindbogglingly unintuitive. Hell, I can’t even see NSFW communities on other instances even though my account is set to show them, and it seems like the only current way to fix that is to go to that instance and subscribe to one of its NSFW communities (that I can’t see).

    •  Pixel   ( @pixel@beehaw.org ) 
      1•1 year ago

      The ability to mute entire communities would be awesome, like if i wanted to keep up with pawb.social but dont have an interest in greyfur content, I don’t really have a way to filter that out of my personal feed. Would be awesome to have that level of granularity

      Multi-communities were suggested, but if possible merging identical topics within those multi-communities with some way to distinguish different communities discussions from the comments (kinda how reddit has its different comment sorting types, but basically it’d be a dropdown to let you see any community’s comments, basically merging cross-posts to reduce noise)

      A public list of federated/defederated communities and reasons why they’re defederated would be awesome just for transparency, probably a bit of a both front-end and back-end thing but it seemed worth mentioning.

    •  SavvyWolf   ( @SavvyWolf@beehaw.org ) 
      1•1 year ago

      Community Approval!

      Basically, an instance option that requires a new community to be approved by an admin when created, in the same way that a new user account would.

      As far as I’m aware, currently there is no notification that a new community has been created and unless people are watching the local community list regularly, it’s easy for them to slip by unnoticed. This allows scummy people to create a dodgy community, post a bunch of garbage to it and use it to attract more scummy people or start inter-instance drama.