Thank you for putting all this together!

Potential conflict of interest: I help with [email protected]

Having a separate list for extensions would work nicely, although I think it fits to have the extensions listed here. There are few actual browser extensions for Lemmy/Kbin/Mastodon. There are a lot of scripts, and we were working on incorporating the better scripts into the extension for the same reasons you mentioned above. Scripts are harder to manage and review

My thoughts on the questions.

1. “last stable version” sounds like a good way to sort it, for readers. It might become cumbersome for you to manage unless you can automate it somehow.
2. I’m leaning towards flagging or removing out of date apps because of potential security issues. Could you contact devs after a few months to ask if it is being maintained?
3. A big list of every app would be interesting for data. It isn’t helpful for users, so I agree with keeping them off
4. I have a donation link. I don’t think it should be included in guides or lists either
5. I like the formatting, as a reader. Consider if it becomes too cumbersome for you and your team to manage. I’d rather have a list that stays up to date and doesn’t cause headaches for the maintainer

I plan on experimenting with the suggestions posted here. That way I can narrow down where the problem is

The live website works on desktop and mobile. The offline folder works well on desktop, but it has issues on mobile, such as the search bar not working

That would work

I’ll check it out

Thank you, I’ll try those

deleted by creator

deleted by creator

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.

This doesn’t answer the Linux part, but on FDroid there’s something similar as “Retro Stack”

Thank you for sharing! This is my first project like this so I’ve got lots to learn. I’m going to try and contribute to a few other ones so try and learn what it’s like

Good to know, could you share what website you were trying to post from?

I think one thing I should implement is a little toast message that explains what went wrong (ex. No title contents found)

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 :)

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

Don’t extensions get reviewed by the various stores? I’d imagine an automated check could catch malicious integrations like that.

Maybe not right away, but once they catch wind of one shady extension they could just search the store for any other ones.

deleted by creator