kbin Federation Awareness script
Given how quickly Beehaw reacted to external users, it's becoming more important for users to know "where" they are engaging with content, meaning "where the content was federate in from".
Lemmy mostly has this handled in the UI but kbin still needs some time. Additionally, while the QOL plugin does show domain suffixes it's not a super strong reminder that you are engaging with federated users/comments/articles. This script colorizes based on "threat level" or strictness of the moderators of the federated server.
compatible with the excellent QOL updates tampermonkey script by https://kbin.social/u/SirPsychoMantis, as well as the other 2 scripts I've previously written
this is great! if anyone wants to change the colors to their liking, this is how:
here are my colors shown in step 3:
blue: rgba(163, 120, 138, 0.2)
red: rgba(62, 70, 106, 0.2)!
screenshot of comments
That's an awesome feature. Would it be possible to add option so it doesn't color whole comment background but eg. adds color to the username or something?
I know this is an old question, but I just got around to playing with things and found if I switched to the borders being the indicator it's a lot "quieter".
I edited lines 40 and 41 to this:
GM_addStyle('[data-is-strictly-moderated="true"] { border-color: rgba(155, 100, 0, 1.0); border-width: 3px; border-style: double;}');GM_addStyle('[data-is-federated-content="true"] { border-color: rgba(0, 100, 155, 1.0); border-width: 3px; border-style: double; }');I changed the script a little bit more to use a class instead, but I've modified my class style to the original lookup style. Should work.
Thanks for the heads-up!
That's nice too. The only thing I'd suggest is having the px as negatives, but that's because I actually didn't think it was working for a bit since I tend to read the left side and totally missed the highlights on the right.
Edit - I just realized that while this point is true on feeds, once you get into the comments putting those colors on the left side would mess up the coloring that shows a tree of comments since that's also on that side. So the fed colors really need to go on the other three sides to be compatible.
A preference setting for this (in the future) could have a huge number of styles to pick from. Some people may even prefer the original simple background color.
I don't want to hijack @CodingAndCoffee 's thread, but... look here. And if you choose to use that, check your options menu out. Though, I only allow it on the left side for articles in the options because I don't like overwriting the waterfall on the left (probably one of my extensions if you don't know what I'm talking about).
Tried the code out. It's working as far as the fed stuff like the original (that I can tell) but I don't see the additional stuff anywhere that your header insert should be pulling up, if I understand the coding intent. Nothing is new on the sidebar with other script options. Best guess is like other issues I've run into it's a Firefox thing.
Weird - I'm using LibreWolf, for all intents and purposes - Firefox. Example
I just took a look at a code and it's kinda hilarious how beehaw is the only one in the strictly moderated list.
I wrote one for Lemmy as well https://greasyfork.org/en/scripts/468763-lemmy-federation-awareness
this one also shows a distinction for kbin users, which I thought would be helpful for Lemmy users because the functionality of how the sites work is just different enough that not realizing someone you're replying to is using a different platform can and has been causing all kinds of confusion.
Oh this is real helpful! Thank you
Suggestions for UI enhancements for the next version of this type of thing:
Allow real time modification of the colors (including transparency)
Be able to choose where the colors are (background, border, text, other)
Able to type in or remove domains or maybe even communities and users and set the colors
(Probably too complex but ) have domains be on a selection menu with some indicator of their actual federation status
The latter is because this federation thing is very fluid and what you set this week may not be the best for next. Dare to dream that we could have some federation setting that would automatically determine where each domain is currently and let us know via this kind of thing, vs. having to research or go by word of mouth all the time.