http://www.toppers.jp/ Is what I and many many Japanese electronics and automotive manufacturers use. It's said uTron/iTron is the most used OS on the planet actually, due to it's almost universial usage in Japanese electronics. I once heard the Toyota Prius has 5 Tron instances running in each break system alone.
Of course all the information and documentation, despite being very plentiful and for a completely Open Standard (Tron) base and Open Source (TOPPERS, etc.) implementations, is in Japanese. Probably not ideal for you, but I just wanted to mention it exists and is pretty nice.
Not related to in-terminal preview but to stream over SSH have you tried mounting the remote location and streaming with sshfs? I've done it before and as long as the link is stable it seems to work fine (even for video).
Seriously, other than a few models Nokia phones have been patently awful. Every project Noka has bought out has ended up turning to absolute crap. They make awful alliances with awful companies. Now pulling tricks with vague algorithm patents? Fucking die Nokia. On and your boots suck too. Just spare us and give up on everything.
Personally I'm not a fan of WordPress, and I'm also not the one who does the WordPress sites. They're just easy, and we only do them for smaller outfits that want a quick shop blog or something like that. We don't extend off of WordPress (if something needed an extension or custom data we'd use Refinery) and we host all the sites off of a shared host that separates each install. Honestly if we knew of a full-featured blog-centric CMS that was easy enough to throw together a full site in a week (just design/views) and was *not* PHP based we'd consider changing immediately. Any suggestions?
You just said everything I would have liked to say but wouldn't have been able to write without just getting angry and swearing. Seriously, everyone who's hooked on Drupal needs to try out some other things. Me and my team do a lot of Rails and it's what I like the best, but I'm not going to claim it does everything and I know it has a place. If you've got a team of Java or Scala developers who live in eclipse use Play. Little real-time apps use node.js. Client wants a simple blog in a week? It's hard to beat Wordpress. But Drupal is a system I can't imagine ever using for anything again.
This! Life is just a lot of work which I have git to rewind, and experiences which would be much less interesting when replayed through video & nobody would care about anyway. But the ability to view my dreams would be awesome!
You're not understanding the exact point Linux is trying to get across. You realize the fact that adding this to kernel space will allow foor secure boot to work from the kernel level, this -is- correct. The problem is allowing secure boot to work from the kernel level will mean everybody has to trust Microsoft, the only signing authority, and that many people will unknowingly be putting their trust in Microsoft. The problem arises when, once all these devices have secure boot and we have however many linux installs that accept this, that Microsoft up and revoke their blessing for some reason - all the sudden people can't install and worst case many existing installations could be crippled on reboot.
Linus is making the point that this should not be handled by the kernel to begin with - put it in userspace as an extension of the boot loader or something like that. Don't force it on people, and above all else *don't make the kernel reliant on it*.
Because in this case he's fighting for their interests. If he allowed the patch it would give Microsoft very real control over what you can and can not run Linux on - and worse than that it would give them the power to revoke that permission from every kernel having that patch.
I see Debian used in professional environments every day, and I do not see RedHat at near that frequency. From where I stand and from what I see Debian and Debian derivatives obliterate RedHat in professional environments.
I do suspect RedHat has a dominance in mid sized office environments though - as that seems to be what they tout. I do not operate in these environemnts so I can't validate that claim though.
It's a damn shame most people who see your comment won't realize it is correct, and will continue to be oblivious of the existence of the most used OS on the planet.
Depending on how you implement that that could be a good idea - though it's a whole other project I think. I'm rolling it around in my head now. Permission to use this idea?
The description was confusing and misleading so I went ahead and changed it. We'll be feeding any excess back into Scroll Ninja is all. Basically this is what happened: 1. Scroll Ninja kickstarter failed. 2. Everybody started scrambling to pick up external work. 3. While picking up a job we realzed one of the libraries we wanted to use was using the copyright and license infringing Apple emoji. 4. We brought this to the attention of the author, who hadn't realized himself, and there was some panick. We proposed creating the kickstarter and everyone agreed it sounded like a good solution. 5. Still wanting to continue development of Scroll Ninja, Tohyama decided he would do the emoji project but wanted any excess to continue funding Scroll Ninja (which is essentially -his- game).
While I sort of agree with this I think there is a very real counter-argument - that being that when I use my Japanese font and view a Chinese page I want to see the Japanese version of the shared characters. I'd also like to be able to view less-often used Japanese characters that may not exist in my chosen Japanese font, but would exist in a Chinese font on my system.
Also, for the most part other than writing style most characters will be recognizably similar. I agree with the Unicode implementation for those technical and practcal reasons.
> Many of these are based on things that already exist, but will be done with your own artistic styling (correct?). No. The existing sets all have copyright and licensing terms that DO NOT allow their free use and many of the emoji in use are being used (EG from Apple) are being used in a way that violates the terms. By distributing a fully free and open source set developers everywhere will not have to worry about violating license terms, but will still be able to use emoji.
> That's all wonderful and whatever, but why does this project demand $50,000? What's stopping you from taking the week or two to fire these things out and just releasing them under the licensing model you claim you want them to be under? Becasue there are a lot of them and we don't want to just release a half assed set. We want animated versions, variations, conversion scripts and pre-packaged library wrappers so every can use an extremely broad set of emoji freely and without hassle. That's impossible in two weeks and we just don't have the financial resources to do it on our own. As a company we've actually carrying a debt and we work overtime every day to stay afloat and get ahead enough to pursue the projets we want to. This benefits everyone and gives us a little funding. Also keep in mind we have no projects that have any particular use of emoji, we undertook this project becuase the distribution of unlicensed sets is a genuine problem and a concern to many developers both OSS and otherwise.
>Why are you only releasing these things once you hit certain monetary goals? Doesn't that seem shitty to you? Because, no offense, it seems pretty shitty to me. We're not holding them captive or anything. The emoji will be created upon funding, they don't exist yet. The reach goals are just stating our bare minimum promises at those levels. If we make some ammount between two levels we won't just stop making emoji at the point of the last level we reached - we'll make as much or more as we were funded for. We're not rich and we don't have free time, but we'd prefer to make our money in ways that benefits people other than ourselves and believe open source is a good way to do that. Sorry if you think that's shitty - but you're totally free to make your own set of emoji with your own time and money if you think that's the only decent way to do open source.
I completely understand where you're coming. I chose to describe them relating to emoticons because that's what most people are familiar with and that's also basically what they were borne from. I'll try to clean up the description a bit - sorry for the confusion.
Emoji is just from Japanese cell phone mail software. To save on space they gave each image a character code and stored the images on the device. This became a standard in a block of Unicode. Emoji are not just translations of symbols like ":)" to a smiley face, they each have their own character code like a font.
Scroll Ninja is open source (source available on github) and we believe it failed because we didn't build up enough PR - and part of that is because we didn't have enough of it completed to show off. We'll be re-launching it but we want to have it more completed before re-launch. Figuring doing in OSS project for a flat rate would be something people would approve of we did this.
You are correct, the rate will be roughly $10 an hour for each of them. Consider that this is well below market rate and that there will not be any residual profits off of the emoji.
We are trying to be honest in how we will spend the money and that's why we wrote exactly how we would use it. Would you rather we said "hey, we're spending all the money just to pay Tohyama to make these" than "we're going to give everyone something for free and in exchange we're trying to cost-effectively build ourselves a future". Either way you're getting high quality graphics for below market rate.
Actually he's kind right. Copyright stuff even up into the early 2000's was crazy here. Now with new laws and the uprise of OSS it's settled down to the point where it's probably better here than in the US.
This is a glyph set, they are not full emoji. The difference is that these are a true font - the only information is outline and fill, they are not multi-colored images.
What you're saying is, thankfully, from an era past. It used to be this way but that's from old companies with old mindsets and old laws. Things have changed a lot, and there is a huge OSS movement here.
Creator of the project here, and that is correct. Please consider that we won't be selling or profiting from this afterward, and that $10 an hour for a skilled and trained artist is a very low rate. We're scraping by right now, we want a future, and this way we help open source and the community at large.
Slashdot Mirror
http://www.toppers.jp/ Is what I and many many Japanese electronics and automotive manufacturers use. It's said uTron/iTron is the most used OS on the planet actually, due to it's almost universial usage in Japanese electronics. I once heard the Toyota Prius has 5 Tron instances running in each break system alone.
Of course all the information and documentation, despite being very plentiful and for a completely Open Standard (Tron) base and Open Source (TOPPERS, etc.) implementations, is in Japanese. Probably not ideal for you, but I just wanted to mention it exists and is pretty nice.
Not related to in-terminal preview but to stream over SSH have you tried mounting the remote location and streaming with sshfs? I've done it before and as long as the link is stable it seems to work fine (even for video).
Seriously, other than a few models Nokia phones have been patently awful. Every project Noka has bought out has ended up turning to absolute crap. They make awful alliances with awful companies. Now pulling tricks with vague algorithm patents? Fucking die Nokia. On and your boots suck too. Just spare us and give up on everything.
Personally I'm not a fan of WordPress, and I'm also not the one who does the WordPress sites. They're just easy, and we only do them for smaller outfits that want a quick shop blog or something like that. We don't extend off of WordPress (if something needed an extension or custom data we'd use Refinery) and we host all the sites off of a shared host that separates each install. Honestly if we knew of a full-featured blog-centric CMS that was easy enough to throw together a full site in a week (just design/views) and was *not* PHP based we'd consider changing immediately. Any suggestions?
You just said everything I would have liked to say but wouldn't have been able to write without just getting angry and swearing. Seriously, everyone who's hooked on Drupal needs to try out some other things. Me and my team do a lot of Rails and it's what I like the best, but I'm not going to claim it does everything and I know it has a place. If you've got a team of Java or Scala developers who live in eclipse use Play. Little real-time apps use node.js. Client wants a simple blog in a week? It's hard to beat Wordpress. But Drupal is a system I can't imagine ever using for anything again.
This! Life is just a lot of work which I have git to rewind, and experiences which would be much less interesting when replayed through video & nobody would care about anyway. But the ability to view my dreams would be awesome!
You're not understanding the exact point Linux is trying to get across. You realize the fact that adding this to kernel space will allow foor secure boot to work from the kernel level, this -is- correct. The problem is allowing secure boot to work from the kernel level will mean everybody has to trust Microsoft, the only signing authority, and that many people will unknowingly be putting their trust in Microsoft. The problem arises when, once all these devices have secure boot and we have however many linux installs that accept this, that Microsoft up and revoke their blessing for some reason - all the sudden people can't install and worst case many existing installations could be crippled on reboot.
Linus is making the point that this should not be handled by the kernel to begin with - put it in userspace as an extension of the boot loader or something like that. Don't force it on people, and above all else *don't make the kernel reliant on it*.
Because in this case he's fighting for their interests. If he allowed the patch it would give Microsoft very real control over what you can and can not run Linux on - and worse than that it would give them the power to revoke that permission from every kernel having that patch.
I see Debian used in professional environments every day, and I do not see RedHat at near that frequency. From where I stand and from what I see Debian and Debian derivatives obliterate RedHat in professional environments.
I do suspect RedHat has a dominance in mid sized office environments though - as that seems to be what they tout. I do not operate in these environemnts so I can't validate that claim though.
It's a damn shame most people who see your comment won't realize it is correct, and will continue to be oblivious of the existence of the most used OS on the planet.
Depending on how you implement that that could be a good idea - though it's a whole other project I think. I'm rolling it around in my head now. Permission to use this idea?
The description was confusing and misleading so I went ahead and changed it. We'll be feeding any excess back into Scroll Ninja is all. Basically this is what happened:
1. Scroll Ninja kickstarter failed.
2. Everybody started scrambling to pick up external work.
3. While picking up a job we realzed one of the libraries we wanted to use was using the copyright and license infringing Apple emoji.
4. We brought this to the attention of the author, who hadn't realized himself, and there was some panick. We proposed creating the kickstarter and everyone agreed it sounded like a good solution.
5. Still wanting to continue development of Scroll Ninja, Tohyama decided he would do the emoji project but wanted any excess to continue funding Scroll Ninja (which is essentially -his- game).
Details of Scroll Ninja are on the (currently neglected due to lack of time and resources) Scroll Ninja webste: http://scrollninja.com/ and on our last kickstarter http://www.kickstarter.com/projects/374397522/scroll-ninja-revised . The source is up on github at https://github.com/Genshin/ScrollNinja .
While I sort of agree with this I think there is a very real counter-argument - that being that when I use my Japanese font and view a Chinese page I want to see the Japanese version of the shared characters. I'd also like to be able to view less-often used Japanese characters that may not exist in my chosen Japanese font, but would exist in a Chinese font on my system.
Also, for the most part other than writing style most characters will be recognizably similar. I agree with the Unicode implementation for those technical and practcal reasons.
> Many of these are based on things that already exist, but will be done with your own artistic styling (correct?).
No. The existing sets all have copyright and licensing terms that DO NOT allow their free use and many of the emoji in use are being used (EG from Apple) are being used in a way that violates the terms. By distributing a fully free and open source set developers everywhere will not have to worry about violating license terms, but will still be able to use emoji.
> That's all wonderful and whatever, but why does this project demand $50,000? What's stopping you from taking the week or two to fire these things out and just releasing them under the licensing model you claim you want them to be under?
Becasue there are a lot of them and we don't want to just release a half assed set. We want animated versions, variations, conversion scripts and pre-packaged library wrappers so every can use an extremely broad set of emoji freely and without hassle. That's impossible in two weeks and we just don't have the financial resources to do it on our own. As a company we've actually carrying a debt and we work overtime every day to stay afloat and get ahead enough to pursue the projets we want to. This benefits everyone and gives us a little funding. Also keep in mind we have no projects that have any particular use of emoji, we undertook this project becuase the distribution of unlicensed sets is a genuine problem and a concern to many developers both OSS and otherwise.
>Why are you only releasing these things once you hit certain monetary goals? Doesn't that seem shitty to you? Because, no offense, it seems pretty shitty to me.
We're not holding them captive or anything. The emoji will be created upon funding, they don't exist yet. The reach goals are just stating our bare minimum promises at those levels. If we make some ammount between two levels we won't just stop making emoji at the point of the last level we reached - we'll make as much or more as we were funded for. We're not rich and we don't have free time, but we'd prefer to make our money in ways that benefits people other than ourselves and believe open source is a good way to do that. Sorry if you think that's shitty - but you're totally free to make your own set of emoji with your own time and money if you think that's the only decent way to do open source.
I completely understand where you're coming. I chose to describe them relating to emoticons because that's what most people are familiar with and that's also basically what they were borne from. I'll try to clean up the description a bit - sorry for the confusion.
As linked and explained in the kickstarter there is a block of unicode specifically defined for emoji as transferred from the original emoji sets. Here's the list and the mapping: https://ja.wikipedia.org/wiki/Unicode6.0%E3%81%AE%E6%90%BA%E5%B8%AF%E9%9B%BB%E8%A9%B1%E3%81%AE%E7%B5%B5%E6%96%87%E5%AD%97%E3%81%AE%E4%B8%80%E8%A6%A7
Emoji is just from Japanese cell phone mail software. To save on space they gave each image a character code and stored the images on the device. This became a standard in a block of Unicode. Emoji are not just translations of symbols like ":)" to a smiley face, they each have their own character code like a font.
Scroll Ninja is open source (source available on github) and we believe it failed because we didn't build up enough PR - and part of that is because we didn't have enough of it completed to show off. We'll be re-launching it but we want to have it more completed before re-launch. Figuring doing in OSS project for a flat rate would be something people would approve of we did this.
You are correct, the rate will be roughly $10 an hour for each of them. Consider that this is well below market rate and that there will not be any residual profits off of the emoji.
We are trying to be honest in how we will spend the money and that's why we wrote exactly how we would use it. Would you rather we said "hey, we're spending all the money just to pay Tohyama to make these" than "we're going to give everyone something for free and in exchange we're trying to cost-effectively build ourselves a future". Either way you're getting high quality graphics for below market rate.
If you create one I will put a link in our project and we can compete.
Fun fact: The backwards N is a Cyrillic "i", it makes the "i" sound. So you are technically writing NII.
Actually he's kind right. Copyright stuff even up into the early 2000's was crazy here. Now with new laws and the uprise of OSS it's settled down to the point where it's probably better here than in the US.
You're talking about emoticons, not emoji. BTW the full emoji set includes just under 830 images, not 20 some yellow smiley faces.
This is a glyph set, they are not full emoji. The difference is that these are a true font - the only information is outline and fill, they are not multi-colored images.
What you're saying is, thankfully, from an era past. It used to be this way but that's from old companies with old mindsets and old laws. Things have changed a lot, and there is a huge OSS movement here.
Creator of the project here, and that is correct. Please consider that we won't be selling or profiting from this afterward, and that $10 an hour for a skilled and trained artist is a very low rate. We're scraping by right now, we want a future, and this way we help open source and the community at large.