1. 7
  1.  

  2. 4

    Before I found the twirssi I couldn’t find a client I didn’t hate. It will be unable to replicate this display, so I suppose it will be banned in 6 months.

    The new policies strike me as really alienating to the kind of alpha nerd that Twitter cut its teeth on (note: not me, here). Maybe they’re eating seed corn. Maybe I just have nerd migration on the mind because I’m on lobste.rs instead of HN. :)

    1. 1

      I had never heard of twirssi before but it looks interesting. I probably fall in the very high volume twitter user who follows 2000 users and uses Tweetdeck with six columns. That’s probably a difficult use for twirssi. Apparently Tweetdeck would not be affected as it’s owned by Twitter.

      The biggest casualty of this type of thing for my uses is Tweetbot. I’ve been using it almost since it was launched on both the iPhone and iPad. The Mac version is coming along nicely as well. I would love to see Tweetbot work with Status.net or Identi.ca or some other new implementation of the same idea.

      1. 2

        What are columns in TweetDeck?

        If they let you split up tweets to different places, twirssi does this; I have windows dedicated to friends, coworkers, high S/N, particular searches, and one big noisy feed for skimming the rest. Though what interested me first was the no-frills interface and plugging into something that’s already open all the time for social stuff.

        1. 1

          That might work then. That’s pretty much exactly what TweetDeck columns are. I use Twitter lists extensively so I can watch what I really want to know about without seeing all 2000 Twitter users I am following. I’ll have to investigate twirssi further then. It might be an interesting solution and would also work on OpenBSD unlike TweetDeck (except thorugh maybe Chromium??).

    2. 2

      I wonder how this will affect (if it does) Twitter bots – they don’t display tweets to end users, in general, except perhaps in log messages.

      1. 1

        This might be a good reason to investigate something like Status.net. Perhaps a client like Tweetbot will be updated to work with other networks like Status.net.

        1. 4

          I was actually just looking at their Wiki after reading this article. I only ever use Twitter through den.im and if I ever open it up, I don’t want to worry about Twitter revoking my application key because I’m not displaying Tweets according to their specific requirements that day.

          I looked at identi.ca which is apparently a free network running on status.net software, since status.net is now trying to target companies (MySQL, anyone?). That doesn’t really seem to be much better than Twitter because I’d still have to use their servers to host things. I want to host my own data and have other networks connect to me when they want my data, just like e-mail or XMPP. I don’t want to run status.net’s giant PHP server just to host one user, either. Where are the other implementations of their federated protocol (OStatus?)

          1. 3

            I’ve implemented OStatus over at http://rstat.us. It’s up on GitHub: https://github.com/hotsh/rstat.us

            1. 1

              Wonderful! That’s perfect. I just came across rstat.us a few days ago. I’ll have to start working with the code on a dev box and see how it goes. Thank you!!

              1. 2

                Awesome. We also broke all the OStatus stuff out into gems, so if you use Ruby, you could also write your own stuff to integrate with it.

                Let me know if there’s anything I can help with.

                1. 1

                  Excellent! Thank you! I’ll let you know!

            2. 1

              I haven’t investigated the size or scope of the status.net software but something that’s compatible with OStatus (or whatever it’s called) that runs on OpenBSD with nginx and not must else would be great. I am also a firm believer in running everything possible with my own infrastructure. Have you investigated the protocol at all?

              1. 2

                The protocol is PubSubHubbub with a custom XML envelope inside. Also Salmon and Webfinger.