I’m working on open source projects :)

🔗 Links:

GitHub Reddit

🍪 Get me a cookie:

Go to Ko-fi GitHub Sponsor
  • 38 Posts
  • 51 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


  • Thank you for putting all this together!

    Potential conflict of interest: I help with !instance_assistant@lemmy.ca

    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

















  • 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’re actually working on a browser extension for this! It currently supports both communities and posts

    !Instance_Assistant@lemmy.ca

    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.