The “guest account” loophole on which nitter depended seems to have been shut off, so nitter servers will stop working over the next few weeks. This means that using Twitter without logging in will be pretty much impossible.

      • maol@awful.systems
        link
        fedilink
        English
        arrow-up
        7
        ·
        10 months ago

        What’s driving me mad at the moment is the plague of bands, artists, organizations using linktr.ee instead of a website (or even if they have a website). That’s what your website is for!

    • self@awful.systemsM
      link
      fedilink
      English
      arrow-up
      7
      ·
      10 months ago

      I maintain that the fediverse should be viewed as a Usenet clone with easier self-hosting

      and therefore it will be the prerogative of one of the big Silicon Valley players to kill it as dead as humanly possible

      • Steve@awful.systems
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        10 months ago

        should make an alternative markup and transfer protocol for fediverse. copy the best bits of the web, but take away the baggage so it’s easier to build new browser engines

        • self@awful.systemsM
          link
          fedilink
          English
          arrow-up
          4
          ·
          10 months ago

          for some folks that’s gopher or Gemini, and I can’t say I disagree with that choice. I wonder how fancy one could get with rendering, within the bounds of those protocols?

          • self@awful.systemsM
            link
            fedilink
            English
            arrow-up
            5
            ·
            edit-2
            10 months ago

            I very briefly fell in love with the idea of a Gemini interface for our instance, but unfortunately it’d be read-only:

            you can’t use Gemini itself to put content into Geminispace. You need to use something else, such as (S)FTP, SSH, rsync, git, a web interface, an email interface, etc.

            (from geminiprotocol.net)

            I’m actually kind of pissed off that that’s where the line is. sessions aren’t what enshittified the web; cookies as an enabling technology for sessions are ridiculously awful and prone to abuse, but they aren’t required for sessions. there’s absolutely a way to do modernized sessions and forms in a privacy-preserving way that’s still incredibly simple. like fuck, the features I’m hoping for are BBS staples that predate the web. why are we fetishizing the brief period before the web was useful?

            e:

            This freedom from the threat of tracking comes with downsides: Gemini has no support for caching, compression, or resumption of interrupted downloads, and as such it’s not very well suited to distributing large files, for values of “large” which depend upon the speed and reliability of your network connection.

            imagine being so allergic to success that you decide your special protocol shouldn’t even be good for piracy due to the fantastic tracking risk of supporting gzip or a seek header