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

This looks good, thank you!

I think it’s about IO interrupts?

https://www.geeksforgeeks.org/interrupts-in-8086-microprocessor/

deleted by creator

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

I think the issue here is

they don’t show up under “posts” on your own profile

It makes sense to hide read posts on the main feed, but not when you’re looking at a particular user?

I’ve been working on the [email protected] extension :)

RES initially helped me get into Reddit, so hopefully this helps people get into Lemmy as well

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

This is very helpful, thank you! I’ll look into setting up more of that sometime

Good to know, I’ll explore some more

Thank you!

Makes sense, thank you!

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

Sounds good! This was my first dive into browser extensions as well. It’s not too bad once you go over the basics. If you give it a try, see the contributing page on the repo’s wiki for some resources on how to get started with browser extensions.

A super short summary is:

• manifest.json is the entry point, it links to HTML files (which represent things like the popup, sidebar) and scripts (which do most of the work)
• the background script runs all the time (see background.js), and the content scripts run on specific pages (ex. There’s one for Lemmy community pages, one for error pages)

If you DO give it a try, we were part way through migrating features from the LemmyTools userscript and that might be a good place to start. I wasn’t familiar with userscripts so I didn’t make much progress, and can’t get back to it for a little while. The issues page of the repo should have LemmyTools related features tagged. If any details are missing, let me know and I’ll add them in :)

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:

[email protected]

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