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
Who is going to maintain this now that @Bruce has deadpooled?
Hostress has not deadpooled.
I say keep hostress's name here on the deadpool list. Won't be long before they've dead pooled anyway.
@tdale What i read and saw, i will not take long trust me.
nothing dead about me. just promoting services when/where I'm a verified provider
Not yet, so you shouldn't be on but correct me if I am wrong but I am sure you can't make offers here anymore either way?
as stated previously, this list is about fact not fiction.
@Bruce
Whats your definition of deadpool?
Company put of business? Not providing services anymore?
From what I saw, it is acquired (and/or dissolved), no longer resolving, AS not routed, things like those.
It is not (yet) if all VMs or a big part are down, no announcement was put up about ceasing operations or acquisition, no matter how much complain there is.
So I think he is pretty liberal, it matches my view, we have a saying here, the dead man is not coming back from the grave, but we have seen a few here doing that, more or less.
firstly, it's not my definition. it's consensus of LET opinion. but generally it will include a company that is no longer operating at all, or services withdrawn with consideration to customers.
whenever customers aren't getting what they PAID for, they will be added somewhere to the list. sometimes that will be the "in the doghouse" section, as they're not strictly deadpooled.
the point of the list - inform LET readers about which providers to avoid, when a provider is no longer providing a service that is shown to be available (ie GVH), or there are significant issues with the quality of their service.
suggestions for improving the criteria are welcome
Just asking because there are a few errors in that list.
Brand is still operating != deadpool.
which one?
but is cancelling services and refusing to refund people, give it 30 days....
30 Days, when (some) employees are working for free?
Huge challenge.
BlueVM, change of ownership is not a deadpool. If you want to keep the list updated at least move them together with 123systems.
If I remember correct Damian is no longer working for ipxcore. I could be wrong, he went back there before.
hostress is down for few days... I think they're deadpooled..
Whoaaaa... The end is nigh...
Data center Calpop (calpop.com) filed Chapter 7 bankruptcy. The first meeting of creditors is November 23. While they themselves are not a low end host, their data center has housed many low end hosts. They were located in downtown LA.
UrDN is dead, too. For now, at least.
Which?
They had a 50,000 ft data center, since 1999, in the heart of LA, and I believe I read that at one time over 1 million domains were hosted there. They had a reputation for being disorganized, so many of their best customers moved on. Many companies started with a server there. If they want to identify themselves, that is up to them.
Wasn't called Calihop?
I am thinking of setting up a git that has a list of providers that have deadpooled, changed owners, or are in a warning phase due to lack of response or issues. The git would track all communication and attempts to contact the host and keep track of ownership changes via a number based system.
What does everyone think about this?
YES. As long as it's actively maintained it'll be great!
@Ithinkufailed, part of it would be that there would be multiple people managing it, hopefully.
Suggested format? CSV, TXT, XLS?
Definitely not XLS.
Do you intend for it to be read primarily by humans or by software?
Why not a google docs that is edited by only trustable people on the LET community?
A Git repository is vendor-independent.
EDIT: And machine-accessible.
and with versioning.
The reason I brought that up is readability. Txt is quick and easy, highly supported, but formatting can be "taxing". Where a CSV could be much more uniform and easier to shape to a readers wants, and with the bonus of being readable by computers.
How about TSV? Tab-separated values. Bit more work to get the indentation right, but readable by both humans and computers.
Or if it's more complex data than a few columns, you could look at Markdown (or even something like YAML). CSV is rather hard to read for humans.
EDIT: To clarify, TSV parsers will generally 'collapse' multiple tabs into a single one, so you can just use however much indentation is needed, as long as it's at least 1 tab.