[–] 2 points 9 months ago* (last edited 9 months ago)

According to your logic, I can't blame you for believing that "news/blog posts, documentation, government pages [...] should be as robust as possible", but you also can't blame anyone else for interpreting objectives and functionality differently, and drawing the line elsewhere. Your post is a rhetorical suicide, and there is no point continuing this line of argument

  • source
  • parent
  • context
  • [–] 3 points 9 months ago* (last edited 9 months ago) (2 children)

    Well, if we’ re following my logic, like you claim, then it depends on why the page is failing to load in Firefox: Are you using an outdated version of Firefox or on an outdated system? Is Firefox missing major functionality? Has your admin disabled major functionality in Firefox? Won’t some part of the website load in Firefox and if so, why? Are you using assistive technology in Firefox and if so, is it broken, misconfigured, or does the website not follow best practice?

    If it is for another reason, then it obviously depends on that reason

  • source
  • parent
  • context
  • [–] 9 points 9 months ago* (7 children)
    • outdated browser - your fault, and a foolish thing to use considering the modern, online threat landscape
    • outdated system - your fault, and like above you probably shouldn’t connect to the internet with that thing
    • text-based browser - your fault, and it shouldn’t surprise anyone that websites break when you use a browser that misses major functionality
    • JS disabled by an admin - your admin’s fault. Go complain to them, not to anyone else
    • JS won’t load - depends on reason for why JS fails to load
    • assistive technology - depends on the reason; your assistive software may be broken or misconfigured, or the website fails to follow best practice
  • source
  • parent
  • context
  • [–] 2 points 9 months ago (1 child)

    I use Mega(sync) to keep my various PCs in sync. Before that I used SpiderOak for a number of years, but the service started degrading at some point, which forced me to switch.

    While committing to a git host is not a bad idea, it doesn’t cover all the stuff you might want to sync in my experience

  • source
  • [–] 4 points 9 months ago (1 child)

    He has made a large number of questionable comments, including the argument that the solution to human trafficking includes legalizing child prostitution:

    27 April 2015 (Human Trafficking Act)

    The Senate's Victims of Human Trafficking Act is dangerous in several ways.

    When it talks about having the customs agency do more to enforce "intellectual property", I am sure that refers to something bad. Whenever that term is used, something nasty is afoot.

    The way to protect children from being forced into prostitution is to legalize prostitution by licensed prostitutes. Customers could be required to check the prostitute's license. If the customer fails to check, that concrete omission would be legitimate grounds for punishment.

    Minors should not be denied prostitution licenses in a blanket way, but the state should ask them why they want one and probe their situation, then offer help so they can avoid prostitution.

    https://www.stallman.org/archives/2015-mar-jun.html#27_April_2015_(Human_Traffickting_Act)

  • source
  • parent
  • context
  • [–] 8 points 10 months ago* (last edited 10 months ago) (1 child)

    Most or all of these problems, and several more, are solved by using pre-commit. The author vaguely alludes to having had troubles with tools like this, but that has not been my experience.

    The problem with somebody bypassing the hooks (intentionally or unintentionally) is solved by running the hooks as part of your CI; if you don't allow merges that fail these checks, then people can't skip them. If you also squash merges as a rule, then every commit on your target branch will pass the checks

    EDIT: I'll add that, IMO, hooks should never modify files. They should simply check that your code meets whatever requirements you want your code-base to meet

  • source
  • [–] 7 points 10 months ago

    Well, maybe you’d better wait 10min instead of one, to make sure the led lightbulb heats enough, but still…

    I tested this with a 5W IKEA LED light-bulb, since I was just doom scrolling, anyway:

    • After 1 minute of being on, the bulb was still room temperature.
    • After 10 minutes of being on, the bulb was lukewarm.
    • After 10 minutes of being off, the bulb was room temperature, though the fitting maybe felt slightly warmer. That latter will probably depend on your installation, and how well it is able to disperse the heat.

    This means that the solution either breaks down entirely, or is unreliable, since you are not (reliably) able to tell the first two buttons apart

  • source
  • parent
  • context
  • view more: ‹ prev next ›