Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]
Fyi this is calling out links made with the official autocomplete. I've blocked it but does that stop it from replying to me or just stop me from seeing the replies?
It stops it from replying to you. And the official autocomplete is weird, it produces wrong links and then replaces them on the fly with the correct ones.
Yeah I'm aware not all the app interfaces etc have caught up with the proper links yet. So I'll just keep including the local ones manually for now to include the most people. Anyway cheers, I post a lot of links so as long as it's not hassling me with false positives 😄
It probably doesn't know about the community, or it doesn't have support for the site. Can you link me to the post (either here, or in PM, it's up to you).
Edit: Probably found it, it doesn't have any support for news.sky.com, shall I add it?
Thanks for your answer. idk about adding it, the article sounded interesting but idk how relayable this news site is and how much work it takes. I guess it's up to you :)
Added it along with the ability to respond to mentions. Once it's deployed, it should respond to your mention (hopefully, it was kinda huge overhaul of the code).
Just throwing out an idea, feel free to ignore it XD
I think that if one would write a quick "how to write a site handler" with a built-in template (like I've seen used), I'm sure many will contribute and send PRs for their favorite sites. If you're interested of course. I don't mind volunteer for doing the writeup either.
Go to your favorite news site (for example: euronews.com)
Go to a random article
Go to the blank space inside of the actual article (Not the summary that's usually on top)
Right click on that spot and go to inspect
In our example:
Then, look at the div HTML element it selected for you, and try to go up to the Parent div element as long as when you select it, only the body of the article get mark.
In our example, when I did the inspect step, I got this div element marked:
But, as I went up the tree like the last step said, I found this div:
You might think to go even upper like this:
But as you can see, the browser highlighted parts that aren't the body of the article itself. So...don't.
NP, but I'd advise you to save it somewhere else as a whole as I don't know for how long that code sharing website host the templates. Although you can easily rewrite this part.