Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Saturday January 25 2020, @09:07PM   Printer-friendly
from the should-have-objected-by-writing-in-runes dept.

Rock Paper Shotgun reports:

As reported by PennLive, the U.S. Court of Appeals for the 3rd Circuit has affirmed the district court's decision that a Pennsylvania man was not discriminated against by being "muted" in an online game.

Amro Elansari filed his original complaint against developer Jagex in July 2019, claiming they "violated his rights to free speech and due process of law." The suit was dismissed by the district court, a decision that has now been upheld by the appeals court for the 3rd Circuit.

Elansari was "muted" in an unnamed online game in March of 2019, according to his "largely handwritten" complaint, says PennLive. Given his suit names Jagex and that Elansari "claimed he had 2,000 hours invested in the game when he was booted out," it seems to follow that he had his account muted in some version of RuneScape.
...
The appeals court says that Elansari has not named a "state actor" for his Fourteenth Amendment claim. His complaint under Title II of the Civil Rights Act of 1964 was also dismissed with no evidence of a "public accommodations discrimination."


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Grishnakh on Sunday January 26 2020, @05:52PM (1 child)

    by Grishnakh (2831) on Sunday January 26 2020, @05:52PM (#948931)

    Yeah, I keep forgetting that there's actually people who use their phones to type comment on message boards like this. Personally I can't stand it. Typing a few sentences on a phone is an exercise in frustration for me because it's so slow, and autocorrect is so horrible. I'm debating turning off autocorrect completely and seeing how that works out, but it is really helpful for fixing common mistypes (which are so easy because the screen is relatively small, even on my phablet-sized phone), but when it screws up, it's such a PITA because it frequently won't even allow me to type something correctly without continuing to type more stuff, then going back and correcting the "autocorrected" word. It's amazing that after well over a decade of smartphones being commonplace that they haven't figured out how to make autocorrect work well yet.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by barbara hudson on Monday January 27 2020, @03:18AM

    by barbara hudson (6443) <barbara.Jane.hudson@icloud.com> on Monday January 27 2020, @03:18AM (#949147) Journal
    I tried to disable autocorrect on my Android, it said it was off, it lied. So now I'm stuck with autocorrect on iPhone, BUT while it insists on changing "fuck" to "duck", it has no problem suggesting fucké after I typed it once and clicked on it in the list of suggestions. Same with blockquote after typing 3 letters.

    There's always a way to game the machine. Even one that's all fucké.

    --
    SoylentNews is social media. Says so right in the slogan. Soylentnews is people, not tech.