[–] 3 points 7 months ago (1 child)

I don't find it super easy to read. Even white on white is somewhat readable, but the black tree part on the left is particularly hard to read. Certainly not scan-readable / fast, like I would be able to read normal text.

  • source
  • [–] 5 points 7 months ago (1 child)

    Seems you don’t know how anything on Linux

    What makes you think that is what they think? They referenced other people. They didn't make any claims themselves or made any indications that they agree with those "flipping out" (who misunderstand).

    I read it as the opposite. They know and criticize those who don't and flip out because of that.

  • source
  • parent
  • context
  • [–] 1 point 7 months ago*

    Git push to Forgejo -> automated build, package, and deploy pipeline -> use secured credentials to upload via scp or ssh or sftp

    Alternatives to copy-upload or upload-package and then extract via command is stuff like rsync (reduce redundant, unchanged file uploads) or a simple receiver service (for example REST endpoint that receives a package with an identifier key and secret key, that it extracts to a configured target folder).

    What solutions are simplest or easiest depend on the target environment, and how much of it you control. If you host the website on Forgejo itself it's as simple as pushing the static files into the corresponding pages branch.

  • source
  • [–] 1 point 7 months ago*

    It falls back exactly the way I think.

    This article talks about flashes, and proceeds to say fallbacks should be defined. It explains how fallbacks work, but fails to describe what actually leads to the flashes, how fallbacks get replaced, and fails to say anything about solving that flashing issue they talk about.

    Defining a more similar fallback font may reduce the issue visually, which is not mentioned either, and either way is not a solution for the flashing.

    Dunno why one would expect lower precedence CSS rules be integrated into more specific CSS rules without explicit "inherit". That's not how CSS works. Dunno if that's a common enough misunderstanding to warrant a "not the way you think it is" title.

  • source
  • [–] 1 point 7 months ago

    Not the first time I think damn, let me check what my legacy projects have, and it's several versions higher.

    Such long term support is a rare but very valuable thing. I'm glad my legacy is not that legacy/far behind, though.

  • source
  • [–] 11 points 7 months ago (4 children)

    Possibly AI company crawlers. When they came up there was a lot of bad publicity and reports of actively malicious and toxic crawling behavior, including ban evasion.

    You can think about locking some url paths behind valid login sessions, or use a proof of work proxy guard.

    Anubis is the popular tool for that. I've seen maybe three alternatives, one of which from Cloudflare.

    See also related Codeberg ticket (Forgejo instance) https://codeberg.org/forgejo/discussions/issues/319

    If you search, you can find various blog posts about these issues. Not just when Forgejo.

  • source
  • [–] 6 points 7 months ago* (2 children)

    Meh.

    I have been using vertical tabs for a long time, through Tree Style Tab (Firefox Extension), which has the additional benefit of tree hierarchy.

    I don't see a "everyone should use them", though. People have different usage patterns, number of tabs, amount of parallel or queued work and concerns, or ability to clear out tabs on session end. Many people prefer classic horizontal tabs - whether as a deliberate decision or not.

    I certainly prefer horizontal tabs, and by a lot. But I don't think it's the best layout for everyone and every usage pattern. It's good that we have the choice of alternatives.

  • source
  • [–] 3 points 7 months ago

    Interesting, clever technical workaround for (potentially) real user benefit. But still, they should never do that. Working around safeguards and system component borders for user convenience is a very bad idea and practice.

  • source
  • view more: ‹ prev next ›