This looks good, thank you!

That t-shirt would be cool, but don’t have time to properly test our extension before then

I’m looking forward to December when I’ll have time to work on it. I’ll try to attend some office hours, I didn’t know that was an option

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?

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

!instance_assistant@lemmy.ca

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

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.

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

I don’t have as much experience working with the stack, but from what I’ve read it seems like Rust is a pretty solid choice for the backend. It also seems like a lot of the upgrades people want are for the front end, so that’s what would benefit the most from being simpler.

Typescript makes sense, and a handful of frameworks have typescript support. Would anyone know more about the benefits of using Inferno over something like Vue/Nuxt or plain React?

Hope it helps!

Hope it helps :)

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.

Thank you, hope it helps!

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