who hijacked servers? considering the foundation owned the servers, they couldn't hijack their own server now could they.
what was the 1st thing DJ did when he was given all the access info (which he did not require root access)? the 1st thing he did even though he was asked not to, was to change the password and refuse to inform the foundation. he then altered config settings on the server which caused more issues later on. let me remind you the foundation servers were thoroughly tested by many users and even digg users. but after DJ's messing with the server, there were more problems than a little. he even changed the servers contact email address to his own instead of the foundations.. basicly HE was locking the foundation out.
but enough of that..
why the hell should we resign from xoopsinfo, xoopsaddons etc? come on give me 1 #OOPS# good reason.
Quote:
Resign from XOOPSAddons and XOOPSwiki and XOOPSdocs, give it back to the XOOPS community, and MOVE ON!!!! Don't hold those Website hostage, especially since they are paid by the XOOPS Community!
give it back to the community? when was it the communities in the 1st place? they were built for the community. but we did not and have not taken it from the community. they are not being held hostage.. lmao and as for paid for by the community.. get frakin real.. the server was paid for by the foundation, but the sites were not paid for not 1 little bit, no money was passed between anybody, everyone was working on them voluntarily.. so don't try and say that the community bought & paid for those sites.. that is definitely not True
yes they are offline at moment, but thank your brazilian hacker friend for that. but no you won't blame him because you just want to blame us for everything.
and we have moved on, but we also still support XOOPS software. BUT you are telling us in fact demanding that we STOP supporting XOOPS software. so just go back to sleep will you.
and they were needed because there was no module repository at the time in xoops. so it was built to give the community a repository, and it was built by many people not just us 3. because there was a need.
as for fragmentation, we did not do that, DJ did that and others by ignoring, disrespecting & back stabbing people. but anyway enough is enough.
is it NOT allowed for anyone to support more than 1 project? get real.
as for:
Quote:
one stop? all those my friend are seperate sites, and all will be clearly linked, with navigation, matching themes etc, and sub domain urls.. which is what we suggested before. except you wouldn't listen.. a url is a url it can be easily changed..
but even xoops.org is seperated with sourceforge & dev.xoops.org etc etc.. they are seperate sites or is that acceptable because well you're just nitpicking.
oh and btw.. WE ARE STILL SUPPORTING XOOPS SOFTWARE just not here.. xoopsaddons is for XOOPS modules.
it will be a seperate repository for impress modules at addons.impresscms.org.. ie addons.impresscms.org & xoopsaddons.org will NOT be the same site, they are seperate sites. get that? u probably don't.. lol
and as for what Catz says, he is correct.. the security fixes aren't fixes they are just covering it.
since when is htmlspecialchars used for sanitizing? sanitizing means to clean the $string text or whatever you call it.. it does not mean Prevent all html from being parsed which is what htmlspecialchars is used for.
Prevention is not sanitizing!!!
as for providing you with how it should be done.. why should we (according to you, we are not allowed to support or help people who use XOOPS).. that's what you are saying anyway..
but if you want a tip.. remove the htmlspecialchars from places where it is incorrectly used to (not sanitize but prevent) and properly Sanitise the $string 1st instead.. then it wouldn't need the htmlspecialchars (especially in function insertbreak() ) lol
and if you want us to stop coming here and replying to your stupid comments and insinuations then stop frakin making those stupid insinuations and accusations in the 1st place, then there'd be no need for anyone to respond to it would there..
so we move on, you should move on too.
XOOPS Addons & XOOPSWiki will re-open once the issues are fixed. if you don't like it, so be it.. to be honest I don't care what you think. just like you don't really care what I think either.. so i guess we're even there.