Related
I mine BTG and would like to know what is immature share?
Will it be added to balance?
If yes, then when?
On what it depends?
Why it is bigger than balance?
http://joxi.ru/VrwnyjQHKzOjGA
Immature shares mean that they are shares of coins that cannot be transferred or spent yet. When they become mature (in 100 blocks for bitcoin gold) the pool should begin to payout the shares.
So, I have tried to upload my application to the iTunes Connect, but it gets rejected.
2.11
Apps that encourage excessive consumption of alcohol or illegal substances, or encourage minors to consume alcohol or smoke cigarettes, will be rejected
My application
So the application I am creating is a Drinking game application. It contains "I have never/Never have I ever", and some spinning bottle look-a-like. I have several view controllers that contains rules on how to play each game.
After a search on AppStore for "Drinking Game" I get over 500 results of games. So how come that theirs game gets approved, but not my game.
I do not have any question in the "Never have I ever" game that asks for alchol, cigarettes or any usage of drugs, but the other games does.
EDIT:
I submitted an appeal to the Apple Review board, and got this back:
2.18 - Apps that encourage excessive consumption of alcohol or illegal substances, or encourage minors to consume alcohol or smoke
cigarettes, will be rejected
This is fairly obvious isn't it?:
2.18 - Apps that encourage excessive consumption of alcohol or illegal substances, or encourage minors to consume alcohol or smoke
cigarettes, will be rejected
You have implemented what is a very well known drinking game.
The fact that other games have slipped through is not really relevant. You could try pointing to these and ask for clarification as to why they are approved but yours isn't, but the most likely response is the other games also get pulled.
Since 2.18 appears to address an issue with minors you might want to try to re-submit it making it 17+ or higher (if possible).
Hope that helps :)
I am developing the firmware for a USB-based hardware device. The USB interface protocol requires that each device be assigned a vendor ID (VID) and product ID (PID).
How do I, as a device manufacturer/designer/developer, acquire a vendor ID? It is my understanding that the USB-IF assigns and policies these; is that correct? Do I need to buy a vendor ID from the USB-IF?
What happens if, instead, I just randomly pick a vendor ID to assign to my device, or just enter 0x0000, 0xFFFF?
Vendor IDs are a scarce resource, just like OUIs (top 3 octets of MAC address) and IPv4 addresses are. They have to be allocated so others don't use IDs/addresses that collide with yours. The cost just raises the barrier to allocation, so everybody doesn't land-grab willy-nilly.
It would be nice to have a "private" range, much like RFC1918 addresses (10/8, 172.16/12, and 192.168/16), that people who don't care about collisions can use.
The only meaning of getting a vid and a pid is to ensure that your sub device will not affect other with the same vid and pid.
You could set the vid or pid you like but you get the risk of a collision and your driver or the one of the other device could stop working, or both.
Ref: http://www.usb.org/developers/usbfaq#12
One other answer that people have missed: It takes a surprising amount of money and time to run a standards body.
There are costs to host the web site and official repository for the standard. You have to setup your own server, or rent space with a hosting company.
A new standard requires marketing. If people do not hear about your standard, how are they going to adopt it and use it?
Are you going to demo the new USB standard at CES, IDF, Embedded World, or some other trade show? It costs tens of thousands of dollars to rent a booth and pay for construction at one of the big shows. It costs thousands in air travel and hotels.
Are you handing out pamphlets at the show? How much does it cost to have them printed?
Are you going to advertise your standard in a magazine? Or banners on a web site? How do you expect to pay for this?
It costs money to coordinate meetings between the various members of your standards body. If you want a face-to-face meeting, you have to rent a conference room somewhere. Are you providing snacks and coffee? If you want to do a conference call, who is paying for the phone service?
You probably have an e-mail list or discussion forum. Who is maintaining that? How are you paying for the disk space to archive everything?
Does your standards body have a mailing address? Office? PO Box? Phone Number? Fax number? How do you expect to pay for that?
Any standards body with more than 1-2 members is going to have a board of directors, bylaws, officers, etc. Who is running all of that?
At some point, you will want to incorporate your standards body so it is a "perpetual" organization, not just tied to you personally. That means you need to file a tax return. Who is paying for the attorney's fees? Do you want liability insurance?
For a "physical" standard like USB, you probably need to spend money building prototype connectors and testing them. You probably need a test lab somewhere with oscilloscopes and other equipment, not to mention PCs, cables, and other equipment. Before you build the connectors, you probably want to simulate them, both mechanically and electrically. The costs for doing this can exceed $100,000.
Are you designing the logo for the standard yourself in MS Paint? Or do you want a graphic designer to do it for you. Who's paying for it?
Do you want to register your logo as a trademark? Who is going to take pay the fees for that?
Beyond money, it takes a lot of time to run a standards body. In the beginning, you might be able to handle it in your spare time, but for a high-visibility standard like USB, you may need someone dedicated to the standards body full time. They will need a salary.
The money to run a standards body has to come from somewhere.
You can charge membership dues, but this may not be enough. You will find that only a handful of people actually want to contribute to the standard. Everyone else will simply download the spec from your web site and benefit freely from your hard work.
You can charge for Access to the Specs, but this gets the "open standards" people up in arms. It also hampers the adoption of your spec. Not to mention people will probably just share the PDF illegally.
The simple truth is that a $4,000 annual membership fee is a pittance for a USB device manufacturer. You will spend far more than that designing your product and manufacturing it. The people who balk at that cost were probably not serious about building a USB device anyway, and would just "waste" the USB vendor ID (there is a finite number of possible IDs).
I've never found an official public listing of VIDs.
Seems to me that usb.org should provide one as a general service to the USB community, and if a vendor didn't want their VID public usb.org could just list it as "private" (it could well happen that a company wants a VID for internal use only)
The best list I've found for VIDs (and many associated PIDs) is here:
http://www.linux-usb.org/usb.ids
It's updated frequently, but I have found errors, so caveat emptor.
Variations of MIFARE Ultralight cards are becoming quite widespread. For example, huge transport companies employ them as payment cards.
As I get from MIFARE site and Wikipedia there's a full-blown microcomputer inside the card - with a processor, memory, etc. When I move the card close to the reader its field induces current in the card antenna, the card computer turns on and runs some complicated protocol to communicate with the reader.
That's all cool but could I write my own program that would run on such a card and do something useful a card doesn't do by default? What are simple examples of what such program could do?
The microprocessor based contactless cards are easy to work with, our company has had good success with the the NXP JCOP product line with wireless capability (this wireless capability is provided via MIFARE technology, but these are microprocessor cards and not MIFARE Ultralight cards.) The JCOP cards let you install your own Global Platform or Javacard cardlet apps on the card and commmunicate with them wirelessly using the ISO 14443 A protocol.
MIFARE Ultralight cards just store data - you can't write a program to run on the card. The MIFARe Classic and Plus variants are similar. MIFARE ProX, SmartMX & DESFire Cards are all microprocessor based cards.
The memory only cards are easy to work with - readers and cheap & easy to obtain via eBay or similar. I'm not sure how you develop with the microprocessor based cards because we've never used them.
I think you need to talk to MIFARE about that. My guess is that have some sort of software development kit as well as a special programmer for the card for potential developers. I haven't fully perused their site, so they may not allow individual developers to work on it, but do the work themselves as a service.
When selling a software package that requires hardware, typically dedicated hardware (could be a VM), the buyer typically has to buy the server it will run on. So the total cost of ownership (focusing on the capital expense) includes the hardware in addition to the software.
For example, a $3000 bug tracking package might need a $1500 server to run on, total cost is $4500. The hardware is 50% of the software cost, or 1/3 of the total cost.
Of course, with open source packages, the ratio is inverted.
So the question is: does it matter? At what point does hardware expense affect the sale of the software?
Why require hardware at all?
If hardware prices are a big breaking point in your sale, perhaps offer a hosted solution and factor the price into this service.
"Software As Service" might really help you makes some sales for customers with limited infrastructure.
The ratio depends on which part of the equation is the commodity part.
If you are selling a software targeting solving complex problems like air traffic control that can run on any servers, you might want to sell it packaged with the hardware for a bit more, but since the hardware is the commodity and can be obtained from other vendors, the price ratio will be heavily skewed towards the software.
If on the other hand you are OEM and your goal is to sell your hardware, you can use the software as the commodity to bring more value to your offering. For example, you can sell high-endserver machines and add a preconfigured LAMP stack to make your offering better. In this case, the price is heavily skewed towards the hardware.
"typically" - that's an assumption.
And the cost can be more than just hardware and software if there are service or renewal fees involved. This can be true of open source as well, because a lot of companies like to pay for indemnification and services.
If you buy hardware plus operating system, the decision to go with Windows or Linux comes into play.
I doubt very much that there's a meaningful, fixed ratio. It's an interesting question, though. You'd need a LOT of data, and I don't see that it's been gathered into one place.
I had another thought in a comment below that's worth surfacing. There's another consideration that's becoming more important all the time: power consumption. Some corporate data centers can't add a new server without retiring an old one or by reducing power consumption some other way. Being able to deploy a new software purchase on an existing server is big plus. If it can be virtualized, even better.
So it's not always hardware and software. Other economic considerations, like power cost, have to figure in.
I have found that hardware costs rarely affect the decision.
Small companies can get away with reusing servers.
Large companies already support clusters of servers, increasingly with VM capability so it's easy for them to deploy/redeploy software to as much hardware as necessary.