Bookmarklet to automatically create attribution from e621

PurringFox@yiffit.net · 1 year ago

Bookmarklet to automatically create attribution from e621

Wander@yiffit.net · edit-2 1 year ago

Test:

by fffox [1][2].

Edit, by the way, good choice in loading only e621 sources. A potential vulnerability could have come from loading images from external non-trusted sources, but from checking the code and decoding the bookmarklet encoding everything checks out! Good work <3

Wander@yiffit.net · 1 year ago

Hello! Thank you a lot for this ^^

I’ll give it a try in a moment. But before I do, can I propose something to you?

I noticed that I’m able to insert an arbitrary html header into lemmy-ui as part of the environment variables. This could include a <script src=“”> type of header linking to a javascript file of our choice which I could host myself so that there’s no problems with same-origin policies.

I have already started working on a script that creates a “unblur nsfw content” setting in the user’s settings and stores the value in the browser’s localstorage. This is just an example of the type of customization that could be done.

If you ever come up with any interesting “user scripts” for the lemmy ui, I might be able to include them into the site itself. I’m using greasemonkey for the development since it loads automatically every time you open a page and you can also do url filtering, but the idea is to insert the end scripts into the page itself (after publishing them for peer review).

So, if you ever come up with an interesting script idea, feel free to let me know or send me the result. You might also be interested in this lemmy communty: !plugins@sh.itjust.works

PurringFox@yiffit.net · 1 year ago

At first I actually wanted to create an additional button for the editor in create post, to paste the link to, but then I decided against it, since I wanted a more universal approach.

But now I’m actually interested in writing lemmy UI plugins, maybe I’ll rewrite my code :).

First I was confused but now I think I get it. You already did something on here, that nsfw stuff is unblurred by default (since it is at least like that for me now), but you would like to make that toggleable. What talks against the “disableblur” and “shownsfw” themes that are selectable. Are these also experiments from you?

I’ll do some research regarding lemmy ui now.
It would actually be better, when there already would be a way to extend behavior server side, like modifying the HTML that gets served, instead of doing it ad-hoc on client side (performance). Also if at point there are to many scripts “patched in” they’ll probably start to be incompatible. Example, I append a child node to a element called “x” and another script removes the element “x” for some reason, which would break mine. Let’s see if extensions are planned in lemmy. Else forking the entire UI and expanding on that would also be a (but more time intensive) possibility.

I’ll come back to it, after I did some more research.

Wander@yiffit.net · 1 year ago

Right now the blur is controlled via css. Disableblur is a theme that is set by default and which incorporates the css classes that override the default behavior. The problem is that blur is enabled again when a user chooses a different theme.

What I was thinking of doing was having a script that would fetch your preference from local storage and then dynamically change CSS. I agree to keep it light, but there’s a lot of potential. Doing things serverside is possible, but I’d have to learn how to compile and dockerize from source, which might be complicated because the site is written in inferno and would also break future updates.

PurringFox@yiffit.net · 1 year ago

I’m researching right now. Regarding the blurring there is already a pull request, that implements the exact feature you would like to do (if I understand you correctly) https://github.com/LemmyNet/lemmy-ui/pull/1640.

I agree, maintaining a fork of lemmy-ui and rebuilding it every change is not feasible. Sadly it looks like there are not much more possibilities of extending the ui than the custom header and custom theme css.

So I think the header scripts it is… But one thing I think would be nice is, that these scripts can be enabled/disabled by the users individually and should be off by default. So that people not interested in that are not impacted by possible performance issues or bugs. Nice would be if it would be possible to create an additional settings tab, where all these extra scripts are toggleable.

Let’s see, if I have time I’ll setup a dev-environment to experiment with stuff.

Wander@yiffit.net · 1 year ago

Thank you <3 There’s no rush, although I’m pretty excited about the potential!