Explanation
So, as I've been using Lemmy, I've been trying to make a list of features/requests.
But my ideas are not... Complete. They're just simple ideas that may already have a feature request associated with it.
So the purpose of this post is to create and share them, put my ideas on paper and see what kind of discussion can come from it.
If there is already an issue on the GitHub covered by my idea, let me know! I can update this list to reference that here, so I know it's being worked on.
Anyways, in this post above, and added to this comment below are my ideas, feel free to give feedback or additional ideas. If any of these ideas get enough traction, I'll make a feature request issue on the Lemmy GitHub.
(Of course, someone else could beat me to it, too.)
Usability improvements
Optional URL Federating
Currently, to federate, you have to search for an instance using the search in the upper right corner of the site.
After it's searched, you can subscribe to the community from a URL templated like this:
https://<instanceDomainName>/c/<communityName>@<targetInstanceDomainName>
If you do not do the search first, (Read: You attempt to go to the community page before using the search function) the above URL would return 404.
As a general improvement, I would say when attempting to connect to a community that has not been federated yet, it should at least attempt to federate before returning 404, saving a step.
Built in safety:
- Do not add, search, or federate the community unless this URL is requested by a local member that is signed into site/instance.
- Do not federate community until the local member actually subscribes to that community.
Separate load text for Federating
Related to above, when searching for a community that is not yet federated, there is a delay for a community that hasn't been connected/federated to the current instance.
However, when it's done searching the local site, it is still attempting to search and federate to the external site/instance.
For this I recommend any of the following:
- In search results, have separate sections for local and external results.
- When it is still attempting to federate
- It should show that it is in fact, still trying to search and/or federate
- The message should should be distinct from a local search
- Simple ideas:
Federating...
- Advantages:
- Simple
- Drives home the concept
- Disadvantages
- Unintuitive (But then again, so is the entire concept)
Searching for external Community
- Advantages:
- Disadvantages:
- No side benefits like above
Notifications issue
If notifications are enabled on a site/instance, and a user decides to allow them, they get a notification for each tab of that site/instance that is open, instead of 1 notification total.
End of Original Post