Technology

37742 readers

476 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

291

Twitter API has a list of users who are allowed to use racial slurs (beehaw.org)

submitted 4 months ago by [email protected] to c/[email protected]

58 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 27 points 4 months ago (2 children)

Url does not resolve to an IP address

[–] [email protected] 19 points 4 months ago* (last edited 4 months ago)

I checked too, it's not a valid public DNS record, so then the question is, does Oktas internal DNS resolve this. Even if it does, how does okta even sit in this? Are they the identity provider for Twitter? Surely even if it's identity, it's got nothing to do with content moderation? So many questions.

[–] [email protected] 9 points 4 months ago* (last edited 4 months ago) (1 children)

Odd. I get a full fledged HTML 404 page.

EDIT: https://archive.ph/c49ul

[–] [email protected] 2 points 4 months ago (1 children)

What dns server resolves the site?

[–] [email protected] 3 points 4 months ago* (last edited 4 months ago) (1 children)

I tried to visit the site again when I saw your comment and discovered the DNS record had disappeared between when I wrote that comment and now. Fascinating. It must have been taken down and the change took a while to propagate. Judging by the fact that I could see anything at all before my ISP's nameserver got the memo, the 404 page that was there seems to still be up even though the DNS record that got you to it is gone -- wish I had thought to nslookup it when I still could. If I had to take a guess, though, it probably resolved to the same IP address as the twitter.okta.com domain.

[–] [email protected] 2 points 4 months ago

I'm currently overseas in SE Asia, it resolves to a local address (10.3.1.1) with a cname record pointing to an AWS load balancer with 3 separate IPs through my ISP's DNS server. protected-users.twitter.okta.com still appears across a few different DNS records according to dnschecker.org at the time of my post.