101
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 May 2025
101 points (97.2% liked)
Fediverse
33766 readers
101 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
founded 2 years ago
MODERATORS
Voting, lol. Kinda important.
Dropdown menus. They're not really needed but life sucks without them.
Can't manually switch between dark and light mode (only automatically based on browser settings).
There's probably more but I haven't seriously tried to use PieFed for long without JS. Fundamentally it's built HTML and CSS first, with sprinkles of JS added on for funsies rather than the modern way of being all about JS.
You could support this by making vote buttons submit a form if JS isn't enabled. (That's what mlmym does.)
Hmm... There are some pretty nifty things you can do with a hidden checkbox, label, and some clever CSS (e.g.
html:has(#element:checked)
+ CSS variables -- though FYI:has
is baseline 2023.)Making it persistent would require some more effort -- e.g. form + cookies + server side style sheet selection, most likely. mlmym lets users change their theme w/o JS by submiting a form on the setting page. I'd have to think a bit if there's a good way to make it persistent across multiple requests for logged out users with a CDN caching things in between though...
Doesn't actually work for me in a FF138-based browser w/ JS blocked via NoScript -- I always get light mode despite having a dark mode preference set. (Where do you have your
prefers-color-scheme
media query?)Also, FYI I had to manually override font restriction -- otherwise all your buttons end up as tofu characters. (I think NoScript is being kind of unreasonably strict there by blocking first party fonts.) That's a papercut kind of issue, but figured I'd point it out in case it might save you some debugging time if you get confused NoScript users in the future.
Yeah I think it'd be worth getting the voting buttons working, those are pretty key functionality.
The icons being stored in a font is kinda problematic (some browsers choke, large font file) but on the other hand it's so great being able to set the color of them in CSS, which I found difficult when they are a SVG.
Yesterday:
Today:
You don't need JS at all if you get a bit creative with the CSS.
That way is old and busted, here's the new hotness (anchor positioning).
Yeah. But in this case the Topics menu can be quite heavy as it lists every community that the current user is subscribed to. Instead of generating that menu (and sending it to the client) on every page load, when it probably won't even be used, PieFed makes an ajax call (only possible with JS) to retrieve the topics menu when it's clicked. Same for 'Feeds'.
This cut the amount of HTML being sent to the browser by around 50% (depends on how many communities you subscribe to but PieFed makes it extremely easy to subscribe to dozens of communities with a single click so many people have hundreds) and eased load on the server too. Some of the more under-powered instances run noticeably faster now.