Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TW
TweedyImpertinence @kbin.social
Posts 0
Comments 3
I made the mistake of checking Reddit (using my last few days of Apollo) and came across a complaint about Lemmy that flabbergasted me
  • In theory, custom CSS is a neat idea, but it’s typically a one-and-done project that is difficult to update, and in most cases, an inadvertent “fuck you” to users who rely on the built-in accessibility of native elements.

    Also, custom CSS by users is effectively them placing a code freeze on the frontend.

    If a better way of doing things comes along (which is a given in the tech world), you either improve the core site CSS and break the customizations (and hear all about it from your users); improve both (which is a ton of work with no tangible difference in what’s rendered to the page), but now the people who made those customizations need to up their CSS game (which rarely happens); or you do nothing and let entropy run its course and do a total rewrite some day. The last one is literally what happened with new Reddit.

  • I made the mistake of checking Reddit (using my last few days of Apollo) and came across a complaint about Lemmy that flabbergasted me
  • I would love to see the Settings menu and sections achieve the level of UI customization as the Apollo app.

    Instead of gripes like “too much whitespace” or “needs more rounded corners” or “text is too small” and committing to a single combination of all these complex conditions as “the official design,” every user should be able to customize the UI exactly how they like it.

    I would love to disable everything but text on the page: no avatars; no scores; no icons; no buttons except “Post,” “Reply,” and “Report”; light/dark mode inherited from system/device preference. That’s it. Boom! Done.

    But you need robust HTML and CSS for this, and it is insanely difficult to find frontend devs who actually truly deeply know HTML, CSS, and JS. There are plenty of frontend devs making nice-looking sites, but those sites are typically unmaintainable in terms of CSS, are full of inaccessible nested tag soup in terms of HTML, and are locked into unremovable technical debt from the get-go via JS frameworks that will inevitably go out of vogue (as they all do).

    Something as simple as native aspect ratios for thumbnail images is broken on kbin, so we immediately know that the HTML and CSS for this site are not in good shape, and until those things are addressed with growth and change in mind (and not just closing out bugs or hitting a launch date), it’s all going to fall apart eventually.