Quote from: thejaytiesto on December 08, 2016, 05:11:53 PM

Quote from: geofflosophy on December 08, 2016, 05:05:42 PM

Quote from: rapazev on December 08, 2016, 01:47:36 AM

Quote from: yayayo on December 08, 2016, 12:36:08 AM

Quote from: clickerz on December 08, 2016, 12:20:54 AM

As Far As I Know, KimDotcom will be launching it next year or early first quarter of 2017. I am also eager to know his project since I know,it will have a great impact on bitcoin community. I am hoping his project develops,implemented and fully utilized to exploit its potential for the benefit of community.

I'm not so sure, whether his product will really be that innovative. Kim Dotcom is very good at marketing. He makes a lot of announcements, full of promises. However when it comes to real results, there is a lot less to show.

Bitcoin and Bitcoin users don't need Mr. Dotcom, Bitcoin is working fine as it is. If he truly had the intention to improve Bitcoin, he would have joined the development community. But he lacks the abilities to make a meaningful contribution anyway. The projects of Kim Dotcom serve primarily the purpose to generate profits for him, which is o.k.. Expecting anything special is not realistic.

ya.ya.yo!

i agree with you, but like you said he is very good at marketing and that's the main point to bitcoin.
if his idea will be revolutionary doest matter, all that matter is more buyers to bitcoin and price increasing Cheesy

He said it would launch on 1/20/2017: https://cointelegraph.com/news/kim-dotcoms-megaupload-2bitcache-reaches-funding-target-now-what

Still unclear as to whether he needs SegWit changes to be activated prior to the launch, hopefully not.

Well I would assume he is going to suffer without segwit because segwit fixes the malleability problem thing and this is always very useful specially when this guy wants to make something that relies in massive amounts of microtransactions. The idiots blocking segwit really dont know what they are doing to bitcoin.

He may be able to work around it without SegWit like Yours is doing, in which case the only bottlenecks would be on and off-ramping with BitCache.