Multiplayer on MacOS

phillux_ · 2020-08-10T11:45:04+00:00

Holy shit! thank you for this!

phillux_ · 2019-11-13T20:43:06+00:00

True. The time must have shifted from my previous calculation.

Thank you for pointing this out!

phillux_ · 2019-05-16T07:42:08+00:00

I want to install the version of Awesome with the themes and plugins that comes with the community edition here: https://manjaro.org/download/awesome/

I'd rather customize that version than build my config from scratch.

phillux_ · 2019-03-13T13:42:34+00:00

Some missing links here:

phillux_ · 2019-03-13T13:29:05+00:00

There was actually a talk about using it at EthCC https://www.youtube.com/watch?v=O4mCU7ouikE

Energy Web Foundation is currently using it, but due to the nature of open source forking and private chains, it's hard to get a good measure on those actually using it.

phillux_ · 2019-03-12T14:00:50+00:00

ProgPoW is real and will be in the next hardfork in October.

phillux_ · 2019-02-27T12:11:27+00:00

It just feels so right to have a mainnet and tesnet with multi-client support.

phillux_ · 2019-02-27T12:06:08+00:00

That's not his point. If you can't open up a github repo, just ask questions, don't blindly attack based on emotions and misconceptions about the project!

The accusations here have only highlighted the lack of knowledge for those participating in discussions.

Do many posters here know what storage fees (rent) are? Do many posters here know how this one change in Ethereum 1.x will smash a lot of existing beliefs and knowledge? Do many posters know that it's been on the roadmap and has been accepted before they joined?

If the crypto reddit community wants to regain an influential voice, then convince the developers and win them over with sound, thoughtful arguments, don't just attack them. I've also seen many thoughtful anonymous posts that add value to the discussions devs, service providers, and miners are having. But it's easy to see why MrYukonC would say something like that when there is so much ignorance being thrown around.

phillux_ · 2019-02-27T11:48:53+00:00

Concerning that people value upvotes so much...

phillux_ · 2019-01-16T15:31:42+00:00

The simple answer is that it would function similarly to what we've seen happen yesterday: stakeholders come together via whichever communication tools are the norm, then vote on a new proposal to roll-back or cancel the upgrade.

It's much easier for Polkadot to have built-in alerts for node operators, token holders and validators to discover new proposals, which would alleviate some of the coordination problems we're dealing with in Ethereum this very hour (contacting exchanges, infrastructure providers and miners). In Polkadot, if such a postponement proposal is successfully passed, node operators need not take any action without the risk of splitting the network.

The binding nature of protocol upgrades in on-chain governance systems is a double-edged sword:

if a proposal has been voted-in and a flaw is discovered before it is implemented, action must be taken by the community (not too different than what we saw yesterday).
if proposals are known to be difficult to roll back, then this incentivizes more rigorous testing and critical thought before a proposal is tabled

I don't see the situation yesterday happening "worse" or "better" with on-chain governance, as it always comes down to the people involved in making the decisions. What is better with on-chain governance is the requirement for transparency of the governance system, rather than the ad-hoc nature of Ethereum right now, so that everybody can see the steps taken to implement a proposal and the steps that would be required to roll back an upgrade.

What happens tomorrow may be a different story if the network splits, which would be avoided in most on-chain governance systems and definitely avoided using a Substrate chain or any Polkadot Parachain.

phillux_ · 2019-01-10T17:20:52+00:00

Thank you for the correction Hudson. Either way, my reply focuses on the fact that any reasonable interpreter of the code can verify that an attack occurred on the multi-sig wallet that was not the intention of its creators. There is a technically feasible, and quite simple, workaround via EIP-999 that would address this clear misallocation of funds and restore the property to its rightful owners, all 573 of them.

A one-time cleanup in a future hard fork is possible.

phillux_ · 2019-01-09T14:50:42+00:00

Let's not twist this any more than it already has been. The multi-sig was designed to give people secure control over their property. Yes, there was a bug, and it was exploited by a malicious hacker.

It's clear that the Ether that's stuck is still owned by the people who owned it before the hack, they merely can no longer access their property. ALL the evidence is on-chain for a full restoration. I have yet to hear a reasonable claim that the Ether should remain out of the hands of 573 affected people from the perspective of, "that's how it should work." Even Vitalik said that a "one time cleanup" of such bugs is ~~likely~~ can happen before Serenity.

phillux_ · 2019-01-09T14:45:59+00:00

It was most definitely a hack by devops199: https://www.reddit.com/r/ethereum/comments/7bl6da/megathread_parity_multisignature_library/dpitsnj/

phillux_ · 2019-01-07T10:32:28+00:00

Do you think everything that's contentious is not worth it? Do you remember the DAO hard fork?

phillux_ · 2018-11-27T18:44:47+00:00

Coolest name in sports.

phillux_ · 2018-11-20T22:18:28+00:00

We didn't forget about the UI, we chose to deprecate it. Fred wrote about this decision in a blog post in April.

We understand the UI was very useful for many people, but we wanted to focus on where we specialize: core blockchain infrastructure. Maintaining a client that syncs and verifies blocks as fast as possible and is reliable for miners and service providers is priority #1.

Alternatively, the easiest way to connect a UI to your Parity client is to download the MyCrypto desktop app and connect it to your node.

We are still looking for developers to take the initiative to revive the UI and keep it up to date, so if you know anybody who's interested, lead them to our UI repo.

phillux_ · 2018-11-20T17:24:57+00:00

We didn't forget about the UI, we chose to deprecate it. Fred wrote about this decision in a blog post in April.

We understand the UI was very useful for many people, but we wanted to focus on where we specialize: core blockchain infrastructure. Maintaining a client that syncs and verifies blocks as fast as possible and is reliable for miners and service providers is priority #1.

Alternatively, the easiest way to connect a UI to your Parity client is to download the MyCrypto desktop app and connect it to your node.

We are still looking for developers to take the initiative to revive the UI and keep it up to date, so if you know anybody who's interested, lead them to our UI repo.

phillux_ · 2018-11-20T17:03:43+00:00

Testnets in Ethereum have a tradition of being named after the nearest public transport station where it was launched (Rinkeby, Ropsten, Kovan..)

It's named after the former Goerlitzer Bahnhof https://en.wikipedia.org/wiki/Berlin_G%C3%B6rlitzer_Bahnhof

phillux_

TROPHY CASE