Jump to content

Community

MGBrose

+Clients
  • Content Count

    459
  • Joined

  • Last visited

1 Follower

About MGBrose

  • Rank
    Member

Recent Profile Visitors

264,767 profile views
  1. Mark what about rolling back to a backup pre-seo self destruct? Then just re-import the newer posts. Honestly we had a very similar thing happen in 2009 when we moved from ipboard 2 to ipboard 3. Our SEO got completely trashed and ad revenue dropped to 1/3rd what it was. If I was smart I would have just rolled back and waited for 3.0 to become more mature. But we kept on it and a year later the ad revenue pretty much bounced back/recovered fully. And I'm interested in testing 4.0 carefully this time for the same reason and to better identify what link structures would change and forward them
  2. bfarber is offering an end user toggle to run the site under ssl possible via ipboard 3.4+ ? If so how would you create a toggle like this? Seeing a end user toggle would be an amazing feature/capability! Especially with all of the security/government snooping news lately.
  3. I perfer >post #3's suggestion entering a password 2x is great for verification, however the more fields you have at registration the lower your conversion rates will be.
  4. I'll have to try it out then. It seems like Nexus is a really popular request in regards to https.
  5. interesting I didnt think that was possible. Originally as an example of my setup for my site: I was thinking I could do 2 sets of urls non https --> https (2 seperate urls) upload http://ups.mazda626.net ----> https://d1u9jyesu396vx.cloudfront.net css http://sd1.mazda626.net ----> https://dnma4hc22tbaa.cloudfront.net images http://pb.mazda626.net ----> https://d3bjtoatzo001g.cloudfront.net js http://sd1.mazda626.net ----> https://dnma4hc22tbaa.cloudfront.net but now that you mention that, as long as it works for me I can simply use //d1u9jyesu396vx.cloudfron
  6. I fully acknowledge that both Full site ssl via https in the config file and the current toggle for "login using https/ssl" both work for 3.4, however we are missing a number of features in regards to both using CDN's and more granular control over SSL usage in IPBoard. I suspect that a lack of support for some of these features, especially CDN's, is making it more difficult for admins to utilize https/ssl for their communities. High Priority: SSL doesnt work properly with CDN's. Many CDN's now support SSL including amazon cloudfront. We should have alternate https/ssl cdn text field
  7. very cool Rohitab, I would love to get this built in as an official IPB toggle (toggle full size attachments or something of that sort).
  8. Gotchya! Just misunderstood. I also agree that the Nginx /Varnish are the 1%, but interest in nginx and varnish is certainly rising, and it is becoming more and more accessible as out of the box solutions with increasing plugin support for popular server/host management systems like WHM. The only thing i partially disagree with the traffic spike thing, its useful for alot more than that. Reducing CPU Usage, Improving connect/wait times, etc. But its alsoo great for traffic spikes too of course.
  9. When I mention Nginx & Varnish in the same sentence I was referring to the ability to have "safe" micro-caching out of the box. I think thats what Dmacelo referenced as well, (were both optimization junkies) Sorry I should have been more transparent. Also Dfarber thanks for the input it all seems very reasonable, do you think well see better CDN support prior to IPB4?
  10. Thanks I appreciate that input! if I could get any one of them, I'd take the CDN fix though. It would save me the most time, and is a pretty simple fix!
  11. I'm reccomending a slightly modified version of this here: The idea is, let IPB admins set image thumbnails, or image sizes to be a % of content width available up to 100% the size of the image. (We don't ever want them blown up to 110% 120% etc b/c of distortion. So now admins would have direct pixel sizes, or % width.
  12. I'd like to start this topic to get some discussion going on how we'd like to improve IPB 4.0 out of the box performance. Please don't move away from this topic focus (other 4.0 requests should be placed in a separate thread) These aren't necessarily ordered in order of importance, but 1) Better CDN Compatibility with versioned css/js filenames: Current Setup: The current cache url often won't change after you make edits to css/js, which means for us using CDN's that are "pull" cdn's like amazon cloudfront have a bit more difficulty getting fresh files pushed out properly. Push
  13. Why would you use encryption for the password as opposed to a hash such as SHA-2 (or even SHA-3)? The guy who created Blowfish said in 2007 that he is amazed people are still using it and that he recommends Twofish instead.
  14. Thats a really smart idea, got the line # of that edit so we can share that with others? I may give that a shot.
  15. IPB restricts editing so I can't change the first post or the title. But to me and my community best answers in its implementation is unusable/useless. Brilliant idea! Makes a hell of a lot more sense than an excerpt.
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy