Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


About colonel_mortis

Contact Methods

Profile Information

  • Location
    UK, centre of the observable universe
  • Gender
  • Interests
  • Biography
    ┌ I was born.

    ├ I found LinusTechTips.
    └ Now.
  • Occupation
    Nyan cat herder


  • Display(s)
    Dell U2515H 1440p Monitor
  • Operating System

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I think this is the same root cause as Which should be fixed here in the next update, probably within a few days.
  2. All three of those should be fixed in the next update - looks like we were missing one line to enable the lightbox.
  3. This was a deliberate decision because the old UX was pretty terrible on statuses with more than a few replies, and I suspect that it's something that you will get used to pretty quickly.
  4. It should have applied with the status update changes today actually, but unfortunately you might need to clear your cookies (or if your browser lets you be granular, just local storage for LTT) for it to take effect. Why would that be useful? To avoid temptation to look at it? Surely there are reasons when you'd legitimately want to see the post though?
  5. Basically, computing the correct size of images before they've loaded, to be able to figure out the show more button, and making that solution work on all screen sizes, is hard, and the IPS solution doesn't work properly. The only thing I can do for now is turn it off entirely, but I'm not sure if it's worth doing that.
  6. I don't think making it entirely bidirectional would work, because then the member who was ignored has no choice in whether they can see the ignorer's posts. I'm not sure how I feel about making that information available to the ignoree anyway - that feels like it could end up increasing tensions and disagreements, and generally making people less cooperative. I do see the benefit of not having them reply to you, but would it help if instead you just didn't get notified about having been quoted if it was by someone you ignored?
  7. I think this particular issue (notifications for status updates posted by people who you follow) should now be fixed, although I think there may be unrelated bugs for other types of status update notifications - please do let me know if you run into those. (I have seen a case that I can't explain where I didn't get notified about a reply to a status I was following, and in the beta there was a couple of reports of issues when posting on someone's profile.)
  8. Just testing something, please reply if you want to help

    Edited by colonel_mortis
    What I typed didn't make sense

    1.   Show previous replies  25 more
    2. PCGuy_5960


      This does not change the fact that in Australia there are 48 million Kangaroos and in Uruguay there are 3,457,380 inhabitants. So if the Kangaroos decide to invade Uruguay, each Uruguayan will have to fight 14 kangaroos.

    3. colonel_mortis


      10 hours ago, WereCatf said:

      I wonder how long we can keep this going before mortis gets tired of the spam and takes out the Banhammer(TM)

      Now that notifications get grouped together and you can unfollow, hopefully it won't have to come to that.

    4. Moonzy


      trying to embed a reply timestamp:

      yee it works

  9. It's not a technology problem, it's just that compilers remove information. There may be advances in decompilers that produce more likely code, but you will never be able to take Windows (or something considerably less complex) and get the original code, or in all likelihood anything resembling the original code, back. If you take these C programs: int addOne(int input) { return input + 1; } int getValue() { return addOne(5); } int getValue() { return 5 + 1; } int getValue() { return 6; } Most compilers set to any level of optimization will
  10. For the average internet user, benchmarks do show that is fastest, but it will depend on your individual circumstances. The times involved there are significantly less than the duration of a blink (a blink is 100ms+), so there is no point agonising about which is going to shave off a couple of ms though. I would recommend trying Cloudflare's (, and if that doesn't work for you for whatever reason (for example if it's impacted by the same issue that caused LTT not to work) then you can try switching to Google's ( or another alternative instead.
  11. I would suggest just changing it, and not worrying about the couple of milliseconds difference that will occur, but if you really want to benchmark it you could try something like namebench: https://code.google.com/archive/p/namebench/downloads There are setup instructions on, but yes you set those, using for the primary and for the secondary if you are using Cloudflare's, and for Google's.
  12. This is intentional, and consistent with how other types of content work - when you post a new topic, it takes you to that topic, etc.
  13. Status update improvements are now live. Hopefully this marks the end of me posting status updates about status updates.


    If there are any issues, please post them in Forum Bugs and Issues.

    1. Lurick


      Where can I find a list of enhancements/change log so I make sure if I report something it's a bug/issue and not a feature?

    2. colonel_mortis


      25 minutes ago, Lurick said:

      Where can I find a list of enhancements/change log so I make sure if I report something it's a bug/issue and not a feature?

      It was a ground-up rewrite, but report things that seem wrong (as opposed to different).

    3. Den-Fi


      Bwahahaha. I thought I was on the  beta for a moment.
      Loving it so far.

  14. If it gets noticeable slower (or if the same blip that is causing the forum to stop working also causes your DNS to stop working) then I'd suggest trying a different one. If it gets faster, or even if it seems about the same, then I'd suggest keeping it.