Jump to content
Invision Community

blair

Members
  • Content count

    611
  • Joined

  • Last visited

  • Days Won

    1

blair last won the day on November 4 2010

blair had the most liked content!

3 Followers

About blair

  • Rank
    Community Regular
  • Birthday 03/13/1966
  1. Grinler, I don't plan to upgrade before 4.1.1 at the earliest. Hopefully they won't throw me an EOL curveball prior. I'm guessing you haven't read much about the performance issues with 4.0? Because emoticons are one tag. Bbcode had opening and closing tags. E.g. code /code
  2. @Ralph H. Would you agree that you should be able to create a list of pros and a list of cons at PHPBB.com, copy and paste it here and retain the formatting? Because you can't and that's but one example. What about the same list created here and copied to PHPBB.com... Again you can't. What if you had a catalog of replies, and you never knew what would work and what wouldn't with each new release of IPB? That's the dilema faced by some communities. Just because the problem didn't affect you, doesn't mean it's not real.
  3. Flash is a bad analogy. Bbcode is neither a resource hog or security risk. It has much more common with HTML. Just as HTML is crossbrowser, bbcode should be cross bulletin board. I should be able to format a post using notepad or a third party code generator and paste that code into any bulletin board and expect consistent results. I frequently use IPB, vB, PHPBB, Wolflab and Xenforo. iPB is the only one consistently breaking bbcode. It's not like we're asking for support of an edge case. We're asking bulletin board software to fully support bulletin board code (bbcode). Actions speak louder than words. How about a release version that doesn't break bbcode? Sure WYsIWYG is sexy, intuitive for new users, and meets the needs of 90% of posts. But if you have a community more than a few years old with decent views, you'll soon learn the posts that are generating the traffic are often a how-to guide, well maintained list, or other complex post generated by a power user, who used bbcode. The tech industry is littered with corpses of companies and communities who ignore their power users. I was actually hoping IPB4 would use a modular editor plugin. So you could chose from the default WYSIWYG editor, a third-party WYSIWYG, or something completely different like bbcode or Markdown. If you chose to put your head in the sand, and pretend there are no communities outside of yours, and no community software outside of IPB, then yes iIPB's WYSIWYG editor is perfect for you.
  4. Embrace email

    Don't be shamed. It appears well done. I just wish it were a core feature of a suite interested in building community. And it is only one of my three suggestions. In case you're looking for future enhancements, the stack exchange and discourse folks do an excellent job.
  5. Embrace email

    We have email notifications of reply. What we need is reply via email, submit topics via email, and a weekly email digest of highly rated and new content. Most people want to know what's new. Be proactive and send it to them. People enjoy mailing lists. Hard to appreciate with new forums, but it scales with size. Some will be concerned about creating content via email and losing pageviews, but that's unwarranted. New user generated content is far more valuable than a page view.
  6. ipb 4 seo?

    [sarcasm] Except for hierarchical URLs [/sarcasm] Add or remove sarcasm tags depending on whether you follow @Charles.
  7. profile privacy in IPB 4

    As a forum user, I'd hate to see privacy settings anywhere near as complex as Facebook. As an admin, I realize forum profiles are mostly worthless. I don't show them to guests. I'd like that to change. Facebook, LinkedIn, and many others have built businesses using user profiles. There's obviously room for improvement. Maybe in 5.0?
  8. URL Enhancements

    Microsoft's Community does something like this: Windows | Windows 7 | Repair and Recovery becomes: answers.microsoft.com/en-us/windows/forum/windows_7-system/ Windows | Windows 8.1 | Repair and Recovery becomes: answers.microsoft.com/en-us/windows/forum/windows8_1-system/ Windows | Windows 7 | Devices and Drivers becomes: answers.microsoft.com/en-us/windows/forum/windows_7-hardware/ Now say you're searching for an IRQL error. The post title won't likely include the Windows version, or whether it's hardware or system related. But the forum name AND URL help narrow the search. I wonder why they left "forum" in the URL? I can't imagine there are many forums with a subforum as deep as the example, but having an option to define the forum slug would be an improvement over the generic "topic". A Bing search result: If I add "hardware" to the query, I get different search results because of the FURL (not forum name):
  9. URL Enhancements

    Sorry I'm late to the party. Stumbled across this topic searching for something else. 1) CSEO was no vBSEO, but it was ahead of its time, and most users saw very good results. It used a default FURL e.g. tld.com/community/this-is-a-topic-1234.html. They never had a hierarchical URL. They also had other a few URL options, stop words for keywords/URLs, strip session IDs, etc. Another option they had was transliteration, or custom FURL. For example, if file names are important to your site, you could replace "." with "-" in the URL, instead of ignoring them. It also reversed page titles (board title at end) and had relevant similar topics. Don't underestimate similar content. Of course, a lot has changed in the SEO world since then. 2) If you've ever migrated a forum, or wanted to migrate a forum to another software, topic ID is critical. Why migrate? Don't look any further than vB5. Removing topic ID doesn't offer enough benefit to justify the loss of migration options. If IPS wants to lock in users, get rid of topic IDs (please don't). 3) Don't underestimate speed. While server hardware is cheap, a faster site will win the SERP (everything else equal). Even if Google has oversold the performance/SERP benefit, performance will always be important. 4) Finally, no hierarchical URL option in IPB 4 would be a HUGE disappointment. URL changes should never be taken lightly, but recently I've found search engines more receptive of change with 301 redirects. I would jump at the opportunity to have hierarchical URLs, and some of my communities have 10+ years of URL history. Myself and others have made the case before, but it's just common sense. The current URL structure is broken. Don't force the change on users, but give them the option to redirect it with a graceful 301 redirect. Even though this topic is a very bad example URL (too many subforums), it's still relevant. If you were looking for changes to IPS URLs, which would you be more likely to click in a search result? http://community.invisionpower.com/invision-power-services/ips-client-services/ips-software-and-company-feedback/community-suite-feedback/ip-board/url-enhancements/2471724.html Or, In an A:B test, even in this bad example, the first result would get a better click through. Not to mention how keyword rich the URL is (IPS, URL), to increase SERP. P.S. I didn't make $xx,xxx last month, but my communities do have about 500k registered users, and 4M posts.
  10. Having recently upgraded a forum to 3.4.6 I was surprised to learn this had not been addressed either by feature update or mod. While the postable forums have been a welcome setting, if "Allow posters to view other member's topics" is set to "no", users also can't view pinned topics. Isn't a pinned topic inferred that it's meant to be viewed by all? It would be nice if this oversight were fixed in 4.0, or hookable so a mod could be more easily created. Currently, the only workaround is to make announcements, which don't have the same formatting, and don't allow replies.
  11. Notifications and IP Board 4.0

    I know you said notifications are improved greatly in 4.0. I just want to confirm a scenario common to other platforms has been addressed in 4.0. Many people want two choices when it comes to email notifications. Either an email for every reply, which works fine. Or one email per day, per subscribed topic with updates. This has never worked properly... going back to 2.x. IIRC it did work correctly in 1.x.
  12. Just resize your ads with javascript according to viewport (which I think Charles said). e.g: <script type="text/javascript"><!-- google_ad_client = "ca-pub-*****"; var width = $(window).width(); if (width > 740) { google_ad_width = 728; google_ad_height = 90; google_ad_slot = "*****"; } else if (width > 480) { google_ad_width = 468; google_ad_height = 60; google_ad_slot = "*****"; } else { google_ad_width = 263; google_ad_height = 60; google_ad_slot = "*****"; } //--> </script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>
  13. 2.3.6 as well... I stand corrected.
  14. For the most part I can upgrade PHP and not have it affect my site in any way. I'm running PHP 5.3.23 on 2.3.4 without issue. I don't see the relevance. It's not not irresponsible. I'll give you the URL, and you can let me know when you find a vulnerability.
  15. @ Cyrem, I see you joined in 2009. If you look at my profile, I joined in 2003. I still have a site running 2.3.4. It's the little engine that could. It just steadily, and slowly grows. I also have a 3.1.4 site that lost significant traffic after upgrading fro 2.3.4 (other sites as well). I used to be someone that upgraded the day an update became available. Now, I guess I'm older and wiser. The longer you have your forum, the more you'll realize not all upgrades are improvements. 3.4.4 is the first upgrade I've considered in a long time. I'm making progress on a dev server, but I shouldn't be forced into an emergency upgrade (no skin, lost mods) because of an unpatched security issue. I understand not offering support (even with a paid license), and I have a Facebook login issue that could use some support. I don't understand leaving known security issues unpatched. Every unpatched 3.1.4 forum, 2.3.4 forum... could be the next server that helps DDoS your site (or this one). That infects your computer with malware. That sends you spam. It's irresponsible to leave them unpatched.
×