because ning is a hosted platform, and not 1 downloadable and hostable on your own host, this back end network "lable" is easily visable..
i've brought up the suggestion of mapping these to our domains to make the site more branded as ours but because these are already mapped to an outside sourse and usethe same ning purchased space and bandwidth it just wont work
theres an issue with ssl security when you sign in using a mapped domain they are working on a fix for this but when it released it will redirect you to a login.ning wich is where the ssl resides
what would it take to really be white lable?
an ssl certificate for every site that uses a mapped domain (lets face ot those who dont have a mapped domain dont car at all about white lable anyway) it would take a cdn account for each doman (purchased thru ning's current cdn or any other) then rewritings every refference to the .ning servers with yoir cdn domains (which is basicly everything except the basic html )and if they (ning) were going to go that route they might as well scrap the whole business model and switch to selling a script a script with just community based tech support and ning side just instalation support so when your not getting emails..thats your problem to fix..
you might be able to take the ning out of the ning ..but then ning will no longer be the ning youve known
instead maybe you can take the sting out of being forced to have the ning lable (as the powered by link) by blending it in
2 ways if the tos doesnt alow display:none hiding of the powered by then adding text before it like site security powered by ning content delivery powered by ning etc
or using css t make it really small and a color that barely shows and blends in to the site so its less noticable (but not same color and hidden completely)
also want to note to those who say white lable is essential..
in a way its alot harder to succeed as white lable
ning as a server ..as a domain has been around a long time and gets alot of trafic
this popularity and seniority gives you a boost in search engine ranking a mapped domain has a penalty the 1st couple years and still has a hard time competing with older domains
keeping your site transparent and riding on the ning name will actualy help your site grow alot in the early years especialy
actualy just realized something! ive set uop several ning sites my main 1 i didnt get a mapped domain till it was already popular and doing well
the others i got a mapped domain b4 even starting the site..and that have all been very hard to get started even though i was certain by the subject matter that they would be much more popular then my main site
i wonder if thats why
im going to test it for a bit on my new site and instead of forwarding the ning to my domain il do it the other way around and see if that kicks it off
(i didnt create this to cause arguments just to clarify some of the backend reasons ning cant be white lable like so many want..at least not completely)
(really had no idea which forum section to post in maybe there should be a general talk about ning category)
The bigger problem is when someone shares a link from your site, and the URL shortener has "ning" in it.
url shorteners gotta have something in it shorter then your domain u dont have to use the ning url shortener u can use any number of others
but yea thats just another example i hadnt thought of
nings built on the ning backbone and trying to strip the ning out of ning would leave you with some spineless thing
its very nesacary how i know is i was hacked twice by a tiny pathetic ri asval ning sit hime him after that i got a site security scanner found out theres no ssl on signup with mapped domains so was discussing it with ning they said they are trying to figure out a workaround and it would probably be a redirect to a ning login
woithout that login info isnt secure
That would be uncool, and we're not doing that. What we are considering though is sending the form POST operation for sign up or sign in from example.com to example.ning.com over https, which would then redirect back to example.com. This would not be visible to members.
it would be visible in the startus bar as it says contacting example.ning..
just my point is its not truly invisible unless it was login.example.com
im just trying to show that this whole whilte lable arguments not so clear cut since its truly not invisible that the platforms built on the ning backend and its really kinda impossible to really take ning completely out of the picture and make it completely white lable without changing it to ainstall on your own server type package