Planet Linux Australia

Syndicate content
Planet Linux Australia - http://planet.linux.org.au
Updated: 42 min 36 sec ago

Colin Charles: FOSDEM 2016 notes

Fri, 2016-04-08 20:25

While being on the committee for the FOSDEM MySQL & friends devroom, I didn’t speak at that devroom (instead I spoke at the distributions devroom). But when I had time to pop in, I did take some notes on sessions that were interesting to me, so here are the notes. I really did enjoy Yoshinori Matsunobu’s session (out of the devroom) on RocksDB and MyRocks and I highly recommend you to watch the video as the notes can’t be very complete without the great explanation available in the slide deck. Anyway there are videos from the MySQL and friends devroom.

MySQL & Friends Devroom MySQL Group Replication or how good theory gets into better practice – Tiago Jorge
  • Multi-master update everywhere with built-in automatic distributed recovery, conflict detection and group membership
  • Group replication added 3 PERFORMANCE_SCHEMA tables
  • If a server leaves the group, the others will be automatically informed (either via a crash or if you execute STOP GROUP REPLICATION)
  • Cloud friendly, and it is self-healing. Integrated with server core via a well-defined API. GTIDs, row-based replication, PERFORMANCE_SCHEMA. Works with MySQL Router as well.
  • Multi-master update everywhere. Conflicts will be detected and dealt with, via the first committer wins rule. Any 2 transactions on different servers can write to the same tuple.
  • labs.mysql.com / mysqlhighavailability.com
  • Q: When a node leaves a group, will it still accept writes? A: If you leave voluntarily, it can still accept writes as a regular MySQL server (this needs to be checked)
  • Online DDL is not supported
  • Checkout the video
ANALYZE for statements – Sergei Petrunia
  • a lot like EXPLAIN ANALYZE (in PostgreSQL) or PLAN_STATISTICS (in Oracle)
  • Looks like explain output with execution statistics
  • slides and video
Preparse Query Rewrite Plugins – Sveta Smirnova / Martin Hansson
  • martin.hansson@oracle.com
  • Query rewwriting with a proxy might be too complex, so they thought of doing it inside the server. There is a pre-parse (string-to-string) and a post-parse (parse tree) API. Pre-parse: low overhead, but no structure. Post-parse: retains structure, but requires re-parsing (no destructive editing), need to traverse parse tree and will only work on select statements
  • Query rewrite API builds on top of teh Audit API, and then you’ve got the pre-parse/post-parse APIs on the top that call out to the plugins
  • video
Fedora by the Numbers – Remy DeCausemaker MyRocks: RocksDB Storage Engine for MySQL (LSM Databases at Facebook) – Yoshinori Matsunobu
  • SSD/Flash is getting affordable but MLC Flash is still expensive. HDD has large capacity but limited IOPS (reducing rw IOPS is very important and reducing write is harder). SSD/Flash has great read iops but limited space and write endurance (reducing space here is higher priority)
  • Punch hole compression in 5.7, it is aligned to the sector size of your device. Flash device is basically 4KB. Not 512 bytes. So you’re basically wasting a lot of space and the compression is inefficient
  • LSM tends to have a read penalty compared to B-Tree, like InnoDB. So a good way to reduce the read penalty is to use a Bloom Filter (check key may exist or not without reading data, and skipping read i/o if it definitely does not exist)
  • Another penalty is for delete. It puts them into tombstones. So there is the workaround called SingleDelete.
  • LSMs are ideal for write heavy applications
  • Similar features as InnoDB, transactions: atomicity, MVCC/non-locking consistent read, read committed repeatable read (PostgreSQL-style), Crash safe slave and master. It also has online backup (logical backup by mysqldump and binary backup by myrocks_hotbackup).
  • Much smaller space and write amplification compared to InnoDB
  • Reverse order index (Reverse Column Family). SingleDelete. Prefix bloom filter. Mem-comparable keys when using case sensitive collations. Optimizer statistics for diving into pages.
  • RocksDB is great for scanning forward but ORDER BY DESC queries are slow, hence they use reverse column families to make descending scan a lot faster
  • watch the video

Colin Charles: (tweet) Summary of Percona Live 2015

Fri, 2016-04-08 20:25

The problem with Twitter is that we talk about something and before you know it, people forget. (e.g. does WebScaleSQL have an async client library?) How many blog posts are there about Percona Live Santa Clara 2015? This time (2016), I’m going to endeavour to write more than to just tweet – I want to remember this stuff, and search archives (and also note the changes that happen in this ecosystem). And maybe you do too as well. So look forward to more blogs from Percona Live Data Performance Conference 2016. In the meantime, here’s tweets in chronological order from my Twitter search.

  • crowd filling up the keynote room for #perconalive
  • beginning shortly, we’ll see @peterzaitsev at #perconalive doing his keynote
  • #perconalive has over 1,200 attendees – oracle has 20 folk, with 22 folk from facebook
  • #perconalive is going to be in Amsterdam sept 21-22 2015 (not in London this year). And in 2015, April 18-21 2016!
  • We have @PeterZaitsev on stage now at #perconalive
  • 5 of the 5 top websites are powered by MySQL – an Oracle ad – alexa rankings? http://www.alexa.com/topsites #perconalive
  • now we have Harrison Fisk on ployglot persistence at facebook #perconalive
  • make it work / make it fast / make it efficient – the facebook hacker way #perconalive
  • a lot of FB innovation goes into having large data sizes with short query time response #perconalive
  • “small data” to facebook? 10’s of petabytes with <5ms response times. and yes, this all sits in mysql #perconalive
  • messages eventually lands in hbase for long term storage for disk #perconalive they like it for LSM
  • Harrison introduces @RocksDB to be fast for memory/flash/disk, and its also LSM based. Goto choice for 100’s of services @ FB #perconalive
  • Facebook Newsfeed is pulled from RocksDB. 9 billion QPS at peak! #perconalive
  • Presto works all in memory on a streaming basis, whereas Hive uses map/reduce. Queries are much faster in Presto #perconalive
  • Scuba isn’t opensource – real time analysis tool to debug/understand whats going on @ FB. https://research.facebook.com/publications/456106467831449/scuba-diving-into-data-at-facebook/ … #perconalive
  • InnoDB as a read-optimized store and RocksDB as a write-optimized store — so RocksDB as storage engine for MySQL #perconalive
  • Presto + MySQL shards is something else FB is focused on – in production @ FB #perconalive
  • loving the woz keynote @ #perconalive – wondering if like apple keynotes, we’ll see a “one more thing” after this ;)
  • “i’m only a genius at one thing: that’s making people think i’m a genius” — steve wozniak #perconalive
  • Happiness = Smiles – Frowns (H=S-F) & Happiness = Food, Fun, Friends (H=F³) Woz’s philosophy on being happy + having fun daily #perconalive
  • .@Percona has acquired @Tokutek in a move that provides some consolidation in the MySQL database market and takes..
  • MySQL Percona snaps up Tokutek to move onto MongoDB and NoSQL turf http://zd.net/1ct6PEI by @wolpe
  • One more thing – congrats @percona @peterzaitsev #perconalive Percona has acquired Tokutek with storage engines for MySQL & MongoDB – @PeterZaitsev #perconalive
  • Percona is now a player in the MongoDB space with TokuMX! #perconalive
  • The tokumx mongodb logo is a mongoose… #perconalive Percona will continue to support TokuDB/TokuMX to customers + new investments in it
  • @Percona “the company driving MySQL today” and “the brains behind MySQL”. New marketing angle? http://www.datanami.com/2015/04/14/mysql-leader-percona-takes-aim-at-mongodb/ …
  • We have Steaphan Greene from @facebook talk about @WebScaleSQL at #perconalive
  • what is @webscalesql? its a collaboration between Alibaba, Facebook, Google, LinkedIn, and Twitter to hack on mysql #perconalive
  • close collaboration with @mariadb @mysql @percona teams on @webscalesql. today? upstream 5.6.24 today #perconalive
  • whats new in @WebScaleSQL ? asynchronous mysql client, with support from within HHVM, from FB & LinkedIn #perconalive
  • smaller @webscalesql change (w/big difference) – lower innodb buffer pool memory footprint from FB & Google #perconalive
  • reduce double-write mode while still preserving safety. query throttling, server side statement timeouts, threadpooling #perconalive
  • logical readahead to make full table scans as much as 10x fast. @WebScaleSQL #perconalive
  • whats coming to @WebScaleSQL – online innodb defragmentation, DocStore (JSON style document database using mysql) #perconalive
  • MySQL & RocksDB coming to @WebScaleSQL thanks to facebook & @MariaDB #perconalive
  • So, @webscalesql will skip 5.7 – they will backport interesting features into the 5.6 branch! #perconalive
  • likely what will be next to @webscalesql ? will be mysql-5.8, but can’t push major changes upstream. so might not be an option #perconalive
  • Why only minor changes from @WebScaleSQL to @MySQL upstream? #perconalive
  • Only thing not solved with @webscalesql & upstream @mysql – the Contributor license agreement #perconalive
  • All @WebScaleSQL features under Apache CCLA if oracle can accept it. Same with @MariaDB @percona #perconalive
  • Steaphan Greene says tell Oracle you want @webscalesql features in @mysql. Pressure in public to use the Apache CLA! #perconalive
  • We now have Patrik Sallner CEO from @MariaDB doing the #perconalive keynote ==> 1+1 > 2 (the power of collaboration)
  • “contributors make mariadb” – patrik sallner #perconalive
  • Patrik Sallner tells the story about the CONNECT storage engine and how the retired Olivier Bertrand writes it #perconalive
  • Google contributes table/tablespace encryption to @MariaDB 10.1 #perconalive
  • Patrik talks about the threadpool – how #MariaDB made it, #Percona improved it, and all benefit from opensource development #perconalive
  • and now we have Tomas Ulin from @mysql @oracle for his #perconalive keynote
  • 20 years of MySQL. 10 years of Oracle stewardship of InnoDB. 5 years of Oracle stewardship of @MySQL #perconalive
  • Tomas Ulin on the @mysql 5.7 release candidate. It’s gonna be a great release. Congrats Team #MySQL #perconalive
  • MySQL 5.7 has new optimizer hint frameworks. New cost based optimiser. Generated (virtual) columns. EXPLAIN for running thread #perconalive
  • MySQL 5.7 comes with the query rewrite plugin (pre/post parse). Good for ORMs. “Eliminates many legacy use cases for proxies” #perconalive
  • MySQL 5.7 – native JSON datatypes, built-in JSON functions, JSON comparator, indexing of documents using generated columns #perconalive
  • InnoDB has native full-text search including full CJK support. Does anyone know how FTS compares to MyISAM in speed? #perconalive
  • MySQL 5.7 group replication is unlikely to make it into 5.7 GA. Designed as a plugin #perconalive
  • Robert Hodges believes more enterprises will use MySQL thanks to the encryption features (great news for @mariadb) #perconalive
  • Domas on FB Messenger powered by MySQL. Goals: response time, reliability, and consistency for mobile messaging #perconalive
  • FB Messenger: Iris (in-memory pub-sub service – like a queue with cache semantics). And MySQL as persistence layer #perconalive
  • FB focuses on tiered storage: minutes (in memory), days (flash) and longterm (on disks). #perconalive
  • Gotta keep I/O devices for 4-5 years, so don’t waste endurance capacity of device (so you don’t write as fast as a benchmark) #perconalive
  • Why MySQL+InnoDB? B-Tree: cheap overwrites, I/O has high perf on flash, its also quick and proven @ FB #perconalive
  • What did FB face as issues to address with MySQL? Write throughput. Asynchronous replication. and Failover time. #perconalive
  • HA at Facebook: <30s failover, <1s switchover, > 99.999% query success rate
  • Learning a lot about LSM databases at Facebook from Yoshinori Matsunobu – check out @rocksdb + MyRocks https://github.com/MySQLOnRocksDB/mysql-5.6 …
  • The #mysqlawards 2015 winners #PerconaLive
  • Percona has a Customer Advisory Board now – Rob Young #perconalive
  • craigslist: mysql for active, mongodb for archives. online alter took long. that’s why @mariadb has https://mariadb.com/kb/en/mariadb/progress-reporting/ … #perconalive
  • can’t quite believe @percona is using db-engines rankings in a keynote… le sigh #perconalive
  • “Innovation distinguishes between a leader and a follower” – Steve Jobs #perconalive
  • Percona TokuDB: “only alternative to MySQL + InnoDB” #perconalive
  • “Now that we have the rights to TokuDB, we can add all the cool features ontop of Percona XtraDB Cluster (PXC)” – Rob Young #perconalive
  • New Percona Cloud Tools. Try it out. Helps remote DBA/support too. Wonder what the folk at VividCortex are thinking about now #perconalive
  • So @MariaDB isn’t production ready FOSS? I guess 3/6 top sites on Alexa rank must disagree #perconalive
  • Enjoying Encrypting MySQL data at Google by @jeremycole & Jonas — you can try this in @mariadb 10.1.4 https://mariadb.com/kb/en/mariadb/mariadb-1014-release-notes/ … #perconalive
  • google encryption: mariadb uses the api to have a plugin to store the keys locally; but you really need a key management server #perconalive
  • Google encryption: temporary tables during query execution for the Aria storage engine in #MariaDB #perconalive
  • find out more about google mysql encryption — https://code.google.com/p/google-mysql/ or just use it at 10.1.4! https://downloads.mariadb.org/mariadb/10.1.4/ #perconalive
  • Encrypting MySQL data at Google – Percona Live 2015 #perconalive http://wp.me/p5WPkh-5F
  • The @WebScaleSQL goals are still just to provide access to the code, as opposed to supporting it or making releases #perconalive
  • There is a reason DocStore & Oracle/MySQL JSON 5.7 – they were designed together. But @WebScaleSQL goes forward with DocStore #perconalive
  • So @WebScaleSQL will skip 5.7, and backport things like live resize of the InnoDB buffer pool #perconalive
  • How to view @WebScaleSQL? Default GitHub branch is the active one. Ignore -clean branches, just reference for rebase #perconalive
  • All info you need should be in the commit messages @WebScaleSQL #perconalive
  • Phabricator is what @WebScaleSQL uses as a code review system. All diffs are public, anyone can follow reviews #perconalive
  • automated testing with jenkins/phabricator for @WebScaleSQL – run mtr on ever commit, proposed diffs, & every night #perconalive
  • There is feature documentation, and its a work in progress for @WebScaleSQL. Tells you where its included, etc. #perconalive
  • Checked out the new ANALYZE statement feature in #MariaDB to analyze JOINs? Sergei Petrunia tells all #perconalive https://mariadb.com/kb/en/mariadb/analyze-statement/ …

Rusty Russell: Bitcoin Generic Address Format Proposal

Fri, 2016-04-08 12:29

I’ve been implementing segregated witness support for c-lightning; it’s interesting that there’s no address format for the new form of addresses.  There’s a segregated-witness-inside-p2sh which uses the existing p2sh format, but if you want raw segregated witness (which is simply a “0” followed by a 20-byte or 32-byte hash), the only proposal is BIP142 which has been deferred.

If we’re going to have a new address format, I’d like to make the case for shifting away from bitcoin’s base58 (eg. 1At1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2):

  1. base58 is not trivial to parse.  I used the bignum library to do it, though you can open-code it as bitcoin-core does.
  2. base58 addresses are variable-length.  That makes webforms and software mildly harder, but also eliminates a simple sanity check.
  3. base58 addresses are hard to read over the phone.  Greg Maxwell points out that the upper and lower case mix is particularly annoying.
  4. The 4-byte SHA check does not guarantee to catch the most common form of errors; transposed or single incorrect letters, though it’s pretty good (1 in 4 billion chance of random errors passing).
  5. At around 34 letters, it’s fairly compact (36 for the BIP141 P2WPKH).

This is my proposal for a generic replacement (thanks to CodeShark for generalizing my previous proposal) which covers all possible future address types (as well as being usable for current ones):

  1. Prefix for type, followed by colon.  Currently “btc:” or “testnet:“.
  2. The full scriptPubkey using base 32 encoding as per http://philzimmermann.com/docs/human-oriented-base-32-encoding.txt.
  3. At least 30 bits for crc64-ecma, up to a multiple of 5 to reach a letter boundary.  This covers the prefix (as ascii), plus the scriptPubKey.
  4. The final letter is the Damm algorithm check digit of the entire previous string, using this 32-way quasigroup. This protects against single-letter errors as well as single transpositions.

These addresses look like btc:ybndrfg8ejkmcpqxot1uwisza345h769ybndrrfg (41 digits for a P2WPKH) or btc:yybndrfg8ejkmcpqxot1uwisza345h769ybndrfg8ejkmcpqxot1uwisza34 (60 digits for a P2WSH) (note: neither of these has the correct CRC or check letter, I just made them up).  A classic P2PKH would be 45 digits, like btc:ybndrfg8ejkmcpqxot1uwisza345h769wiszybndrrfg, and a P2SH would be 42 digits.

While manually copying addresses is something which should be avoided, it does happen, and the cost of making them robust against common typographic errors is small.  The CRC is a good idea even for machine-based systems: it will let through less than 1 in a billion mistakes.  Distinguishing which blockchain is a nice catchall for mistakes, too.

We can, of course, bikeshed this forever, but I wanted to anchor the discussion with something I consider fairly sane.

Kristy Wagner: Panama Papers – what does it mean for me?

Thu, 2016-04-07 11:26

It is just a little insane that in the process of my setting up this web site my motivation to launch it with a ‘real’ blog post simply had not transpired.  Then came along Panama Papers, which took me past that point of wanting to write to simply want to bury myself in research and to never resurface.  Data and I have a very loving relationship, I love to surround myself in it and it loves to share its secrets with me.

So, I buried myself and looked at all the tattles on big business and large personalities, and woke up this morning with two questions:

  • How did they manage to mine what they have and how much did they just hand over on platters to government agencies?
  • What does this mean to me?

The former is already being unveiled in the media.  So, I thought I would address the latter.  What do you think this means for you?

Well, the times are changing and, if successful in protecting its source then The International Consortium of Investigative Journalists it has opened up a brand spanking new precedent for whistle-blowers.  The survival of this whistle-blower is now completely dependent on not having given away their identity for themselves in their day to day interactions, dare a bead of sweat even think about beading near an eyebrow then their fate shall likely be sealed, along with anyone else with a vaguely guilty conscience.  Some of the ‘powers’ named in the document have the power to make you disappear and have no issue reaching to foreign soil to reach that goal.

So whilst they are on the chase, we innocents stand by and watch to ‘crazy’ unfold.  In other countries with greater questionability over political ethics there is going to be political change, in some countries there shall be protest and the destabilisation of leaders, in others solidarity as the political spin continues.  Here in Australia, though, it comes down to a bunch of corporations and about 800 of individuals. In the scheme of things, without impact figures, this seems relatively small.  Only time will reveal the size of the tax pie that got carved by offshore money movements.

Spineless ATO settlements

As the Australian Tax Office (ATO) tracks down these individuals and hits them up for tax evasion, we are going to see many, many quiet settlements.  To avoid the difficulties and costs of due Court process the ATO are known to taking settlements at as little as one tenth the known debt, including historic debts by organisations now named as being associated with the Panama Papers.  We are going to see a lot of these but don’t hold your breath, it will be some time before they start building cases.  As a result of settlements, they are not known for seeing these people face non-financial punishments such as actual gaol time.  I hope someone in political oversight gives the ATO a giant kick up the pants expecting that every one of these people gets prosecuted to the full extent of the law.  But hope rarely equates to action in political spheres.

More Leaks

Once one person gets away with whistleblowing, others follow suit, somewhat like media attention on suicides.  If you are free of the offshore banking set up it doesn’t mean you are off the hook.  If your actions are shady then know that even a sniff of it from others may lead to you being caught.  Are you shuffling money, paying family members who are not actual employees, or have a raft of false invoices in your tax deductions?  Yep, if you are then you are now more likely to have someone pull the rug out from under you and it is going to be someone you know.

A company that holds nearly nothing on the public web has lost over two terabytes of data, what can someone with system access do to you?  My first suggestion is to clean up your act and confess any sins before you get caught.  Lest, you shall be the at mercy of others….

 

 

 

Sorry, I trailed off topic reminiscing of a movie scene with Andy Garcia in Oceans 11 as his character, Terry Benedict, throws a tantrum demanding that staff find out how they (Ocean’s 11) hacked into his system.  Whistle-blowers are going to do it if they are given a strong enough encouragement and they suspect they know what they might find.

Dark Web Understanding

Through disclosure of how the journalists went about mining this giant slab of data and communicating about it securely over international boundaries is going to give way to a better understanding of the Dark Web.  Suddenly the fear associated with secure anonymised communication is going to make sense as a safe haven for those pursuing truth (and not just those pedalling unsavoury wares).  I think somewhere in the last 3-5 years we forgot about those proxies set up for people in foreign countries to be able to share what is ‘really’ going on with the rest of the world.  I believe as this story unfolds people will come to understand the differences between the dark web, the deep web and the internet and rather than fear it, will simple accept each for what they are, knowing that all three are destined to evolve over time also.

Closing Loopholes

The Australian Government can’t change international law or laws governing other sovereign nations so what will they do to close loopholes?  The easiest way is to tax the shit out of every dollar that heads offshore and some of that can be controlled in the first instances but other shadier means will be found around it.  The way around it is to make moving the money offshore more expensive than keeping it here.  Some of the obvious tax avoidance avenues that will need to be closed through taxation will be:

  • dividends payments to foreign shareholders,
  • payments to benefactors of trusts who are not paying tax in Australia on the amount,
  • revenues paid back into foreign parent/holding companies,
  • fees paid on goods and services, possibly inflated or non-substantiable items, also through tariffs and duties, and
  • taxation on loans taken by Australian companies from overseas sources, or the limitation of interest deductibility from the same, including from parent/holding companies.

These are just the ones that spring to mind and is in no way comprehensive.  The key thing in this, though, is that such measures would make our economy quite protectionist.  (Not that this is necessarily always a bad thing.)  It means that we will see costs of imports rise, giving way for local business to be a preferred provider of products for our citizens which is awesome, other than for industries that we have allowed to collapse over the last 30 years.  Implementing protectionist tax reform had ought to be worth it too, I actually figure that now would be time to remove exemptions for mining whilst we are at it.  Everyone knows that their international buy prices from Australia to the sister company that sells it is just another loophole to be closed.  Let’s face it, people still need the commodities that are being ripped from our land.  If we are going to let our resources be removed from our own use, then it should benefit our nation far more than it does now.

In reality though implementing the closure of loopholes, like those above, has some serious economic impacts to international trade and our supply chains.  It is going to take a long time for Cabinet parties to get their heads around the impact let alone to debate the cost to benefit from such a decision.  Don’t hold your breath for every loop to be closed but be sure that we are going to see some changes.  Maybe though, we can move the pressure of Mum and Dad investor who are using negative gearing to finance their retirement and instead focus on catching real tax that is being let slide through for the benefit of large multi-nationals and the one percenters who are prepared to dabble in the potentially unlawful.

What about me?

Well, watch the tax space, have a chat to people who understand the economy and international trade about what is happening politically.  The means of gap closure will provide more opportunities in our country for us to build economies anew.  It also means that we may see somewhat of a market crash as foreign investors are taxed for taking their money home but we will find our way through and the crash could open up opportunities that Generation Y and I are missing in respect to owning their own homes and securing personal investment in a meaningful way for the first time.

If we closed these gaps quickly enough for businesses to not have opportunity to jump loopholes, then we would also have a significant revenue impact which one would hope would be pushed to the citizens as investment into education and health.  The potential though is quite amazing because this eye opener is also a good means to revisit the short sightedness of the sale of public assets.  If we temporarily crashed the market by restricting foreign investment and cutting the ability for foreign ownership by sale, we have the opportunity for the Commonwealth as well as States and Territories to change the way they manage economics and asset allocation.

Also, for business owners, this is potentially a great time to consider your capability to be a provider to Government for goods and services.  There is going to be a counterbalance from this event which may just put your tender into the preference pool because as the owner you have a visible Australian face that pays tax right here in Australia.  Right now, that is a really good thing for you.

I am not a bad guy, but I do have offshore funds, what about me?

All I can say is come clean.  Make sure you declare your offshore funds (whether through Mossack Fonsecca or not) to the Australian Tax Office and make sure you take advice directly from them on the tax liabilities you face from your choice of tax minimisation so that you do not cross into the realms of tax avoidance.  If there is an infraction that has already occurred then upfront disclosure is your best option especially before the ATO pulls your file together.  I respect to this one whistle-blower incident, Deputy Commissioner, Mr Michael Cranston has in an ATO press statement detailed:

“The information we have includes some taxpayers who we have previously investigated, as well as a small number who disclosed their arrangements with us under the Project DO IT initiative. It also includes a large number of taxpayers who haven’t previously come forward, including high wealth individuals, and we are already taking action on those cases.”

So, just come clean.  (By the way, the ATO have already offered to treat you nicely if you do.)

Political Ethics has changed

Just before you start thinking that this is all that is going to happen…ponder this statement, also from Mr Cranston:

“The message is clear – taxpayers can’t rely on these secret arrangements being kept secret and we will act on any information that is provided to us.”

Does anyone else here notice a giant ethical shift from the events of Wikileaks where the Government condemned such actions?  In the era of wikileaks controversies Governments were scared of the capability of insiders to release sensitive data and they worked on logging and permissioning tools to deter anyone who might be tempted, but now?  But now what is going on?

Okay, granted, in times of cutbacks it could be questioned if our political leadership have any ethics at all in respect to where tax dollars are given and taken.  However, the statement above flies in the face of our deontological political comfort zone where even if a political leader messed up that we have been encouraged to judge them on the intent of their actions rather than the outcome.  Now, because the leak is corporate and to Government benefit the tables have turned to whistle-blower as hero.  The fact that this act in Australia, given the role that Mossack Fonseca played, would likely be illegal white collar crime shows a giant swing of political view that our Government has permitted to come through the taxation office that now is a time that our Government will embrace consequentialism – that the ‘rightness’ of an act shall be determined on the consequences it produces rather than the morality of the act itself.

How does that play out into politics and society?  That is a whole new conversation for another day.  But if you are keen then share your thoughts on what it will look like in the comments below, along with your thoughts and opinions on how the Panama Papers will affect you.

____

Featured image source: CC-By only: https://www.flickr.com/photos/famzoo/

Kristy Wagner: Hello world!

Thu, 2016-04-07 11:26

Sorry interwebs, I know it was peaceful without me being around blogging for the last 5 years but, it is too late for you.  I am back!

New domain, new site, new content.  I look forward to sharing some thoughts with you.