This is great. I think the option to revert to a perpetual license will be a nice amount of market discipline for the team and keep them from stagnating.
I actually appreciate the subscription model and I hope that it will enable them to support new frameworks more quickly. Front-end development is moving so quickly that yearly upgrades are not fast enough. For example, JSX is just now available in TypeScript, but WebStorm 10 doesn't support it and WebStorm 11 is still in EAP.
These types of bonds do exist. They are called "linkers" and many governments issue them. In the US, we have TIPS (Treasury Inflation Protected Securities) and some savings bonds that are linked to the CPI.
One major issue with these is that the inflation adjustment typically lags by 6+ months, so they are not a good short-term hedge. But they are very popular.
I am working on something very similar with a non-profit in NYC, for NYC schools. It's very exciting, we are building on NodeJS and MongoDB, and already have some data syncing set up with the DOE's systems. Can you shoot me an email (in my profile)? I would love to talk with you and make an introduction if it makes sense.
The title about 'warning Washington' is almost certainly a heads up and not a threat. The Treasury needs to understand market dynamics to have smooth auctions for new treasuries, which is in everyone's interest. Prime dealers (the big banks that deal in treasuries) give the Treasury a heads up about these things, so would be natural for China to do so.
It's extremely likely to pass. Since this isn't technically a "treaty", Congress can only pass a bill to disapprove of it [1]. Obama can then veto the disapproval, and there are enough Democrats to override the veto.
Congress must pass a bill to revoke the US sanctions, which is a separate act of legislation from assenting to this deal. There are several Executive Orders which Obama can revoke but the embargo proper is embedded in US legislation.
How did you guys drop down to a read-only connection on Heroku Postgres? We directly connect DB clients like PGAdmin to a reporting DB on Heroku, but Heroku only seems to support credentials with full access. I don't want an analyst to "DROP TABLES" by mistake.
1. Try your best to move more during the day. Standing desks can help, but standing for 6-8 hours is probably just as bad as sitting. Do walking meetings if possible, and take frequent breaks. sSometimes I'll take conference calls with a headset and stretch in my office. Use a Pomodoro app to remind yourself to stretch or change position every 25 minutes or so.
2. Lots of people who sit for most of the day have lumbar lordosis or weak hip flexors (I did). To check if you have this problem, stand to the side in front of a mirror. Does it look like your butt sticks out and your lower spine curves in? (See here: http://stronglifts.com/lordosis-why-it-causes-lower-back-pai...). The other way you can test this is attempt to do a "hollow rock" (https://www.youtube.com/watch?v=Jh4-uLTL4v4). Is that hard/impossible? You probably have lumbar lordosis, weak hip flexors, weak abs or all of the above.
This can be hard to fix, but not impossible. It's doing to take a few months, but it's totally worth it. The way I did it was to just do Crossfit. It's really hard to do this on your own and keep your motivation up and Crossfit solves that problem. Most Crossfit exercises require you to have an "explosive" hip thrust which will strengthen and stretch your core.
If you don't want to do Crossfit, kettle bells seem to be the exercises in Crossfit that stretch and strengthen the hip flexors most for me. Try kettle bell swings, kettle bell sumo deadlifts, and kettle bell cleans.
The Fed also releases all of the memos that are used by the FOMC to set monetary policy. It just releases them with a five year lag. It also releases transcripts of all FOMC meetings and conference calls, plus all presentation slides used [1].
It really is quite transparent, and I'd argue that releasing things with a codified lag is a good balance between the need for secrecy and the public's right to know.
You can even see the options for wording of the FOMC's statements, considered to be some of the most sensitive material at the Fed. It's contained in the section of the "Bluebook" produced prior to the FOMC meeting called "Alternative Statement Language". [2]
Source: used to work there and make some of the charts and models that go into those documents.
Reading through the history of the case[1], it looks like the District Court ruled that the Federal TSA officers involved were entitled to qualified immunity under the Federal Tort Claims Act. The reasoning was that the TSA followed appropriated procedures and wasn't responsible for the longer (few hour) detention by the Philly Police. In my opinion, that seems reasonable. The TSA only detained him for 15-30 mins to question him about the cards, then turned him over the the state police.
After that ruling, the parties settled. I'm not sure why the case wasn't pursued further against the Philly Police. It could be that the case wasn't likely to succeed under Pennsylvania law, or maybe the ACLU wasn't interested in continuing to pursue it, since a Pennsylvania precedent wouldn't be a "worthwhile" expenditure of ACLU resources.
...the TSA... wasn't responsible for the longer (few hour) detention by the Philly Police.
This rings true to me. The TSA in general does not want people in custody. They know themselves that most of what they do is bullshit, so what would be the point? When I was delayed by TSA, they were eager to turn me over to LVPD, who, after a short conversation about the best way to deal with TSA bureaucracy and escape with minimal fines, told me, "if you run you can still catch your plane". Which I did.
Author of TFA had the misfortune to deal with local police just as stupid as TSA, but without the built-in CYA aversion to arrests.
The TSA "officers" do not have arrest power and are forbidden by policy from using force (to perhaps perform a citizens arrest if allowed in state for a state law violation), so they really don't have the ability to take anyone into "custody", hence calling for local police.
The reason why they don't have arrest powers is because splitting up the particular duties involved in infringing liberties makes it impossible to pin it on anyone. The TSA can blame it on the locals, the locals can blame it on the TSA, and 9 times out of 10 they don't even need to find a patsy for a scapegoat.
(IANAL) The thing is the ACLU only has leverage against the Federal gov't if they pursue a settlement - the federal gov't doesn't want to see the agents deposed. Even if they have immunity, it'd make them look bad. If this went to trial, that leverage would be gone. So, the settlement deal gets them point 2 on that list, instead of just (potentially more) money.
This is pretty bad, but I believe it is only possible to get an access token if you also allow malicious/non-trusted users to either create new OAuth client registrations (`Doorkeeper::Application` models) or modify the redirect URI of an existing OAuth client registration. The reason is that the access token is delivered over a redirect, not in the response to the form POST. Doorkeeper does check for a valid redirect URI.
I actually appreciate the subscription model and I hope that it will enable them to support new frameworks more quickly. Front-end development is moving so quickly that yearly upgrades are not fast enough. For example, JSX is just now available in TypeScript, but WebStorm 10 doesn't support it and WebStorm 11 is still in EAP.