You would be lying - and people will call you out on this, because they will find out that you have in fact issued refunds for products with expired warranties.
They could write "We generally do not issue refunds for items outside of warranty" and they're back to the statement being just one level more vague, and thus more true.
But in reality, both of those mean the same thing. Writing "We don't issue refunds outside of warranty periods" has an understood "excluding exceptional circumstances". Everyone knows it's there. Only people who are pedantic to the point of uselessness will argue about this, and you'll find out that the courts generally have little sympathy for that.
All human languages so far are inexact. Math is probably the most exact language we've invented for communicating ideas, but languages that the general public knows are all inexact.
If the correct thing is communicated unambiguously, that's already a success, even if a pedantic person can say "I know you mean that you don't 'generally' do it, so the absolute there is a lie", the fact that the pedant can point it out means they absolutely understood what was being conveyed correctly.
This level of semantics is indeed pointless - to clarify, your comment supports both what you wrote and Google's use of the "unable" wording in their response; they are unable to reinstate your account <without introducing liability to lawsuits regarding unfair business practices> <and except in exceptional circumstances>.
The person responding at a big corporation is often unable to, for practical purposes as a result of policies other than in exceptional circumstances.
When you write in and ask them, please steal a million dollars and give it to me, while they might be able to figure out a way to steal and give it to you, for policy and job performance reasons they are unable to. They say - "I'm unable to do that for you". Who cares if they somehow could - we all understand they have chosen not to.
We are unable to reinstate your account = person responding does not have policy authority to reinstate your account and the exceptional circumstance was not identified.
The problem dive locations have is a lot of people a) overstate experience or what they remember, b) are unfamiliar or have not tested equip they will be diving with and c) equip is not familiar to operator if they bring their stuff.
People don't dive enough. So they buy all sorts of new stuff for their big new drift dive vacation. In some cases they've literally not been underwater with it for even 20 minutes. Also makes it harder to do an at a glance x-check for folks if you don't know their gear. And some gear harder to deal with (ie, adding weights underwater) if someone turns out underweighted.
My own feeling - unless someone is current with their equip or has current diving - start with a hard bottom dive at 40'.
You touch on what I think is an important consideration. A lot of people want to get into diving but just don't have the time to do it consistently enough to be fully on top of it. They have a few days vacation and go do a nice destination and expect to jump right back in at the same level they have done before, or even worse they buy some new gear as if gear makes up for practice. Like with a lot of things, there is no substitute for time in the water as a diver. Good decision making and technique come from lots of consistent practice, that most people don't have the time to do.
Plenty of resorts and other destinations offer resort and discovery diving. You do need be 10 years old, but no prior experience needed, after some basics some places let you do 1-2 open water dives in the same day! All equip is provided. You really DO NOT configure any of your stuff on these dives (you do get comfortable breathing underwater). It's a scuba dive "experience".
Unless you are a diver please don't comment with this type of snark - seriously.
" Discover Scuba Diving is a quick and easy introduction to what it takes to explore the underwater world. To sign up for a PADI Discover Scuba Diving experience, you must be at least 10 years old. No prior experience with scuba diving is necessary, but you need to be in reasonable physical health. Are you ready to try it out? "
Resort Diving is mostly safe, the dive profile helps keep you safe. At 30ft, a lot less can go wrong. You can easily survive a rapid ascent from 30ft, heck you likely don't need to actively blow bubbles unless you took a huge breath or are ascending super fast. OP who hasn't dove in a while shouldn't make their first dive on vacation a 120ft bottom. They will likely not remember how to breath, how to swim and will consume too much air and blow the dive for everyone. I refuse to dive with strangers on dive boats, I have never once had a dive buddy physically verify my secondary and some of them get weird when I ask them to verify their primary and secondary with me. The 'I know' eye rolls when i show them where my weight release is, where things are on my BC. Honestly thats what pushed me in to technical diving, everyone takes it serious. If we do our math wrong and the drop tanks aren't sufficient or if the trimix was off we were all dead. When we did cave dives, knowing each exit, knowing the routes we were going to navigate. Rehearsing the transitions between lines. Even with the best planning, things go wrong. Read up on the Diepolder II and III caves - scary stuff
What instructors and dive-masters actually do (or should / are trained to do) for those dives is hold onto the first stage regulator at the top of the tank for the entire duration of the dive and never pass 12 meters. The diver never even needs to worry about buoyancy. We use to call them Lipton (tea) dives, because it was just dipping tourists into the water ;) They are absolutely 100% safe when done according to the requirements.
I called them "disco" dives. Dive down a bit, show them some lights and some fish turn around a few times and back up. A play on the discovery label.
But yeah, the grumpy "master" divers will be yelling at you from shore about the whole thing!
Def want 100% contact from start to finish, and if you keep dive to 8-10 meters or less (hard bottom) helps. Just throw some statues / structures down there to look at.
Things to watch for. Folks who can't equalize - just come up or do a super shallow route if you can. And def need to make sure folks can breathe comfortably underwater (shallow water / cow pen). Also doesn't need to be long, it's about the experience. Some idiots take advantage of the depth to extend time which is silly.
Another labor was resort dive, but wasn't sure what differences / similarities were between all these experiences.
As long as it’s actual production of limitless power in 30 - half the time these things are r&d stuff. 20 years to limitless power in production is great.
Current version of GPL is an absolute no go, especially if you need to import an api / sdk style interface into your extensions and tooling - the GPL is viral. You import a GPL library to interface and your stuff is now GPl.
and latest version requires release of encryption keys etc etc - all major studios WANT content protection to work and the GPL is explicit in its attacks on that
Again: why? Because they have a grudge against the GPL's anti-DRM?
That's still FUD. There is nothing that a studio would be doing with Blender where they would want to implement DRM.
Sure, they will want DRM to be used in the distribution of the content they make with Blender; but that is totally separate from Blender itself and the GPL. It's not like the film itself will contain a copy of their asset creation or rendering pipeline!
They don’t want to open source the tools and programs they develop as part of their pipelines that tie into GPl or each other - GPl is viral and a library import triggers it.
In terms of the tivoization / drm provisions - the GPL is viral - it only takes one screw up or chain of viral connection to blow their business up. Apple fought the govt to avoid unlocking a terrorists phone, that’s how hard they protect signing keys .
The issue is they don’t know who will use what where, and the viral aspect adds insane risk. Minecraft / roblox and other games may decide to add design pipelines or render chains. Or they may want to run the software on golden image VDI pools that are locked down.
Even Ubuntu was so worried about the chain risk they changed bootloader license away from latest GPl
> In terms of the tivoization / drm provisions - the GPL is viral - it only takes one screw up or chain of viral connection to blow their business up.
Did I not just finish explaining how that is not true?
The GPL is only "viral" to software that it is licensed with, and extensions to that share meaningful data structures with that software.
The GPL does not cover content created by GPL licensed software.
> The issue is they don’t know who will use what where, and the viral aspect adds insane risk.
Except it's trivial to understand the "viral" aspect of the GPL. It's clearly explained in many places. Therefore, there is no risk at all.
> Minecraft / roblox and other games
Games? We're talking about motion picture and television studios. Then again, plenty of game devs use Blender in their asset creation pipeline without getting the GPL involved in their codebase.
> Or they may want to run the software on golden image VDI pools that are locked down.
So? What does that have to do with anything?
> Even Ubuntu was so worried about the chain risk they changed bootloader license away from latest GPl
I don't know anything about that, but I sincerely doubt the context for that decision is in any way similar there...
All I'm seeing here is FUD. Not one of your examples actually brought up a reason - outside irrational fear - to avoid using Blender to make movies.
Dude - let me make this super simple. These rendering pipelines import the SDKs and APIs they connect with. The pipelines have tons have high value custom code. Under the GPL, they have to be open sourced if they use blender - this is 101 stuff. And under GPL it is viral, if stage 1 is now forced open, the next big set of stuff that integrates with stage 1 is also forced open and so on.
Pixar is not open sourcing their pipeline - period. Do you not understand that these companies build giant and high value software around the various engines?
Listen - I didn't realize how little you understood. This is actually covered in the Blender FAQ's because it can really bite you (even if a small player) if you build an add-on to blender.
"Blender’s Python API is an integral part of the software, used to define the user interface or develop tools for example. The GNU GPL license therefore requires that such scripts (if published) are being shared under a GPL compatible license."
This is cool if you want to use stuff - they make that clear too. "Sharing Blender or Blender add-ons or scripts is always OK and not considered piracy." But for commercial players this is an absolute no go.
This is not FUD, this is hard reality, and no commercial player is going to tie into something like this.
I'm not sure why you're talking about DRM...but software licensing absolutely applies.
Studios work together and with outsourcers. Sometimes that means sharing plugins. Under GPL that would mean they'd have to share their code which is strong IP.
The current version of GPL is 100% toxic at many places I know of - this is not overly conservative lawyers - you have all sorts of rules around releasing your encryption keys - secure boot chains etc - it’s a no go and viral
Except of course the corporate folks who are licensing under AGPL who can and do then take contributors code and make available a commercial version that no one else is allowed to make available.
AGPL is a poison pill license that creates a very distorted open source model - better example is "shared source" - you can look but can't really use it in you own ops.
The whole AGPLv3 / GPLv3 thing was such a mess - a big move towards trying to tell people how to use the code. I think long term GPLv3 and AGPLv3 die out.
> Except of course the corporate folks who are licensing under AGPL who can and do then take contributors code and make available a commercial version that no one else is allowed to make available.
This is only true if there is a CLA, and contributors sign it.
The work around folks use is to claim just new stuff is agpl and skip contribs sign off. After stuff is mixed gets harder to pull apart. AWS just had to go through that exercise with elastic search
