Business responds to our report on Performance-related Pay (High Pay Centre)

Following publication of the final report of our commission on performance-related pay, the High Pay Centre wrote to the Chair of every Remuneration Committee across the FTSE 100.

We enclosed a copy of the report, showing that massive increases in Directors’ pay over the past two decades were not matched by corresponding increases in company performance.

As a result of the letter, we had constructive discussions with teams from SSE; Burberry; Rolls Royce; Marks and Spencer; Legal and General. In addition, we received letters from BT and Prudential acknowledging receipt of the report. 

We have also arranged separate meetings with the Investment Association, who represent the asset managers who manage shareholdings on behalf of investors and have input into the pay policies of the companies in which they invest, and civil servants at the Department for Business Innovation and Skills(BIS). BIS is the Government department responsible for business policy and corporate governance.

Amusingly, our letters to Vodafone and Rio Tinto were returned unopened, with a note saying that the Chair of the Remuneration Committee at each company was ‘not known at this address’ (their respective head offices). 

Posted in Uncategorized Tagged

twister-core 0.9.30: random listening port (twister)

New twister-core 0.9.30 has just been tagged on github:

The most noticeable change from 0.9.29 is that we now listen to a random port number on initialization. So users who want to preserve the old behavior must now add the parameter “-port=28333” to their command line or edit ~/.twister/twister.conf (in config file don’t use “-” before keyword, just “port=28333“)

If you had to manually configure your firewall to allow twister port to receive external connections, you should use the “-port=” parameter as well. But don’t worry, twisterd will remember the parameter you’ve used last time and keep using this same port from now on…

The idea is that lazy firewallers will have a hard time blocking twister now. No more easy “just block port 28333 and we are done”. They now need real content detection. So here is twister’s contribution to fight the crisis and generate programmers’ jobs all around the globe ;-)

The current twister-core also defines Content-Security-Policy to twister-html to prevent Javascript injections. This is an important security fix for the html client.

Besides, I’d love to announce that with twister-core 0.9.30 we now have Private Group Chats and Favorites… However the user interface is not complete for those, so this is just a “half annoucement”…


PS to twister-seeders owners: we now have a newer twister seeder as well, supporting the reporting of non-standard ports., and have already been updated. See