> While JinjaSQL can handle insert/update statements, you are better off using your ORM to handle such statements. JinjaSQL is mostly meant for dynamic select statements that an ORM cannot handle as well.
This library doesn't run SQL, its only a template engine that gives you back a parameterized query and parameter array back. It's up to you to actually use them with an adapter, which means you can use prepared statements.
This is a fantastic anecodote and after the year we've had I'm finding the challenges people are having from entering Linux are becoming less and less.
Earlier today I marvelled at running a game through Steam whilst listening to streaming music through Spotify whilst being able to switch window into bash.
At work, I threw arch on an old-ass laptop we had sitting around, and then installed steam and portal, hooked it up to the office TV and then had to sit there a minute to marvel at the fact that it all just worked. Never would have predicted that a decade+ ago.
I recently bought a new laptop and dual boot Windows 8 and Ubuntu 13.04. It took me 3 hours to get all the drivers working in Windows whilst the only issue I had with Ubuntu was the fact my video card drivers (ofcourse, Nvidia) were going to be proprietary.
Locks and Alarms are the lowest common denominator of security - it stops people from walking in but more than anything just gives an illusion of security.
More importantly, they make the distinction between a welcome entry and forced entry much clearer, which is very important from the legal point of view. It's not an illusion of security, but a precondition for a safety and recovery framework to kick in (police action, insurance, etc.)
I think there is more to it than a buzzword though, the HTML5 way of doing web ie, paving the cow paths is radically different to the methodologies of XHTML, such that the range of technologies to be born/adopted out of that paradigm shift could be thought of as HTML5 era technologies.
As an Australian, I welcome this wholeheartedly. It has been extremely frustrating watching the payment revolution in the states, whilst at home there is next to no alternative to getting a merchants facility through a bank up until now. It will also be nice dealing with an API that isn't stuck in the 90s.
Braintree here. Gave the same response below in the thread,but wanted to make sure to address here as well. You all are right. Getting a merchant account and setting up a foreign currency account has been notoriously difficult to get in the past with extremely high fees and approval requirements. This is no longer the case. Braintree sponsors merchants to get setup with a merchant account in Australia and has built an accelerated process to creating foreign currency accounts.
If a provider states that no merchant account is required, you are most likely being placed on an aggregated merchant account. This has many disadvantages for the merchant as you are grouped under one umbrella account. As the provider grows, this becomes unsustainable and often leads to poor customer experiences (a la Paypal account freezes).
We're working to create a sustainable solution where customer service and great software are the central focus. We'll be constantly improving the on-boarding timeline and look forward to helping the fast growing tech scene in Australia. Always happy to answer any questions about anything payments or e-commerce related, just let us know!
I started the process of getting a merchant account with NAB and quickly gave up. They had a long check list of requirements that had to be completed before the application was submitted. This included have the signup and subscription processes fully working so they could test them.
I remember early on in my web development career to make sure you are selling a service not a product. You aern't building a website - you are providing a marketing service, requiring expert advice and a component of that service is building a website. As people have said, websites are easy - Wordpress + theme + hour of time and you are done.
Sell your knowledge of digital marketing - SEO, Adwords, etc in order to drive sales for your client, which is ultimately the reason they want a website in the first place.
If you place rate limiting on email accounts by default and then for the lower percent of users that need a higher rate do it on a case-by-case basis. In my experience most users that fall victim to these types of phishing attacks do not need to send high volumes of emails.
Oxford already has rate limiting. 1000 messages per hour through their servers, it seems [0].
The next step would be to filter outbound traffic to block SMTP from compromised PCs. It seems they have an outbound firewall, but it's not obvious which ports are closed because the list of blocked ports is ... blocked[1].
The 1000 limit seems like a high number, why would a legit user need to send that much email out? I'd think a much smaller number like 5 per hour would be better.
You're a lecturer with 200 people in your class. That's 2 days. Does the lecturer have to leave their computer all the time? Is their email programme going to handle this sort of delay? What do you do if the lecturer wants to send an email about updated homework due in a few days? Some students will have a 2 day head start, is that fair? Do you have to give them extra time/marks?
You're the first year faculty advisor. There are 1,000 people in that year. That's 1 week. Same questions as above.
(And in case you think "Well let the lecturers send more", what makes you think the lecturers aren't the problem in the first place?)
Calls for Papers / Articles is the classic reason. The IEEE and the ACM might have proper mailing lists for that sort of business ... most academic fields do not.
Edit: I think they could lower the rate more and push mailing lists, but on the other hand a lot of users simply wouldn't notice that they're rate limited. Which could lead to entirely different brand of lulz.
1000 mails/h is definitely too much - it's 16 mails per minute(!). I think something around 60 - 100 mails per hour is more reasonable, to cater for cases like lots of one-liner exchanges.
What exactly makes it impractical to do powerful things? You may have disdain for certain language features but I don't understand how that makes it impractical.
Most of the tech demo's we're seeing coming out of the JS crowd are from people who have only just started using the WebGL API (which is still experimental). I'm extremely excited to see the things that experienced OpenGL developers will be able to do as the API becomes more mainstream.
[1] https://github.com/hashedin/jinjasql#when-to-use-jinjasql