> I Google Python-related things all the time from work, including yesterday and today, but I prefer not to login to any of my Google accounts when doing so.
Same thing here... I'm guessing that Google figures anyone cynical enough not to trust Google implicitly is a less desirable potential hire.
hmmm well I have a Python app running on GAE and I dont think I have been allowed access. With all the languages I work in they must be seeking something very specific.
> wouldn't you just move the files and change the password?
The encrypted files were distributed via bittorrent, with the password given to trusted individuals. This was done as a "dead-man's switch"; insurance against "prior restraint" (which can cover anything from incarceration to termination, depending on your level of paranoia).
Three can keep a secret, if two of them are dead.
-- Benjamin Franklin
Once the password started being shared to people without professional security training and the temperament to keep secrets, it was only a matter of time before it all came out. Regardless if you agree with wikileak's political and social philosophies, and even if you feel they provided much-needed sunlight/disinfectant, as an organization they acted like a bunch of preteens running a club out of a treehouse.
It would have been a better joke if the author had pointed that that if it's controlled by the Federal Reserve, you don't need a proof of work distributed blockchain and you could simply allow all parties to connect to the Fed in some kind of Automated Clearing House network.
This hypothetical system would allow debits and credits to be settled electronically at very low transaction costs and could be scaled to billions of transactions, and anyone could participate in such a system by spending 10 minutes and opening a free "checking account" at a local credit union.
Precisely. It is kind of amusing to see people write something like
> The Fed would create a new blockchain called Fedcoin. Or it might create a Ripple style ledger by the same name.
Do they not realize that if a central bank or any other entity wanted to create a convenient electronic currency system that is publicly accessible, it would be much simpler for them to just set up a boring old webservice with a REST API?
With an efficient implementation, the amount of hardware required to replicate a Bitcoin level of transactions is miniscule.
I think the problem (from a BTC hoarder's perspective) with that is that BTC is neither required nor desirable from an operational perspective in such a system.
From the perspective of the government, Bitcoin is only for Cowards, Crazies, and Criminals.
Cowards, who want to find technological solutions to social problems.
Crazies who are terrified that Satan will take over the Fed and decide to suddenly make dollars worthless, and in the process destroy the county.
And of course criminals who use it to buy drugs.
=====
Luckily we know better, that assuming you are one of the technical 1% who can keep your wallet from being hacked, you can (for a little extra money in conversion costs) use bitcoin to shop at overstock.com.
You could have multiple panes/columns of data, one for the graphical tree, one for the date for each node, one for the username for each node, and one for a node comment.
You should have a compare with button, and when you click the button the mouse cursor changes, and then clicking a tree node will set it as the "compare to" node.
I want to reiterate what has already been said; this does not feel like Excel. If you spend some time watching (medium-to-low skill) people who use Excel as a general purpose tool to perform general tracking and calculation tasks, you'll see there's a very different way they work.
They start with a blank sheet, and start putting data in rows. Then they add some formulas to the rows, and do a bunch of sums on some columns. The idiom you've chosen, of dragging and dropping, is a significant workflow change.
A few more things that I haven't seen pointed out already.
Your pricing scheme should differentiate between designer and non-designer users. If I buy a personal account, it's kinda useless when I can't give my url to someone and tell them to create a new entry and edit data.
Also regarding users, the lack of OpenID integration seems an obvious lack. Creating an account just to enter some data is a pretty high bar. Ideally, I should be able to share a form via email, implicitly granting data entry permissions to the recipient, then they can click the link in the email and be prompted to use their email provider's OpenID to authenticate.
Anyway, you've got some good ideas here, but I don't think you've got the right focus on Excel/Access users quite yet. It lacks the feel of Excel, and lacks the features of Access.
If the user already have data on an Excel, we provide an import wizard so that they can import their Excel and create a database with it.
If the user does not have existing data from Excel, they can first define the data fields on Ragic using the design mode. They can actually create cells as fields just like they would on a spreadsheet, but a lot of users find it hard to catch on so we added the drag and drop model just recently. So both ways should work okay.
And actually we do support OpenID log in, and the ability to click on an URL in e-mail to grant access to some DB entries. I guess we have to work on making these features more obvious to users.
"People Organization Support Training Equipment Doctrine POSTED"
We DID IT! We made it a THING!