트윗

	Ben Kaufman @_benkaufman	16시간
	답글을 받는 사람 @Ricrdo31523064 @jimmysong Yep. That’s not good for either, but it’s better to focus on developing than on the prices.
	대화 보기 ·

	Ben Kaufman @_benkaufman	16시간
	답글을 받는 사람 @jimmysong No, it merely means that it is less economically secure thus it’s bad.
	대화 보기 ·

	Ben Kaufman 님이 리트윗했습니다
	Chardy @ChardyBTC	8월 3일
	Palms are sweaty Charts weak bags are heavy Theres blood in the streets already alts are sketchy Hes nervous but on the surface he looks calm and ready to buy more but he keeps on forgettin its a ponzi the whole crowd shouts im out he opens his account but the funds wont come out twitter.com/TheCryptoDog/s…
	자세히 보기 ·

	Ben Kaufman @_benkaufman	8월 3일
	CoinMarketCap got some serious issues right now, showing lots of false data. Be carful and don’t trust it!
	자세히 보기 ·

	Ben Kaufman @_benkaufman	7월 30일
	답글을 받는 사람 @gakonst That’s a great definition but personally I’d change “economic behavior“ with something like “collective intelligence” as a DAO may also be (for example) a curation DAO (think something like Yelp). In the end everything is incentives but they’re not always economical.
	대화 보기 ·

	Ben Kaufman 님이 리트윗했습니다
	Evan Van Ness @evan_van_ness	7월 27일
	Issue #100 of Week in Ethereum. July 26, 2018 weekinethereum.com/post/176336020…
	요약 보기 ·

	Ben Kaufman @_benkaufman	7월 26일
	답글을 받는 사람 @ummjackson I guess meetings might look something like this? pic.twitter.com/rQq7JQGpYx
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 26일
	답글을 받는 사람 @fluffypony #LookAtMeImCharlesHoskinson ?
	대화 보기 ·

	Ben Kaufman 님이 리트윗했습니다
	Fabian Vogelsteller @feindura	7월 25일
	For web3.js 1.0.0-beta.35 there is a breaking change for the HTTPProvider, please read here: github.com/ethereum/web3.…
	요약 보기 ·

	Ben Kaufman @_benkaufman	7월 25일
	답글을 받는 사람 @udiWertheimer @magicalcrypto You need a way to send msgs which can’t be removed later. Paper can be burned and the people publishing it can be shot but msgs on Ethereum will still be there. There’s no magic in blockchain (except of @magicalcrypto) this is just the power of decentralized “immutable” ledger.
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 25일
	답글을 받는 사람 @udiWertheimer But you forget that even if they encrypt the message on Weibo the gov can just delete the msg. This is not censorship resistance at all.
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 25일
	답글을 받는 사람 @udiWertheimer I think we define censorship resistance a bit different. It seems like you refer to censorship resistance as a way for sending info which can be transferred and can’t be prevented (like talking). I refer to it as way to transfer info which can’t be censored (deleted) later on.
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 25일
	답글을 받는 사람 @udiWertheimer 1. Do you have any suggestions better than running their own nodes? 2. Read the posts I added, they used Ethereum after getting censored from Weibo. (On a different occasion) 3. This is the only method which PROVED it’s resistance to the Chinese censorship (at least so far).
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 25일
	답글을 받는 사람 @udiWertheimer But you can’t access Twitter from China... And even if you use some other accessible website the Chinese government can just censor it. google.com/amp/s/amp.redd… google.com/amp/s/qz.com/1…
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 25일
	@udiWertheimer as I said, most people don’t need censorship resistance like the blockchain can provide, but a few does need it. This is my example of how blockchain can provide censorship resistance and why I’m willing to pay more to support experimentations trying to simplify it twitter.com/patrickguay1/s…
	자세히 보기 ·

	Ben Kaufman @_benkaufman	7월 22일
	답글을 받는 사람 @udiWertheimer @WhalePanda @peepethApp A user can “follow” specific addresses (just like you follow Twitter accounts). So if I’d like to see content from you all I need is to know your address. You need hashes both for consistency and to prevent replay attacks (a provider “replay” a tweet to receive more payment).
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 22일
	답글을 받는 사람 @udiWertheimer @WhalePanda @peepethApp Basically, you can give a provider the incentive to give you the data and if it doesn't want to or simply can't, you can just ask another one. And the cool thing is that it can be all done using lightning for micropayments.
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 22일
	답글을 받는 사람 @udiWertheimer @WhalePanda @peepethApp I also think it is fine that if a provider can't protect himself against attacks then no one should use his service like no one would use Twitter if it was down all the time.
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 22일
	답글을 받는 사람 @udiWertheimer @WhalePanda @peepethApp But you can aggregate multiple providers in order to receive the full picture. Also the punishment for a “censoring” provider is that nobody will want to use their service so attacking a provider would be like attacking Twitter or so, but here you can have multiple providers.
	대화 보기 ·

	Ben Kaufman @_benkaufman	7월 22일
	답글을 받는 사람 @udiWertheimer @WhalePanda @peepethApp I can prove that a message was sent but the provider doesn't show its content. This is not 100% censorship resistant as one can claim he didn't receive the contents or so but if it happens constantly or if other providers do have the message it is much easier to detect censorship
	대화 보기 ·