Feature requests, bug reports, etc

I understand, however in my head it doesn't seem like such a major case.

All posts are now marked with numbers and have their own URL. That way a small script, or maybe even a cookie could remember the newest post when reading a topic.

I'm thinking every user has a script somewhat like this:

"flagged as unread" happens
If "topic" is "unread"
//nothing
else 
do "copy URL of last post" and "paste as topic URL for user:XXX"
end

The script should run every time a new post is sent in.

Let it be said that I have very little skill with web development and I might be thinking all wrong. Also, I am just stressing my personal opinion that this function is very important for the flow and navigation of the page.

Edit: uuhm.. There seems to be a problem with the formatting here. I can't do single line-breaks, only double. Both with and without the quote marks.

Edit: uuhm.. There seems to be a problem with the formatting here. I can't do single line-breaks, only double. Both with and without the quote marks.

If you use three accents (these guys: `) before and after code, you can do code snippets. I edited your comment to show you what I mean, that might help?

I understand, however in my head it doesn't seem like such a major case.

It could very well be me overthinking it in Rails-mindset (where you would have unread and read stamps on every single comment), I'll look into using cookies instead.

Problem with cookies though is that it would be bound to one computer. Annoying for those using both phone(s) and computer(s). But it would be a good start!

That way a small script, or maybe even a cookie could remember the newest post when reading a topic.

Actually thinking about this, the easiest way to do it is probably:

1. Capture the number of comments available when I timestamp you visiting a post
2. When that post is updated I'll fetch the number of comments again
3. Numbers are compared and offset to what your timestamp says

So then when you go to an unread thread, I'll push you down to the last comments number + 1, which means you'd start reading the comment you haven't seen yet. This approach also means I can show you a number next to the post title that indicates how many comments you haven't seen yet in that particular thread.

Facebook Connect for registration please! Then you can instantly sign up and starting contributing.

Actually, registration via Twitter might be more useful if it's the case that most users are coming here via a tweet.

Actually, registration via Twitter might be more useful if it's the case that most users are coming here via a tweet.

You're a tweet!

You're a tweet!

I've been called worse.

I've been called worse.

That avatar is bloody mesmerising Alex

Ix - how about instead of upvotes and downvotes, Goals and Own Goals? Or was that an own goal suggestion?

How about a go to bottom of page button at the top of threads? When threads get too long, scrolling can be a pain.

Added badges of doom™

http://www.dialsquare.co/achievements

Very fancy. It'd nice to be have tool tips on them in the user's signature.

Very fancy. It'd nice to be have tool tips on them in the user's signature.

Why do you love tooltips so much.

How do I get my hands on the Eisfeld Award?

Very fancy. It'd nice to be have tool tips on them in the user's signature.

Added normal system tooltips.

An update on embeds slowing the site down in Chrome (this is a bit technical, and is just as much for my own documentation as it is an explanation for those who want one):

The problem is specifically GfyCat. The reason Youtube videos won't slow the site down is because Youtube only loads one low-res image and then you have to click to start it, at which point the full video starts loading. GfyCat embeds are autoplay, and quite massive files as well. Chrome doesn't handle that very well and dedicates resources to loading those huge GIFs/Webms on pageload.

Another problem is that you can't just hide the iframes through CSS, as they'll load in the background anyway (display:none only hides an element, it doesn't stop it from loading into the DOM). You have to remove iframes from the DOM completely for them not to load, or null their src attribute, which is what I experimented with. But if you remove the src attribute, you can't update it at a later stage as the iframe has already loaded.

My initial plan was:

1) On pageload, replace the src attribute of every iframe on the page with an empty tag:

$('iframe').attr('src', '')

2) As the user starts scrolling and "hits" one of the iframes, replace the iframe src with its original value:

var src = $('iframe').attr('src');
var offset = $('iframe').offset().top - 20;

$(window).on('scroll',function(){
  var scrollPos = $(window).scrollTop();
  if (scrollPos > offset) {
    $(this).attr('src', src);
  } else {
    $(this).attr('src', '');
  }
});

But because of all of the issues listed above, this doesn't work. As the iframe has already initiated, it won't accept a new src attribute. Ideally I'd like to force reload the iframe at the point of scroll, but then I run into same source shenanigans.

TL;DR:

There are only two ways around the slow loading:

• Hide all iframes
• Live with it

What is best?

I say live with it.

Added +1 buttons. Right now they're not user limited, meaning a user can give a comment an infinite amount of +1s if he or she wants. This is intentional for now, but will probably change as the user base grows.

I was pushing for this back in the 39t.co days. Smileys with Arsenal players faces.