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

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!

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.

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!

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

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)

Hope it works for you!

Hope it helps :)

Hope it helps!

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

Thank you, hope it helps!

There ARE other downsides to this law, outside of the hissy fit Facebook is throwing.

For example, smaller independent news companies don’t have the bargaining power to come to a fair agreement with Facebook, like the larger organizations can. A solution to that might be to have some standard rates set up, but again, don’t know enough about it

I don’t agree with the solution the government came up with, but the problem still exists and I don’t understand it well enough to come up with an alternative solution.

Making news is expensive, and good quality news (not mucked up by corporate interests) needs a way to fund that work. We don’t want news to be an outlet for corporations investing in a mouthpiece. So traditionally this was done through advertising.

Now people barely ever click through to the websites so the advertising doesn’t work. Meanwhile the places where people ARE seeing the news do have ads. The content is produced by one party, and the profit goes to another.

The problem exists and needs a solution, but I don’t know what it might be. Australia brought in a similar law successfully and Facebook/Google came to a deal. Canada might also be able to do that?

The other long term solution IMO is to make the platforms obsolete with things like Mastodon and Lemmy. That might take some time though

Not really emergency notifications but news, which tbh isn’t as important in this case because non-Canadian news orgs aren’t affected and are covering it too. So there isn’t an immediate risk I don’t think.

As for the main point: The problem is that a subset of the population ONLY gets information through one platform. The only way to reach them is through that platform, and not reaching them means excess costs when you have to rescue/treat/otherwise deal with the fallout. It’s also the government’s job to inform people and keep them safe.

At the same time, the companies need to be regulated by the government. Can’t just let them have free reign because they seized control