I made a userscript (eventually converted into a userstyle) so I could go sightseeing across lemmy and spot all you animals out in the wild. pawb.social, pawb.fun, and furry.engineer are pre-filled already, but you can add other servers to track as well!
Edit: Special mention to redyoshi49q@furry.engineer for this post, whose techniques resulted in CSS to achieve parity with my userscript. My older userscript should not be used anymore, as the CSS will do the same thing but more efficiently.
Instructions:
-
Install Stylus extension for firefox/chrome
-
“Write new style” in the addon settings
-
Copy paste the CSS code below in
-
Modify the code around line ~11 in order to reflect your homeserver and any additional frendservers that you want to highlight. Currently it’s set to pawb.social and the mastodon servers that pawb.social also operates, but feel free to add some of the furry instances below as well (post in the comments if you’ve got a good furry instance to add here!):
- yiffit.net
- meow.social
-
Modify the code around line ~19 to reflect your homeserver
-
(Optional) If you’d like your homeserver buddies to have a different marker, uncomment the various sections around line ~27 through ~50 by removing the
/*and*/bits -
(Optional) Play around with different markers and colors!
CSS/Userstyle: https://gist.github.com/redyoshi49q/f1b2d1da0a8f7536aba1f8c3110d2dd8
I love this concept! Another prominent instance that comes to mind is meow.social I’m looking forward to playing with this after work _
Added to the description!
I’m on meow.social, it’s a good instance but it is quite large and is near the limits of what it can handle, I believe. The Fediverse does better spread across smaller instances.
I signed up about five years ago back when it was smaller; then snouts.online went down, and a lot of users migrated to meow.
Thank you so much for this and thank you for mentioning us! ❤️
I’m not on a PC right now but will install it in a little while.
❤️ I’m working on an update to this at the moment so stay tuned. The way lemmy re-uses links is not what I was expecting, so currently if lemmy live-inserts a new post above another one, everyone’s hearts get mixed up. I’ve got a fix for this but I’m going to look at a couple other features as well.
No worries! I was wondering if I could pitch an idea. The biggest gripe I have right now with Lemmy is not being able to only view content of furry instances.
I was imagining a userscript that when you turn it on, hides any post that wasn’t submitted to an @pawb.social or @yiffit.net instance.
Do you think that’s feasible?
A CSS script could do that… if the :has() selector is supported.
With that said, I’ve recently run into issues with that selector not being supported (due to it being recent CSS spec) in two different (but not recently updated) user style extensions that I’ve tried it with (in one, it is entirely unrecognized; in the other, you get errors when trying to do nontrivial things in the :has() ).
I could copy/paste some example user CSS for you if you’d like to see if you can get it working.
I whipped up a proof-of-concept user CSS that does this (and should automatically adapt to entries shifting down).
**********
@namespace url(http://www.w3.org/1999/xhtml);
@-moz-document domain(“pawb.social”) {
a.text-info[title$=“@lemmy.blahaj.zone”] span::before {
content: "❤ ";
color: red !important;
}a.text-info:not([title*=“.”]) span::before {
content: "★ ";
color: yellow !important;
}}
The first part prepends a red heart to usernames from a particular remote server (and variants of the CSS selector can be copy/pasted into a comma delimited list to allow the rule to apply to other servers as well).
The second part prepends a yellow star to usernames from the local server… by crudely assuming that they won’t contain any periods (CSS selectors aren’t flexible enough for anything more elegant). The selector can instead be applied to the first rule to make those hearts as well.
Edit: Okay, apparently you need to pick a language if you’re sending a message from lemmy to mastodon, otherwise you get eternal spinner.
Normal comment as follows:
You’re amazing. I had a gut feeling that CSS could solve this but I couldn’t find enough info myself. I’m a backend/integration guy and CSS scares me.
This solution is definitely better designed than mine, but I’m not sure if it can handle highlighting when you’re on a foreign server instance (e.g. literally on beehaw.org and not pawb.social). This isn’t a huge deal imo but I posted the script somewhere and someone immediately wanted that feature so I put it into mine. I did solve the shifting around issue - it wasn’t that hard to solve I just wasn’t expecting lemmy to reuse elements in such a weird way. When a post comes into the feed, all the elements change their values directly - nothing “moves” around in the DOM (at least that’s what I observed during 10 seconds of testing).
With your current CSS, there’s an issue where the star inserts itself on upvote counts for me after I’ve upvoted a post:
This should be fixable by using something like this (pls fix if I’m doing it wrong):
a.text-info[title$="@lemmy.blahaj.zone"] span::before { content: "❤ "; color: red !important; } a.text-info:not([title*="."])[href*="/u/"] span::before { content: "★ "; color: yellow !important; }I can confirm both that my original version has the bug you described and that your fix does not produce that bug.
I don’t actually have a native Lemmy account, so I didn’t realize that upvoting would cause the upvote count to gain a CSS class that I used in my selector.
(Thankfully, the DOM changed to reflect given/taken upvotes in spite of me not being logged into the Lemmy server at all; I only got a “Not logged in.” error each time.)
(Also, you would not believe how often I’ve had to write user CSS to unbreak the broken CSS of websites.
A classic example is when the CSS defines dark text color without defining a background color. The browser I use derives color defaults from the OS, which uses light text on a dark background, and the page renders in dark text on a dark background, generally becoming nearly unreadable.
I’ve also (ab)used “display: none !important;” to snip out annoying “improvements” to pages.)
I’ve ended up with a style like this:
a.text-info[href*="/u/"][href$="@pawb.social"] span::before, a.text-info[href*="/u/"][href$="@pawb.fun"] span::before, a.text-info[href*="/u/"][href$="@furry.engineer"] span::before { content: "❤ "; color: red !important; } a.text-info[href*="/u/"]:not([href*="@"]) span::before { content: "★ "; color: yellow !important; }Frustratingly, I can’t seem to check whether pawb.social is in the href of a relative href like
/u/yote_zip. If I could do that, this could work on foreign instances, because I could add a qualifier that someone is not only a member of the instance I’m currently on, but also my specific homeserver. As-is, this can be limited to pawb.social and will work just fine.Try this:
@-moz-document domain(“pawb.social”), domain(“yiffit.net”) {
a.text-info[href*=“/u/”][href$=“@pawb.fun”] span::before,
a.text-info[href*=“/u/”][href$=“@furry.engineer”] span::before {
content: “❤ “;
color: red;
}
a.text-info[href*=”/u/”]:not([href*=“@”]) span::before {
content: "★ ";
color: yellow;
}
}@-moz-document domain(“pawb.social”) {
a.text-info[href*=“/u/”]:not([href*=“@”]) span::before {
content: "❤ " !important;
color: red !important;
}}
There’s three lists of domains at play here:
* The domains in the first @-moz-document are domains where hearts and stars appear at all.
* The domains in that section’s a.text-info block are the domains that get hearts.
* The domains in the second @-moz-document are the domains where the stars are overridden by hearts.This lets you always have hearts on an instance, even if you’re already on that instance, while also letting you have stars show native accounts elsewhere.
