"Hey, look at all these downloads CE is getting. We need to start following up with these users to try and promote Enterprise and other products. Start capturing emails at the point of download."
551 karma · joined October 11, 2016
"Hey, look at all these downloads CE is getting. We need to start following up with these users to try and promote Enterprise and other products. Start capturing emails at the point of download."
Calendar for tasks tied to a specific date - Outlook for work, Google for home.
Jira for projects.
This feels more like a single feature of a larger product, than a product in its own right. I already have Facebook for my Facebook content, so putting the same thing on my website isn't really bringing much to the table. It looks like a nice zero-effort way to keep a "news" or "blog" section of a website up to date, but I'm still going to want all the other features of a website to be there.
If it were my product, I'd look at a few approaches to generate revenue:
- Your page puts the £15 a month front and centre, and makes it seem like the "free non-premium domain" is part of that package. There's no mention of a free tier.
- Forget the premium domain tier. Instead, limit your free tier to one post every 24 hours or something like that. Your current model means I can't upgrade without losing all my traffic - any my registrar will redirect my domain to the free tier anyway, so why pay you?
- Have your example sites link to the actual site instead of just popping up in the same page. Let me see and use existing sites so I know what I'm getting.
- Let me have some analytics, either my own Google Analytics ID or some inbuilt functionality. It's one of the things a website offers that Facebook doesn't, so use it.
- Give me a free trial. For something like this, I'd offer 3 months free. Combine that with a marketing campaign to encourage me to promote my new website. By the time I need to start paying, I've already got traffic and possibly stationary printed, so it's easier for me to justify the cost.
If we remove single use bags and cling film (yes, cling film is going to be a tough one), you're no longer reliant on the consumer to responsibly manage their waste.
There's a trade off. You're no longer sorting waste, and you're still generating less waste, but reduced shelf lives mean you now need to shop for fresh produce more often, potentially using more fuel and offsetting any gains. But you're no longer producing waste that takes centuries to decompose.
The problem with "better waste management" is it requires involvement on an individual level, and individuals can't be trusted to do it. Elimination at source removes the responsibility for the consumer and reduces the requirement for complex waste processing. That's a win for everybody.
The same argument applies to your steak - the environmental cost of the steak is irrelevant, because the steak is the product we want, and again, leftover steak disappears without trace in very short order. The issue is the packaging, which we don't want but hangs around for half a millenia if disposed of irresponsibly.
The goal of this part of the initiative is to deal with that "last mile" problem of irresponsible waste processing, because we can't trust people to dispose of plastics properly. That will inevitably have a knock on effect on the rest of the supply chain, because now companies can't sell products which use single use plastics in that area, so they'll look at alternative ways of packaging their product.
That might result in some products having shorter shelf lives, but those products don't require complex waste management practices - they just move to different levels of the food chain.
The other environmental issues such as the transport cost are an entirely separate concern which aren't impacted by this move at all.
Also, your privacy policy makes no mention of what data is included with validation requests, and what you do with that information. GDPR is still very fresh, and if my app is passing every URL data to a third party, that sounds like it could be a problem.
> Personal data held by a hospital about their patients may not be used for any non-medical purpose, and may not be shared with any third parties unless directly necessary for a medical purpose.
I'm 38 and I'm just now trying to get my own business off the ground, for an idea I had back in 2003. I registered the domain and ran it as a side gig, but there wasn't a viable business back then. Now SaaS and cloud services are more mainstream, there's a lot more potential to develop the idea. The only downside being that now I have to balance a family life and a career path along with it.
In that context, the landscape changes significantly - instead of a self driving car that mowed down a pedestrian, we have a driver who was too busy looking at her phone to pay attention to what her vehicle was doing. From the various articles, it seems that she's not an engineer, and is there in effectively the same capacity as any other Uber driver. If that's the case, she's putting far too much trust into an experimental system. I agree that Uber could do more in the way of technological means to ensure the driver is paying attention, but at some point, an adult with a job needs to be responsible for doing that job.
A good driver will look back at what they did after an accident to see if they could have done anything to prevent it, even if they weren't at fault. Uber need to do exactly the same thing. Fortunately, unlike a human driver, they have significantly more data than an adrenaline-fuelled mind and some grainy dashcam footage to work with.
A human driver, in the scenario as reported, can be expected to take a certain amount of time to react to an unexpected event, such as a pedestrian walking out in front of it. An autonomous driver, IMO, doesn't have that luxury. That vehicle should be aware of every other object it's sharing a length of road with (sidewalks and medians included). It should be tracking every other object at all times, anticipating a change of course. It should know the proximity of other vehicles, and be able to calculate whether it has space to swerve if necessary, and whether the following vehicle has enough stopping distance in an emergency. It should know EXACTLY what it will do in response to any of the potential hazards it can detect. It should absolutely not be exceeding the speed limit under any circumstances.
I suspect this incident will highlight one of the areas where investigators are not currently up to speed with technology. You can't look at an incident like this as if it was a human driver using multiple dashcams, because "It was dark and she came from nowhere" doesn't cut it. For an autonomous vehicle accident, the video isn't enough - investigators need to see and understand all the sensor readings taken by the vehicle in the lead up to the accident. Did the car detect the pedestrian? If not, why not? Why didn't it notice the change of course? How long before impact did it identify that a collision was imminent? Why didn't it brake?
Unlike a human driver, there's no human factor to consider. Every decision that vehicle made was based on rules. So "The Uber was not at fault" isn't enough - every day, thousands of people are involved in accidents where they're not at fault. That doesn't mean they couldn't have avoided it, and part of being a good driver is allowing for other people doing dumb things. The investigation needs to highlight exactly what decisions that vehicle made which resulted in this tragedy, and what can be changed to make sure it isn't repeated.
I'll forgive a human driver for not noticing a pedestrian and reacting in a quarter of a second. But all the marketing videos have trained us to hold an autonomous car to a higher standard. Certainly a lack of lighting isn't an excuse. The car should have known she was there, identified her as a potential hazard, and been prepared to take appropriate action should her course change. Speeding, along with the fact that the car made no attempt to stop before the collision, is a "back to the drawing board" level of failure.
Of course, a counterclaim for existing owners would be that the product they purchased was licensed for DC usage at time the contract was entered into, and so the original rights cannot be unilaterally revoked without consent.
In the UK, this may be your own private domicile, but you can still be harrassed.
While you can reasonably be deemed "in charge" of your camper van, if you're seen climbing into the living area with the clear intention of bedding down for the night, or are knocked awake by the police and then breathalysed, you would have a very good argument that there was no likelihood of your driving the vehicle, and therefore you would have a defence against the charge.
If, on the other hand, you climbed into the drivers seat and started the engine so you could turn on the heaters and put the radio on for a bit while you had your evening cocoa, you'd have a rather more difficult hill to climb.
If you make a habit of sleeping somewhere other than a recognised camp site, it would probably be worth your while keeping a couple of those £2 disposable breathalysers from Halfords in the glove box. Not only will it prevent you from accidentally driving while still over the limit the next day, but if you are challenged by the police while you're still drunk, it allows you to demonstrate that you have the means on hand to ensure that you won't be driving before you're fit to do so.