70
This is amazing, thank you for reaching out to the dev!
This was on the list of ideas for InstanceAssistant, but I didn't know where to start. It is great news that it was added to the original extension.
55
EDIT: Thank you for all the great responses! I agree that a forced implementation is no longer the way to go. I've left the post as is, aside from this comment, in case anyone wanted to reference part of it. At this point, I think implementation 1 (Sincere Request) is the way to go if anything.
I've seen a few of these posts, some with really cool solutions, but a lot of them are difficult to implement, or complicated for casual users to understand. Here is my proposal on how we can coordinate communities that share the same topic, while also keeping the spirit of federation.
This post has some general thoughts on why I think this is the best solution. It also has some possible implementations, including a trivial one that works already without any automod or code changes.
General Thoughts
This talks about why I think this is a better solution. Feel free to skip to 'proposed solutions'.
Leave vote counts alone:
- Some proposals talk about sending vote totals to the original post or having all cross posts share a total vote count. This leads to issues since larger communities can manipulate which posts show up, and it creates an incentive for users to spam posts to unrelated communities. This also might lead to implementation issues, where the vote counts don't properly federate out. It's also confusing for casual users, and it takes power away from individual communities to decide if a particular post is relevant or not.
- With all that in mind, I also don't see much of a benefit in playing with the vote counts. It might be better to leave them alone.
What are the issues we're trying to address
- Comment threads are disjointed. Users need to open up multiple posts to see what is being discussed. With small communities, a few users are just talking into the void. This issue is addressed.
- Can't see relevant content without subscribing to multiple communities. While this can be seen as a downside, I think it has an added benefit because each community can decide if a post is relevant or not. Forcing posts into one community may lead to other drama with linking/unlinking, and it's very confusing for casual users to figure out who's actually going to see a particular post if it automatically appears pops up in other communities.
- Scrolling past multiple identical crossposts in a row. My proposal doesn't address this directly, but it may offer a way for apps and frontends to deal with them.
Proposed Solutions
The general premise here is:
- User makes a post in community A
- User makes crossposts in communities B, C, and D
- Posts in communities B, C, and D are locked, with a link to the post in community A
- If someone wants to make a comment about the content, they can do so in the main post in community A
Benefits
- User can pick which community to have the comments appear in. They can base this on rules, moderation style, or if they want to promote a niche community
- Everyone else is free to upvote/downvote the posts independently
Issues that need to be addressed:
- A malicious user can post a scam or misleading content, and then lock the post with no easy way for people to call it out. While this can be reported to moderators, people may fall victim to it before the post is removed and the user is banned. Simply checking for a redirected post isn't enough because a user can make that post be on an instance/community they control, and remove comments calling out the content.
Implementations
- Sincere Request: After making a post, the user can paste in a standard comment asking people to comment in the linked post.
- Doesn't require any code changes and you can start doing this right now
- Relies on commenters listening to the request
- somewhat silly, but this is the easiest implementation
- Automod locks top level comments: After making a post, the user can leave a comment to trigger automod.
- automod will prevent any top level comments, but still allow replies to the original comment.
- requires updates to core lemmy for partial locks, or for an admin level bot that can remove comments from posts based on characteristics
- Automod locks post entirely: After making a post, the user can leave a comment to trigger automod.
- automod will lock the post entirely, and leave a comment on how to deal with issues
- anyone can message automod with a link to the post, and have it be unlocked to discuss issues
- doesn't require updates to core lemmy, but it does require an admin level bot
___
6
cross-posted from: https://lemmy.ca/post/6770347
This is a very small update, but hopefully it's helpful! As I mentioned in the last update, I'm a little tied up with other commitments right now, so I haven't had a chance to implement the other features on the to-do list. This one was requested the other day, and it was simple to add since I could reuse a lot of existing code.
Links:
- Firefox Add-on
- Chrome Extension
- Edge Add-on (waiting as of 2023-10-09)
- GitHub
β What is Instance Assistant?
If you're new to Instance Assistant, it is a browser extension with a collection of tools and features to simplify your browsing experience on Lemmy and Kbin. It is available on Chrome, Firefox, and Edge; you can also install it from the releases page on GitHub.
For a full list of features, please see the GitHub homepage: https://github.com/cynber/lemmy-instance-assistant
β What's new in v1.2.6?
- Redirect user profile pages: When you want to message a user and click on their profile, you might end up on a foreign instance. To message them, you need to modify the URL or copy/paste. Instead, you will now find a little button to jump you to your home instance.
π Also
Thank you for all the suggestions and feedback! Like I said before, I'm really happy to see that people are using the extension and finding it useful. Please continue to make suggestions and contribute your expertise.
Cheers :)
7
cross-posted from: https://lemmy.ca/post/6770347
This is a very small update, but hopefully it's helpful! As I mentioned in the last update, I'm a little tied up with other commitments right now, so I haven't had a chance to implement the other features on the to-do list. This one was requested the other day, and it was simple to add since I could reuse a lot of existing code.
Links:
- Firefox Add-on
- Chrome Extension
- Edge Add-on (waiting as of 2023-10-09)
- GitHub
β What is Instance Assistant?
If you're new to Instance Assistant, it is a browser extension with a collection of tools and features to simplify your browsing experience on Lemmy and Kbin. It is available on Chrome, Firefox, and Edge; you can also install it from the releases page on GitHub.
For a full list of features, please see the GitHub homepage: https://github.com/cynber/lemmy-instance-assistant
β What's new in v1.2.6?
- Redirect user profile pages: When you want to message a user and click on their profile, you might end up on a foreign instance. To message them, you need to modify the URL or copy/paste. Instead, you will now find a little button to jump you to your home instance.
π Also
Thank you for all the suggestions and feedback! Like I said before, I'm really happy to see that people are using the extension and finding it useful. Please continue to make suggestions and contribute your expertise.
Cheers :)
18
cross-posted from: https://lemmy.ca/post/6770347
This is a very small update, but hopefully it's helpful! As I mentioned in the last update, I'm a little tied up with other commitments right now, so I haven't had a chance to implement the other features on the to-do list. This one was requested the other day, and it was simple to add since I could reuse a lot of existing code.
Links:
- Firefox Add-on
- Chrome Extension
- Edge Add-on (waiting as of 2023-10-09)
- GitHub
β What is Instance Assistant?
If you're new to Instance Assistant, it is a browser extension with a collection of tools and features to simplify your browsing experience on Lemmy and Kbin. It is available on Chrome, Firefox, and Edge; you can also install it from the releases page on GitHub.
For a full list of features, please see the GitHub homepage: https://github.com/cynber/lemmy-instance-assistant
β What's new in v1.2.6?
- Redirect user profile pages: When you want to message a user and click on their profile, you might end up on a foreign instance. To message them, you need to modify the URL or copy/paste. Instead, you will now find a little button to jump you to your home instance.
π Also
Thank you for all the suggestions and feedback! Like I said before, I'm really happy to see that people are using the extension and finding it useful. Please continue to make suggestions and contribute your expertise.
Cheers :)
35
cross-posted from: https://lemmy.ca/post/6770347
This is a very small update, but hopefully it's helpful! As I mentioned in the last update, I'm a little tied up with other commitments right now, so I haven't had a chance to implement the other features on the to-do list. This one was requested the other day, and it was simple to add since I could reuse a lot of existing code.
Links:
- Firefox Add-on
- Chrome Extension
- Edge Add-on (waiting as of 2023-10-09)
- GitHub
β What is Instance Assistant?
If you're new to Instance Assistant, it is a browser extension with a collection of tools and features to simplify your browsing experience on Lemmy and Kbin. It is available on Chrome, Firefox, and Edge; you can also install it from the releases page on GitHub.
For a full list of features, please see the GitHub homepage: https://github.com/cynber/lemmy-instance-assistant
β What's new in v1.2.6?
- Redirect user profile pages: When you want to message a user and click on their profile, you might end up on a foreign instance. To message them, you need to modify the URL or copy/paste. Instead, you will now find a little button to jump you to your home instance.
π Also
Thank you for all the suggestions and feedback! Like I said before, I'm really happy to see that people are using the extension and finding it useful. Please continue to make suggestions and contribute your expertise.
Cheers :)
7
This is a very small update, but hopefully it's helpful! As I mentioned in the last update, I'm a little tied up with other commitments right now, so I haven't had a chance to implement the other features on the to-do list. This one was requested the other day, and it was simple to add since I could reuse a lot of existing code.
Links:
- Firefox Add-on
- Chrome Extension
- Edge Add-on (waiting as of 2023-10-09)
- GitHub
β What is Instance Assistant?
If you're new to Instance Assistant, it is a browser extension with a collection of tools and features to simplify your browsing experience on Lemmy and Kbin. It is available on Chrome, Firefox, and Edge; you can also install it from the releases page on GitHub.
For a full list of features, please see the GitHub homepage: https://github.com/cynber/lemmy-instance-assistant
β What's new in v1.2.6?
- Redirect user profile pages: When you want to message a user and click on their profile, you might end up on a foreign instance. To message them, you need to modify the URL or copy/paste. Instead, you will now find a little button to jump you to your home instance.
π Also
Thank you for all the suggestions and feedback! Like I said before, I'm really happy to see that people are using the extension and finding it useful. Please continue to make suggestions and contribute your expertise.
Cheers :)
We're actually working on a browser extension for this! It currently supports both communities and posts
We ran into the same issue, federated sites are hard to work with. Right now, the extension has it so that a user needs to right click on a link to be redirected. That way the user can choose which links get redirected, and there's no chance of accidentally redirecting the wrong thing.
There are other solutions (using the API for example), but they seemed to slow the browser down too much. Another proposed feature that hasn't been implemented yet was to redirect when holding down a key (when holding down "r", try to redirect the link).
Feel free to take a look, try it, and you can totally contribute code. It's all open source and we've tried to keep the code simple and easy to verify/contribute.
That's fair, I've posted here in the past but I'll take it off my list moving forward. I think early on there wasn't much content so it was ok, but now that the community is rolling it's not that relevant
It's good feedback!
I don't agree with the solution the government came up with, but the problem still exists and I don't understand it well enough to come up with an alternative solution.
Making news is expensive, and good quality news (not mucked up by corporate interests) needs a way to fund that work. We don't want news to be an outlet for corporations investing in a mouthpiece. So traditionally this was done through advertising.
Now people barely ever click through to the websites so the advertising doesn't work. Meanwhile the places where people ARE seeing the news do have ads. The content is produced by one party, and the profit goes to another.
The problem exists and needs a solution, but I don't know what it might be. Australia brought in a similar law successfully and Facebook/Google came to a deal. Canada might also be able to do that?
The other long term solution IMO is to make the platforms obsolete with things like Mastodon and Lemmy. That might take some time though
Not really emergency notifications but news, which tbh isn't as important in this case because non-Canadian news orgs aren't affected and are covering it too. So there isn't an immediate risk I don't think.
As for the main point: The problem is that a subset of the population ONLY gets information through one platform. The only way to reach them is through that platform, and not reaching them means excess costs when you have to rescue/treat/otherwise deal with the fallout. It's also the government's job to inform people and keep them safe.
At the same time, the companies need to be regulated by the government. Can't just let them have free reign because they seized control
Yep, it works perfectly
Bitwarden has it too, but eggs in one basket etc.
What's a good place to get/hold domains these days?
This is something that is probably better if implemented in Lemmy itself. It would be tied to a particular community, and it wouldn't need to cross over between instances.
If someone tried to make a browser extension for it, it would only appear for people using the same browser extension. Some third party apps have it like that, and it's not that helpful.
What's better for a browser extension / app to take on is cross-instance functionality, such as jumping between instances, having buttons / content in the UI, etc. I'm working on an extension for that ( !instance_assistant@lemmy.ca ), and while I really want flairs as well, I don't think it would be good for a browser extension.
Once it's implemented in Lemmy itself, then we could probably make it easier to add/remove/view/filter flairs using a browser extension.
I tried Sync for a bit, but I agree with the other posters that the pricing model is a little outrageous.
Have you considered adding a donation option through google play? I'm not sure what the process is like, but it might make it easier for people to donate.
Yep, use lemmyverse.net to search.
We're integrating lemmyverse.net searches into the browser extension were working on (see more on https://lemmy.ca/c/instance_assistant) so that it pops up right on the Lemmy UI,, but for now I just open it in a new tab
I've been using Nova Launcher for years now, but I explored other options a few months ago because of the ownership change. Lawnchair was the best one I found, but I didn't switch to it because it looked like it was missing features I needed. Folders was an important one.
Which version / source are you using for the app? I got a bit lost trying to find a recent version. The last release on the GitHub is from 2018, and the last prerelease is from a year ago. There's also an issue for the folders which I was following, and it actually just went stale: https://github.com/LawnchairLauncher/lawnchair/issues/2471
I also see Lawnchair2, but that looked like a fork or something
view more: next βΊ
I was chatting with a friend, and she mentioned how she tries to at least set up a README, which includes her vision for the project and her plan for the implementation, design, and goals.
Best case scenario is that the planning helps her complete the project herself. Worst case scenario, someone else can pick up where she left off and use her considerations for the project.
I'm thinking of doing that for future projects too