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
I would disagree on using TSV primarily. Perhaps as a choice, but TSV is still debatibly obscure, and people may be more comfortable with CSV.
Hopefully there's a good choice of main format that can be automatically translated into the others.
I think CSV is the way to go, since there will not be many columns.
Why not just make one file per provider?
I don't want to make the list of just bad providers.
Well, you'd let maintainers put whatever they want in each file, good, bad, ugly ...
It is a possible structure for sure, I thought the goal was to find a quick way of seeing everyone whom deadpooled this year, and not just a random list of providers that you have to search through to find if a provider deadpooled or is good.
Well, you can standardize the data in the file. For example, a DEADPOOL <year> entry. Then one can just grep for that to get a list. And other tags, OVERSOLD, DOWNTIME <hours>, LOSTMYDATA, etc.
I agree about Git backed file.
What's the view on markdown tables? I just discovered them after googling.
My vote goes to a Markdown powered git-backed file. (I use the Gollum wiki integrated inside gitlab for docs. I love that it's still fundamentally a file I can clone/migrate to another data management system; a future git-killer perhaps)
Sample md table generated via http://www.tablesgenerator.com/markdown_tables
| Provider | Died | Months alive | Re-incarnations/acquitions | ?? | |----------|-------|--------------|----------------------------|---| | GVH | 2015 | | | | | | | | | | | | | | | |
Are you all going to track old deadpoolers trying to come back with a new brand?
Francisco
What, like this one?
There was a rumour floating around a couple of weeks ago that he was even already back on LET with another brand that nobody had figured out.
Why aren't you banned yet?
It could be possible with info from the community was provided and capable of making the jump.
Agreed, I think we will use .md based tables.
Columns for deadpool would be something like:
Events would be a document that explains why they are listed, and steps to get in contact with them. It would have more detailed info on what happened, as well as the actions taken.
What other columns would you like to see?
Considering recent events, a schema to model acquisition/post-acquisition behavior and changes ?
I fear I'm leading this into Relational schema territory.
Was planning on making a second table for ownership changes.
Realistically, neither of them are 'real' formats that have a specification or any consistency. TSV is not going to be any harder to parse than CSV. You just split by tabs.
Markdown tables sound like a decent idea as well.
I fear I'm leading this into Relational schema territory.
Well...
Why not just JSON documents and then you can change the parent on the document as brands get moved around.
haha. Neat.
@joepie91 omg, that is a lot of connections.
Deadpool: https://git.enjen.net/Munzy/Host-Status/blob/master/slug/deadpool.md
Ownership Change: https://git.enjen.net/Munzy/Host-Status/blob/master/slug/ownership_change.md
Suggested: https://git.enjen.net/Munzy/Host-Status/blob/master/slug/suggested.md
Warning: https://git.enjen.net/Munzy/Host-Status/blob/master/slug/warning.md
What columns would you add for each one, only test data as of current.
Not even close to completed It's something I occasionally work on, when I'm bored.
Wish it was collaborative.
Likely will become that at some point in the future, once I get around to the new version of my VPS provider comparison table (along with another project that's meant specifically for this kind of research). There's not really any decent open-source collaborative graph tools around.
No idea when that'll become a thing, though. Depends on how much money comes in -> how little I have to worry about making the rent
@joepie91 some things never change with you.
Github repo up! https://github.com/Munroenet/Host-Status
Master repo will still be: https://git.enjen.net/Munzy/Host-Status/tree/master
DEADPOOL
Ownership Change
seems there's no great progress with an alternative list, so should update it here. apart from ho-stress, who else has deadpooled ?
FYI, anyone is welcome to edit/repost this list with updates. I started the thread, but don't own it
Nexhost is now owned by jmckeag12
xlvps.com? http://www.lowendtalk.com/discussion/67298/xlvps-deadpooled
igniteservers.com (Website disappeared)
ROFL.. just wait a few hours, I am sure the owner is reading this from his phone now, so he is not able to reply