• 0 Posts
  • 55 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle
  • I think accessibility is widely misunderstood. The way I view it, it’s not only about giving people who need them more ways to access something, but also giving people who want/prefer them those methods as well.

    One example of this is wheelchair ramps. Building the ramps benefits those who need them by giving those people a way to go up/down an incline, but many people use the ramps. The ramps are also for those who would prefer to avoid the stairs.

    Digital tools are another example of this, and a great one. Keyboard accessibility is a must for people with visual impairments, but also a preference for many who prefer not to move their hand to the mouse constantly. Keyboard-accessible tools are almost always a better experience to all users as a result.

    Not building for accessibility is honestly just lazy. It shows that you don’t care about your customers, and you don’t want them to have a good experience. At best, you want to force your experience on them and only your experience is allowed (my biggest gripe with Apple products honestly).

    As for digital art, I’ve seen a lot of what you mentioned, and I think it’s honestly been going on for centuries at this point. It’s problematic, especially because not everyone wants to create art in the One True Manner™ and may want to experiment with new ways to create art, or may want the art as a part of a larger project and don’t really care about the means (as long as it’s ethical).



  • While I agree, it makes connecting to localhost as easy as http://0:8080/ (for port 8080, but omit for port 80).

    I worry that changing this will cause more CVEs like the octal IP addresses incident.

    Edit: looks like it’s only being blocked for outgoing requests from websites, which seems like it’ll have a much more reasonable impact.

    Edit 2: skimming through these PRs, at least for WebKit, I don’t see tests for shorthand IPs like 0 (and no Apple device to test with). What are the chances they missed those…?













  • For library code - yes, you’d usually want to direct users to the correct way of using the library, so you’d be more likely to come across fallible build functions or a bunch of type parameters to constrain when it can be called.

    For applications - honestly, it’s your code, so do what makes sense to you. Using a build function can help you ensure your settings were fully configured before using them, but it’s up to you if that’s the direction that makes the most sense to you. One benefit is you only need to perform the check once, but the downside is having another “built” type that you need to keep in sync with the original type. You can also look at libraries like derive_builder if you want to have your builder generated for you to avoid needing to manually update two separate types.