New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Colocrossing gonna colocross.
Thb i have 3 servers coloed in buf and the support has been great.
Besides that time everyones servers overheated because the air went out
They are a horrible host that deadpooled with no support years ago
I cannot login my ColoCrossing
my y im colocockring tag remove next week
rig
That's what will happen:
Overall: Not gonna happen. Just swallow it and continue on. Keep your rightful anger for better moments.
It is important we state our voice. We must play our part. Whether others do theirs or not - that's up to them and their conscience.
Come on Raindog, you're a intelligent and friendly bloke..... but please don't insult the intelligence of everyone else, you're better than that!
Sometimes I wonder if LEA still trolls aboot these parts and what he might think of us these days.
Wonder who voted for "No".
This is not gonna happen. Welcome to Low End Support
We should all be so lucky to have a ride or die like @raindog308 in our squad.
WINNING
I must also admit things are different. However, it is still unclear if the "funiculus umbilicali" has been cut or not.
I think, at the end of the day it's quite simple:
Don't get me wrong, I'm absolutely not defending CC/HD and/or the way they handled the clusterfuck.
But before anyone attacks jbiloh they should see the reality. And the reality is that so far to the best of my knowledge jbiloh tolerated the threads and voices critical of (or even disgusted by) CC/HD's handling of their clusterfuck.
So, let's stay reasonable.
ahh ok...I thought one blue party from US will be counting the votes
Yes if nothing else nobody is stopping us from rehashing it and keeping it alive. And let's be real, some of us are just enjoying the kerfuffle.
Also we had like 10 charityhost threads going on the front page at one time, this has lots of room to grow!
Too bad ColoCrossing owns this site
Stop spreading BS! They do not. @jbiloh owns LET.
True. ColoCrossing does not own LET - jbiloh controls both LET and LEB, earning the money from advertising as well as provider tags.
From what little is known about their setup, I wouldn't even be sure that LET/LEB really is a money earner.
But hey, let's just assume that @jbiloh does see a profit of a couple of $10k per year. I'm still not sure I'd call that (a) easily earned, and (b) a significant profit at all, considering what someone in his position could earn if he didn't run the attention needing and trouble prone LET/LEB bitch plus put this time into really earning $$.
Plus, considering that LET/LEB is a very, very significant "shop front" for many providers, jbiloh could ask for way more than $200/yr. Especially for new providers this here usually means the difference between basically no visibility at all (~ early and soon belly up) and having a chance to grow.
TL;DR Nuh, I don't think that jbiloh owns and runs LET/LEB to make money. What could be discussed IMO is whether the way he runs it is the best and whether letting whole gangs of marauding trolls and memers and a few people without even a modicum of manners and decency run freely makes and keeps this place attractive for civilized people with a working brain, etc. - but jbiloh possibly making some money here, if at all, isn't bothering me in the least.
Plus, again: nobody forced anyone to be here.
Your TL;DR is almost as long as the text for which you made the shorter version.
Which is why we have some rules in place. If someone does not like the rules, they can leave even before registration. However, ColoCrossing is not mentioned in community rules - it's just another provider endorsed by a provider tag. If they break the rules, then their provider tag should be removed.
@default I think you might be showing symptoms of CDS — ColoCrossing Derangement Syndrome.
Let’s not gloss over the fact that the control panel software in question released two security updates immediately following the ColoCloud incident. That alone says a lot. Plus they are making more changes from the lessons learned in a future update.
ColoCloud notified all customers within hours of the event. Anyone who reached out during or after the event got a response, and nearly every message included an apology.
Was it a frustrating situation? Absolutely. It created a huge amount of work for the ColoCloud team. But they stepped up, communicated quickly, and learned from it.
Online, no matter how a company handles a bump in the road, there will always be critics. And sure, the response wasn’t perfect, no incident response ever is, but it was far more responsible and transparent than you’re giving credit for.
I also want to remind people that if you forgot your ColoCrossing password or smth, Im sure someone can remind it to you.
Because their leaked customer DB is going around still. Which CC never acknowledged of such thing happening.
so why not release a post mortem? Explain what the bug was since it was fixed and not a colocrossing issue.
And there were several breaches AFTER the announcement and emails sent.
I am not sure about that part, I am only aware of virtualizor leak but what were other leaks?
I mean the hackers were able to still have access after the email colocrossing sent out saying the situation is under control
I believe he means the part that "hackers" were gaining access to nodes and randomly wiping VPS of people or accessing their files or installing crypto miners on it.
I guess what would really help would be some technical description of how the security issues that were fixed were directly responsible for the data breach. From the description of the Virtualizor changes I just can't figure out which issue could be responsible for a node takeover (when following usual security best practices). Let's also not forget that no other host seems to have been impacted by those issues.