7 comments

  • rvz an hour ago

    This was obviously going to happen once Nitter got an immediate C&D.

    It just means that it will happen to these alternatives as well and the lawyers have all the money from X Corp to do just that.

    These open source projects circumventing X for free, unfortunately have zero chance in fighting these legal takedowns.

      flotzam an hour ago

      Hoping we'll see more resilient development/hosting emerge

        toomuchtodo an hour ago

        Probably the best use case for onion routing and IPFS. Each X URL gets a content addressable IPFS URL, served via an onion site that should be hard to take down.

        Browser->Tor Onion site->IPFS as storage system pull through cache->X

          flotzam 21 minutes ago

          Or just a .onion for the frontend server + another server at some clearnet domain proxying it to the normies (until taken down and replaced with the new one) would probably work fine. The hidden server can even terminate TLS with a valid cert for the clearnet domain.

          The .onion could host the code forge too, but Tangled (ATproto) would be poetic justice.

  • ChrisArchitect an hour ago

    Related discussion and predictions (2 days ago):

    https://news.ycombinator.com/item?id=49449576

      flotzam an hour ago

      Seemed worth a new post, now that they actually killed it today :(

      Is there any frontend still standing?

        zImPatrick 19 minutes ago

        Nitter itself is still fine, there are like 2 public-ish instances I‘m aware of but I think people should go out and host some in more private communities/run one over Tor or something