I’m working on open source projects :)
🔗 Links:
GitHub |
---|
🍪 Get me a cookie:
Go to Ko-fi | GitHub Sponsor |
---|
For smaller extensions, you can start by looking at the manifest.json
as this file is the entry point. You can see which part of the code needs access to ‘everything’ and go from there.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json
For example, with Instance Assistant for Lemmy, you need to give access to all sites because it needs to run on any Lemmy site and that’s not something you can hardcode in.
You could try from this
https://lemmy.world/post/1289432
Ideally try for a smaller size, else it takes time to load and wastes people’s data
We actually have an extension for this, it’s one of the more popular extensions for Lemmy&Kbin, going by the counts on chrome/firefox stores:
It was originally made to solve this problem, but we’ve been adding other features as well. Right now you can redirect communities and posts, and redirect links by right clicking on them.
Let me know if it works, and also where it doesn’t so that we can improve it :)
I personally find a lack of downvotes to be annoying and harmful. People don’t go through the trouble of reporting problem content, and it usually leads to poor quality inflammatory content rising to the top.
If you’re new and haven’t really set up yet, explore other instances. You can find one that aligns with what you want out of Lemmy without jumping through hoops.
If you have set up, there are account migration tools for you. They just aren’t perfect yet
That sounds good, and it sounds easy enough to implement.
I’ve made the issue here: https://github.com/cynber/lemmy-instance-assistant/issues/45
I’ll get to it when I have time in the next few months, unless someone else gets to it first :)
For sure, I’ll incorporate a TLDR in future posts :)
That’s really great to hear, thank you for the comment :)
Image size manipulation is something that’s on the list, and it’s one of the features that myself and the dev for LemmyTools was working to bring over from the userscript
Here is the specific issue, although I’m not sure when I’ll be getting to it: https://github.com/cynber/lemmy-instance-assistant/issues/28
In the meantime, you could also try out the userscript itself and see if it does the job, and also what could be improved when we do bring the feature over: https://github.com/howdy-tsc/LemmyTools
There are a few userscripts out there which I could integrate into the extension. It depends on when this commit gets pushed into Lemmy core:
https://github.com/LemmyNet/lemmy/issues/2397
After that, it could still be useful if someone wanted to block it browser wide. At that point I’d check if people still want something like that.
Sorry to those that have already seen this. I’m trying to space out the posts so it’s not in a large clump in your feeds. People have different subscription lists, so I’m trying to reach those that haven’t seen it yet.
These are the last 4 posts :)
Sorry to those that have already seen this. I’m trying to space out the posts so it’s not in a large clump in your feeds. People have different subscription lists, so I’m trying to reach those that haven’t seen it yet.
These are the last 4 posts :)
A few days late, but this is actually something I’ve been working on for Instance Assistant! I implemented a first attempt and released it this weekend. Let me know if it works for you :)
It should pop up in the sidebar of any post on a foreign instance. If it doesn’t load, you may need to refresh the page. That’s something I’m still working on because redirecting on a Lemmy site isn’t always detected as navigating to a new page.
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 guess so, it would still be a problem. Once one extension is caught, it should be simpler to catch the rest.
It’s harder to quickly switch stuff up when you need to send the devs new code to put in
From what I’ve experienced with my extension, every update has to go through a review process. Firefox is pretty fast, chrome takes a few days and edge takes a while (opera hasn’t finished reviewing my first version, so I stopped trying with them).
The only time I failed a review was early on when my build script choked and I submitted an empty file to Chrome (whoops). So I can’t really tell how good those reviews are, but I’m not planning on testing them. I just know that they exist
I think the issue here is
It makes sense to hide read posts on the main feed, but not when you’re looking at a particular user?