Jump to content
SiouxSports.com Forum

jimdahl

Moderators
  • Posts

    4,545
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by jimdahl

  1. It's a little confusing, but the behavior differs based on what screen you're on: If you're on the front forum screen (that lists hockey, football, etc...), then clicking on the title of a thread will take you to the last read post in the thread. If you're in one of the forums, so you see a list of threads, you instead have to click the little dot or star to the left of the thread (but if there are no new posts in that thread, the star or dot won't appear). If you think it might not actually be remembering what you've read, a way to test that is clicking "unread content" in the white bar near the top and see if it lists anything.
  2. Ok, I found it. Known bug, will be fixed in next version. Sorry about that. https://community.invisionpower.com/4bugtrack/active-reports/417-public-poll-does-not-show-voter-name-r10042/
  3. It's actually slowed down a lot... the first day (when we were unaware) something like 10 came through. Since then we've had 2 make it through, but one was at like 2am CT so it took a few hours to catch. I try to strike a balance between making it accessible/friendly to new users, while keeping the machines out. Here's what I've done so far: New registrations require the industry-standard reCAPTCHA (identifying photos) to prove you're human New registrations require a valid email address (confirmed) New registrations require answering a custom question unique to this forum, to stop us from being affected by shotgun attacks against numerous forums We use a third party spam service that will catch any email/IP used for registration across a large number of forums Obviously they're still slipping past that occasionally, so for the short term I'm going to have all new registrations go into a queue where I have to approve them manually. That will slow down new registrations a bit, so I'll turn it back off once the spammers have settled down.
  4. jimdahl

    New Goalie

    While we all agree that we need someone other than Sedevie in net, bumping like this clearly just creates confusion. Please don't do it.
  5. I'm on it And for those who reported it right away, thanks! It really does help bring it to our attention ASAP.
  6. I agree, I can't see them either. Will look into it.
  7. UND's success on the ice this year has attracted international attention!
  8. Oh, yeah. It's actually been that way for a long time. The author is locked out from editing after 24 hours (on the theory that it creates confusion to edit a post after it's been read a lot and there have been lots of replies). I have no problem tweaking it, but I thought 24 hours was pretty generous. How would you prefer it behave?
  9. You mean for embedded tweets? They should convert from URLs to live tweets when you hit post. Until today, there was a bug that prevented that from happening if the tweet URL wasn't on it's own line. That should now be fixed.
  10. Yep. My guess is extortion attempt. This sort of attack is not cheap. I assume they wrote the network provider and offered to back off for $$$. That the network owner refused and instead tried to work around it is why I can't be too mad about the down time.
  11. Though SiouxSports.com has been happily chugging away, the owner of the network that sits between you and siouxsports has been under a significant attack that has limited everyone's ability to access the site from the outside. It's a pretty significant provider, hosting something like 500,000 sites, so they've been working hard to work around the attacks. Hopefully things will stabilize soon. For techies interested in the gory details, you can view their updates on the situation here: http://status.linode.com.
  12. URL is same as it has always been -- http://wiki.siouxsports.com. Link is at the bottom (in the green footer) of the main pages. You're absolutely right that the fans of the wiki would be unhappy about that, in that it's a serious deemphasizing of it. In the earlier drafts I had actually dropped the wiki entirely, because it's usage is so low, but people emphatically assured me that they really wanted it.
  13. Just take the URL to a tweet (e.g. http://twitter.com....), and paste it into the editor. If you're having troubles getting the link to a specific tweet, hit the "...", click copy link, and then copy the link to your clipboard (Ctrl-C on windows, Cmd-C on apple).
  14. To the contrary, there's now native support for fully functioning (e.g. likes, retweets, follow) embedded tweets. Just paste in the link.
  15. Fixed. Given that it doesn't work in your usual browser, but does when you switch away to a less common one, I'm guessing that this is a browser cache issue as I described above.
  16. You don't a "Theme" dropdown at the bottom of the page? (right next to the Privacy Policy)
  17. Most of the problems (apparently missing functions) are due to people having cached icons from the old system. Clearing your browser's cache would fix it. So would a forced reload (holding Shift or Control while pressing reload on most computer browsers).
  18. Yeah, that's the biggest complaint I've seen on their support forum (which I've been watching closely to decide when to jump). They claim these "streams" are much better because you can set up streams other than just unread. But, I'm certainly not used to them yet. Made me wonder if this is them dipping their toe in the water to consider moving away from a traditional 90s era paginated forum to something more feed-based like Twitter or Facebook.
  19. I installed a notable update to the forum that included a new version of the editor. Hope this helps with some of the editor problems people have been having, it's certainly worked well for me so far! (the red quote line is gone!) However, given that it was a significant update, I'm sure there will be some issues. Let me know of any problems.
  20. Yeah, I already have a few of those locked up from when I thought I might make a change back in the no-nickname days. Definitely a possibility if people stick to calling us "North Dakota" more than "Fighting Hawks".
  21. I'll definitely get the update on here sometime during the break. Lots of changes to the editor, so hopefully more problems go away than are caused Is your zoom issue all the time, or just sometimes? I see it happen sometimes when someone has embedded non-responsive content (e.g. a large image).
  22. There's been a significant update to the editor available for a few weeks, but I'm always hesitant to jump on the first release. Will probably switch to it over the Christmas break, by which time it will probably be on the 3rd or 4th iteration.
  23. I was trying to put together a rebuttal post about how Santiago was #4 in I-AA with 1459 yards rushing, and intended to compare him to the top NDSU rusher. Unfortunately, they only listed the top 50, so no NDSU players were listed. http://www.ncaa.com/stats/football/fcs/current/individual/469 But, you're right, no one is disputing that the NDSU defense stopped UND cold. But to question whether Santiago is a top rusher just makes you look silly.
  24. Ok, I'll try making it unlimited and we'll just adjust later if it turns into a problem.
×
×
  • Create New...