41–50 of 60 posts
Earlier quoted context omitted.
Am I the only one who never care about licenses? It says "free" so I download it. What is the worst thing that can happen?
https://www.gnu.org/philosophy/free-sw.html
"Free" as in GPL2.
Ripped that out pretty quickly.
First thing I check when I read "Free" is I see what the license is (MIT/BSD). Unfortunately, you can't find out what license the theme uses until you get the actual theme. You don't get the actual theme until you put your email address in. I couldn't submit my email address until I subscribed to the newsletter (but upon trying it again in incognito I wasn't prompted to subscribe -- might have been an error on my par…
Am I the only one who never care about licenses? It says "free" so I download it. What is the worst thing that can happen?
The worst thing that can happen is going to jail or having to repair whatever damage they claim you have caused. Though it's very unlikely in your case and for this library.
First thing I check when I read "Free" is I see what the license is (MIT/BSD). Unfortunately, you can't find out what license the theme uses until you get the actual theme. You don't get the actual theme until you put your email address in. I couldn't submit my email address until I subscribed to the newsletter (but upon trying it again in incognito I wasn't prompted to subscribe -- might have been an error on my par…
Am I the only one who never care about licenses? It says "free" so I download it. What is the worst thing that can happen?
The issue becomes when you then decide to build something commercial with photos/libraries/etc that have non-commercial/attribution features to them. If I wanted to use this theme to build a Startup, it could become very enticing to companies to target litigation against me. Above and beyond litigation, it could be a PR nightmare if press found out I had built something on top of code that I wasn't allowed to use. Think of all the questions it would raise -- well if he used non-commercial code commercially, what if he had stolen code from other places?
It also lends a sense of credibility to the project/photo/download in that the author thought about the way that his creation was to be used. We used a "free" open source iPhone mockup that seemed perfectly legitimate, and implemented it into one of our client's websites. A few months later, Getty Images had detected that a commercial copyrighted image had been used in the background of the iPhone mockup and sent a litigation letter to our client demanding payment. It was an expensive lesson for us to learn that just because something says it's one thing doesn't mean we can take them at their word.
First thing I check when I read "Free" is I see what the license is (MIT/BSD). Unfortunately, you can't find out what license the theme uses until you get the actual theme. You don't get the actual theme until you put your email address in. I couldn't submit my email address until I subscribed to the newsletter (but upon trying it again in incognito I wasn't prompted to subscribe -- might have been an error on my par…
I did some poking around, and the license information can be found here: http://www.blacktie.co/about-themes/ It uses the Creative Commons Attribution 3.0 license.
Earlier quoted context omitted.
Am I the only one who never care about licenses? It says "free" so I download it. What is the worst thing that can happen?
https://www.gnu.org/philosophy/free-sw.html
One question though, did I understand it correctly or have a got it wrong:
I can make a free software (free as in speech), and charge you X amount of money for it, but it is within your right to sell it to the next person as long as you keep the freedom to modify etc?
I have also just discovered fontawesome, which just shows that I really need to improve my front-end programming skills...
The themes are beautiful and the presentation is nice but the required email opt in totally turns me off. Why not just host these on github? I actually want to be on your newsletter but I don't like that you are forcing people to do so [1]. [1] https://news.ycombinator.com/item?id=7002338
On the other hand, the "leave email to download" model is completely fair. Not only is it used by the overwhelming majority of companies (most apps require some form of signing up), but you're also the only one receiving those email. So the cost is entirely personal.
So in this case, it's really a matter of whether or not the transaction is worth it for you, and I don't think you have any grounds to complain.
P.S. I'm not the author by the way, I just get ticked off seeing that objection, especially when somebody is already not charging any money for their products.
The themes are beautiful and the presentation is nice but the required email opt in totally turns me off. Why not just host these on github? I actually want to be on your newsletter but I don't like that you are forcing people to do so [1]. [1] https://news.ycombinator.com/item?id=7002338
The "tweet to download" model is bad because you're forcing someone to endorse a product publicly before they even get a chance to try it, thus potentially hurting their credibility. On the other hand, the "leave email to download" model is completely fair. Not only is it used by the overwhelming majority of companies (most apps require some form of signing up), but you're also the only one receiving those email. So…
Blacktie.co was created by Carlos Alvares (http://www.alvarez.is/). He's a designer who has a number of paid themes on https://wrapbootstrap.com/user/Basicoh. Blacktie appears to be his own site where he gives away some free themes in exchange for your email address.
Earlier quoted context omitted.
Maybe people just put time into their appearance? It's amazing how far a good diet, good sleep, exercise, and some grooming can go.
Real hackers are fat, have Unix beards and drink Jolt Cola.