Threads for fgutz

  1. 3

    I removed Disqus because I might have gotten 3 comments in total during the time I had it.

    If someone wants to discuss something on my blog, they can DM me on Twitter ;)

    1. 1

      I wonder if it’s possible to leverage Twitter as a sort of comments section. Once you publish an article you post a link on Twitter, then embed that tweet into the page along with its replies.

      Of course embedding a tweet will come with its own bloat which doesn’t solve OPs issues (including privacy), but it could be an interesting alternative to using Disqus.

      It’s probably better to just link to the tweet and have people go to Twitter to respond.

      1. 2

        I thought about this, and I think the only suitable way of doing it, would be to have a script to add in each blog page, that loads a server-side program.

        The deploy script would publish on Twitter/Mastodon/others and save the social network links to a database (like in a text file in the blog repository itself, for easy backup?) so that the server-side program is able to check and load comments on the blog page.

        But you’ll have to deal with moderation. That’s why I didn’t code that although I got the idea. If you want to accept or refuse comments before they are shown on your blog, you can also use that time to copy and paste comments from these social networks manually, or use a script just for that task.

        1. 2

          You don’t control twitter, and you shouldn’t trust twitter not to censor your comments about your blog, or other people’s comments about your blog, on their platform. Twitter does this all the time for all sorts of reasons. This policy also forces any potential commenters to have a twitter account, which means they have to either give twitter their phone number, or go to some effort to spoof one. There was one time when I wanted to talk to someone I knew from university years ago after seeing a blog post of theirs. Their only public contact information was twitter, and trying to sign up for twitter in order to send them a brief hello was how I discovered the phone number thing.

          1. 1

            The requirement for having a Twitter account is a valid concern.

            On the other hand, anyone who allows completely anonymous comments is asking for trouble. When I used Disqus, commenters had to have a Disqus identity (which is separate from an account, you could auth with other services - part of Disqus’ value-add).

            Twitter is a bad example for this, for many reasons, but I personally would not have any problems enforcing that commenters to my blog had to have a Github account, for example. This is similar to my personal informal requirements for extending a Lobsters invite.

            1. 2

              Just remember that any external service that you outsource your commenting authorization to is an external service that could screw with your potential commenters in any way they like. If you believe that Github will always make exactly the same decisions about who they will allow on their service as you will about who you will allow to comment on your blog, then you have more faith in Github than I do.

          2. 1

            Maybe… with some hacky plumbing that would be removed the next time Twitter decides to change their API…

            I guess an IFTTT to publish a tweet, then a link to that “discuss this article on Twitter!” would work, for some values of work.

        1. 24

          When did we lose our way? When everything became about making money. I always describe my developer burnout to folks, and I always tell them “I got into it because it was fun, and a creative outlet.” Maybe I just need to start making geocities sites.

          Though, I don’t think we need to bring back jquery.

          1. 14

            The issue is saturation. If you want to have fun then develop for a less popular platform. There’s a ton of good, fun platforms to develop for with solid commuities surrounding them. You just have to find them.

            1. 2

              Agreed. Maybe discovery isn’t as easy but even on the current platform there are fun and interesting sites.

              I also like to wax nostalgia on the internet of old but I do not want to bring it back. Find the new weird, don’t try and recreate the old weird

              1. 4

                That’s a good point. Find the new weird. The internet is too young for us to go back to old weird already

                1. 5

                  The new weird will probably look similar to the old weird (minus specific format-related glitches) though.

                  Like, the new weird will probably use color and animation for expression, offend the sensibilities of people who expect the web to be ‘readable’ (i.e., for artistic statements to obey the same laws of propriety as marketing and documentation), contain surrealistic and scatological humor, and occasionally be intentionally annoying or hostile. These are all things the early web has in common with dada, outsider art, lettrism, oulipo, faxlore, etc. In other words, it’s part of the general tradition of democratized creative work, and one of those things that gets axed as soon as the work is coopted by the Spectacle.

                  The new weird will break in different ways. We won’t use gifs because it uses less bandwidth to store actual videos these days, so we won’t have artifacts from 8 bit color or from transparency being inconsistent in a single frame or from the size changing for one frame (unless we go out of our way to reproduce those things). Hosting is cheaper per byte, so we won’t have failures related to files being deleted because we went over our megabyte of storage. We’ll have new and exciting failures.

            2. 10

              I’m building a greenfield web application with Haskell, Elm, Nix, Event-Sourcing, aaaaaaaand… jQuery!

              Nothing wrong with it :)

              1. 3

                I’m using intercooler for most stuff that I can these days, and it sits on top of jQuery (or zepto). So it’s definitely not going away for me yet.

                1. 2

                  Ohh nothing wrong with jQuery ;) I guess I felt real good coding in javascript without having to include it!

                2. 3

                  I use jQuery every day at work. It’s pretty funny considering the code base is only 3 years old or thereabouts. The stack is definitely considered “old” by some. I try to make the best of it. Sometimes I’ll just write plain JS and it feels oddly satisfying.

                  1. 2

                    “Writing is like prostitution. First you do it for love, and then for a few close friends, and then for money.” - Moliere.

                    1. 1

                      ‘bring back’? It was never gone…

                      1. 1

                        yeah that’s true. one of my clients uses it in their front end stack. though whenever I work in a more modern codebase we end up not bringing it in.

                    1. 2

                      I noticed this the other day with keepass2android because it offered me the option and I love it