Hacker News new | past | comments | ask | show | jobs | submit | jann's comments login

Being on the receiving side of that can be very frustrating. Even though users can cancel easily and without any human interaction, they cancel their credit card which then costs us multiple months of revenue in cancellation fees.


Which is why I'd not do it to a small company with a clean cancellation process and also why it is a good thing to do it to Adobe (multiple times a day ideally).


Instead of allowing 24 hours, I prefer to agree on a start time with the candidate, schedule the email to go out at that time and expect to receive the reply two hours later. That way everyone has the same amount of time.


Yes, I'd used that method too, but I'm not sure how many developers do their best work when told they have 2 hours max to complete any task. In fact we never put any recommendations on how long the task should take, just that they had a 24-hour window in which to come up with the best submission they could. In some (rare) cases submissions that didn't technically complete all the requirements exactly were considered more favorably than ones that did.


Messaging apps like WhatsApp will save to your photo library though (unless disabled).

So any photo sent to you would be scanned. If you someone sent you a bunch of files, that might trigger a manual review, that would most likely flag your account.

I wouldn't expect that immediately deleting them would stop the review process.


again, I hope someone sends a couple of executives the recently posted images, to make a point


That is why they talk about having a manual review process. So that when someone wealthy or politically connected triggers the system there is a review.


I haven't used WhatsApp, but I'm tempted to call bullshit on that. I've never used any messaging app on iOS which saves photos to your photo library. Doing so would make no sense and would surely be infuriating. It's also worth noting that apps on iOS can't save to your photo library unless you give them explicit permission.


WhatsApp does by default save received images to your photo library (as opposed to e.g. iMessage). You can turn that off, though. And the permission to read from a user's photo library (to e.g. post images) includes the ability to write to it.


Gross. I can't fathom how anyone would put up with that.


WhatsApp really does it, by default. It's a weird choice.

https://faq.whatsapp.com/iphone/how-to-save-incoming-media/


I only had issues so far when I accidentally didn’t convert the signed page back to an image.


Just a warning (I don’t know the specs of that ThinkPad) but just because it’s a physical switch doesn’t mean it actually physically disconnects the device.


It's called ThinkShutter and it physically covers the camera lens.


so it doesn't turn it off, it just puts some plastic in front of it. Plastic that is easier to break then something inside the case that will cut the power. While I am a big fan of the idea of the thinkshutter and friends, a real switch that cuts the loop to the cam/mic is a better option.


I think a physical shutter is superior, if only for peace of mind. If the lens is covered, nothing else matters.


I'm of the same opinion. I keep one on at all times, especially for those moments when someone's teleconferencing software turns on camera by default and I'm not in a work-safe outfit or environment.


I can't answer for cloakandswagger, but GPs comment sounded to me like this blog post is missing something essential because it doesn't talk about security.

This isn't an expensive course on setting up the perfect ES cluster in production.

As someone who is currently planning to set up a substantial ES cluster, I'm very grateful for someone to write up their learnings in such a compact overview.


The antonym for "insecure" is not "perfect."


Isn't that what Apple's "True Tone" is about? (I just know of that one, but probably there's something similar on Android devices)


Lateral | Berlin, Germany | Onsite | Full-time | https://lateral.io/

Lateral, a machine learning startup, is looking for front- and back-end engineers to join our growing team. We’re creating production systems around cutting edge machine learning and deploying them to help a wide range of industries, be it building physical infrastructure or drafting proposals. We have a real focus on UX and design and strive to create the best experience for the users of our tools.

Back-end engineer | As a back-end engineer at Lateral you will work with a team to start from a project specification, plan out a solution and build it out to production. You will have the opportunity to influence the outlook of our development process. Experience with APIs (design, implementation), Python and SQL databases (we use PostgreSQL) are essential.

Front-end engineer | As a front-end engineer at Lateral you will work with back-end developers and the UX/Design team in order to take a design and turn it into a functioning web application. We develop a broad range of interfaces to recommend content, train machine learning models or make workflows more efficient. Ideally you can work with or without frameworks (we mainly use React) and can keep up to speed with the rapidly evolving world of front-end dev and tooling.

What we offer:

- Competitive pay

- Budget for learning and conferences

- Urban Sports Club membership

- A great atmosphere

- Autonomy and responsibility

- Team events

- Relocation assistance

Lateral is committed to creating a diverse environment and would encourage people from all backgrounds to apply for this role.

We look forward to hearing from you :) Just send me an email: max at lateral.io


But in all fairness, if you actually implement that ”best practice” HA infrastructure, you will also be miles ahead of almost all internal IT departments.


It takes fuel (onboard) + oxygen (environment) to create the CO2. I assume that’s where the additional mass comes from.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: