As a teenager, my dad confiscated my laptop in the run-up to exams. Unperturbed, I wrote pages & pages of BASIC by hand, though I unfortunately never got around to typing them up...
This is a great opportunity to be a part of a growing development team in a London-based mobile start-up, and work in an environment that requires collaboration, great communication skills and flexibility.
At Moni we believe in latest technologies and lean approach. Our solution revolves around a distributed API backend with UX focussed mobile and web clients. We are strong believers in lean development, outside-in testing, continuous integration and delivery; we automate virtually every aspect of our day to day and are constantly looking for improvements in these areas.
Our diverse team, based in central London, is now 24 strong and growing, we are looking for smart & ambitious people who would like to help us build something truly great. If you are engaged, critical, and always ready to propose that one idea that will make our product and systems that much better - WE WANT YOU!
We are well-funded. The founders were previously heads of Google Mobile and Yahoo! Mobile product teams and we're backed by TechStars as well as a team of smart investors & advisors who believe in our vision.
If you are up to the challenge, we’d love to hear from you. Please email Athina: [email protected] and let us know why you'd like to join.
Thanks for the feedback :) - can you possibly upload a screenshot for me* so I can see the issue you're having? (It can be a little tricky with the Mailchimp template editor)
Hi all, this is very much an MVP. The idea is to collate up-to-date conversation + best practice, and share with the community. I always wanted something like this, so figured I'd scratch my own itch.
Please do feel free to provide critical feedback :)
We've discussed this in previous threads - but for those reading for the first time - there was no UK law, Cameron circumvented the legal process entirely to introduce these filters.
Background: I spent the last 2.5 years working as a product manager at another payments company. I've integrated Stripe.js in various side projects. I saw first hand what happens when you make a checkout highly customisable (dozens of options): you introduce huge complexity cost.
Here are some ways this manifests:
- longer dev cycles/increased difficulty in testing/more frequent release rollbacks
- higher merchant support costs
- harder to innovate
- a need to support dozens of legacy use-cases that only some merchants use
- harder to onboard new merchants
- more complex sales process
- inconsistent user experience for customers
- higher staff training costs/time
- impossible to optimise conversion for the majority, as each merchant is showing a different checkout.
It all starts with 1 option, but it's a slippery slope.
In summary, I think Stripe are probably taking the right approach here, and I wish them the best of luck.
Not at all - I'm just trying to keep my comments balanced. By drawing attention to the insurmountable obstacles involved in achieving Cameron's stated goal, I would hope people can draw their own conclusions.
I personally think censorship is both unworkable + immoral, but I think the HN crowd can draw their own conclusions.
"Never attribute to malice that which is adequately explained by stupidity." (1)
As a UK citizen, I've been very disappointed by this debacle. I suspect that Cameron's heart was actually in the right place (protecting the children, etc) but he does not understand the significant number of unintended consequences that we are likely to see (and are already seeing).
I would suggest doing the following to make this workable long term:
- Centralise the list of sites categorised as obscene/pornographic/etc (why should it be different for different ISPs?)
- Make the list of these sites publicly accessible and searchable
- Ensure the list is maintained by a non-political and balanced panel (is this possible?)
- Implement a process for removal requests where a site is mis-classified and ensure that this appeal process is separate from the initial panel
- Implement KPIs on the effectiveness of the filter that take into account false positives + false negatives
- Remove any automatic categorisation based on keywords, this is too crude
- Make publicly accessible the guidelines for classification
Unfortunately, I don't expect the above to actually happen :(