• 14 Posts
  • 54 Comments
Joined 2 years ago
cake
Cake day: February 16th, 2024

help-circle
  • the main reason is because people don’t know about it

    But you know about it now and you’re still arguing against it.

    it’s an extra thing to remember for little benefit the “only” do a really useful thing that lots of people want.

    The benefit you see in those tags is the same level of benefit that users who use accessibility features get from output and other semantic tags. But your argument seems to boil down to “I dont need accessibility features so i don’t care about enabling them for ppl who do”. That’s very disappointing and continuing this debate seems pointless so i’m gonna stop here


  • Expecting all devs to test their sites with screen readers is unrealistic.

    I disagree with this but its not what we’re talking about. You said output is useless and I’m saying its obviously not. There’s zero cost to using it instead of a div so the only reason not to use it is to purposefully screw users who need accessibility features.

    All those other elements give some benefit apart from accessibility

    Maybe for label but p and h1 - h6 only differ from div in styles, which is another argument in my favor. If you’re willing to swap a div for one of those for visual users, swapping a div for output should be just as easy of a change.




  • They don’t need “powerful ammo”. They’re already rounding ppl up and illegally imprisoning them. And they plan to keep going further; ICE is on a hiring spree right now and just got a huge budget increase. They don’t need valid excuses to be jackboots because they’ll just do it anyway.

    Refusing to use available tools to fight back is ridiculous. There is no “what if” here. They’re already doing it and they’ve made it clear that want to do more


  • If the system flags the wrong person and a witch hunt ensues, it will validate every right-wing persecution complex there is.

    Could you explain your worry further? To me, the problem with AI facial recognition is that a government or company using it has all the power. If they get a false positive, the wrong person gets hurt with no recourse. Civilians can’t do anything detrimental with a person’s identity that’s not already illegal. Cops have been identifiable since they were catching slaves and outside of organized efforts (which this is not) there’s been no issue with thatt.

    Also, it seems trivial to add a step after the system returns an identification that checks if that person is actually employed by ICE. If not, oops it got it wrong; no harm, no foul. Even if it’s wrong after that step, then what? I’ve seen no evidence that ICE agents are receiving anything beyond verbal harassment in the first place (outside of protests, where any hypothetical harm is random and not based on identity)




  • The point I was making here is you start sabotaging & can end up harming people that may have been allies

    How? The call to sabotage was against fascist programs, like surveillance, illegal arrests, etc. How would sabotaging those hurt people who could have been allies?

    Second, the more you start demanding people do what you want else you’ll sabotage, attack them, etc

    That is nowhere near what is happening here. We have a system of laws that is being broken. Nobody was calling for sabotage when those laws were followed. But people who use less aggressive methods to combat fascism, i.e. writing op-eds, speaking publicly against administration policies, leading protests, have started facing punishments. They are preventing the normal exercise of civilian power, so we have to escalate to sabotage or similar actions. That doesn’t make us like fascists because we are not the ones defying and breaking existing social norms and laws. This is a ridiculous argument.



  • so, now, Firefox detects if you are on a page that has search capability

    Didn’t Firefox have this years ago through OpenSearch and Mozilla removed it.

    Moving the shortcuts at the bottom of the URL bar dropdown into a more prominent position

    They’re moving always visible icons into a menu that takes an extra click. Years ago these used to be actual buttons that you could click to perform the search with that engine.

    It’s like they’re bragging about their feature regressions.










  • I didn’t cherry pick a statement. I included the part where they said the very first draft.

    I did fail to explain how its a power grab, but that’s was only because I thought it was a fairly obvious one-to-one point. I’ve also added another example. But lemme try again.

    1. Mastodon has a history of pushing features that affect interop with other implementations without seeking feedback from other implementations or outright ignoring the feedback they do receive.
    2. A member of the mastodon team wrote a FEP to formalize a setting related to search indexing. This was the right way to go about it. yey Mastodon was working with other implementations. But that FEP didn’t receive positive feedback and it seems like it was abandoned.
    3. Now mastodon is trying to standardize something using the ideas from that FEP, outside of the FEP process (which is the agreed upon way to collaborate between implementers).
    4. They’re warning on their site that they have deadlines and may not incorporate feedback if they can’t resolve it without breaking deadlines.
    5. They are under no obligation to incorporate it after their initial draft and, historically, mastodon is unwilling to update their work to incorporate other implementers’ feedback.

    A more collaborative way to do this would have been to seek feedback before making a grant proposal and making the grant proposal jointly with other projects so they weren’t the only ones getting paid for it.