- If I am using the 10Duke Identity Provider, how does one of my customers reset their password?
- The default password reset process requires the customer to click on a 'Forgot Password?' link and then enter their registered email address. The IdP then sends a link via email to the customer which takes them through a password reset process. The default security level (which can be made either more strict and more lenient) uses an expiration time-based token and a user secret in the process. More strict security can include e.g. SMS delivered tokens to ensure that the genuine user has required the password reset.
- If we are running 3 separate web applications, do your Identity Provider Support Single Sign-On between them so the user only has to sign in once?
- Yes, the user would log in to the first web application, but in practice they would be actually logging into the Identity Provider. This would then authenticate them and grant access to the first web-application. When the user tries to access the second web application, a similar process would occur and the IdP would authenticate them to the second application. The process is the same for the third (or N) web application. For the user, they only login once and each subsequent authentication happens so quickly it is not normally noticeable by them. Similarly, once they log out of one application, they are logged out of the IdP itself and therefore are logged out of all applications.
- Does your Identity Provider support fingerprint scanners as a method of authentication?
- Yes, the IdP can be configured to include a number of alternative ways to authenticate users. The challenge is harder on the client application side as the protocol and best practises require that clients connecting to the IdP do not know how the user is authenticated. This means that the IdP is responsible for presenting the challenge and the client application(s) must have the capability to present relevant UI and methods for the user to interact. Common technologies and methods usually use "smart card" based approaches.
- Does your Identity Provider allow us to work with companies where the company is a customer and may have a number of people within it who receive a subscription but are managed as a 'group' subscription?
- Yes, our Identity Provider has a particularly extensive model for supporting organisational structures. In this case, the IdP could recognise 'The company, customer' for which there are designated representatives who can login and manage the subscription and to which people the subscription is provided. The number of subscriptions and type of subscription within that group is governed by the Entitlement Service, which working in the SSO environment is able to connect users to their organizations and thus further make the connection between a user and her right to consume the customer organizations entitlement.
- How are clients updated when a new version of the Identity Provider solution is released?
- Changes to OAuth, SAML and other SSO protocols are rare and therefore in most cases there is not a need to update client applications for this reason. Also, the HTTP / endpoint contract that the IdP provides supports versioning, which means that old client versions may be maintained for a time period deemed feasible by our customers without adversely impacting their current SSO service in production.
- The 10Duke IdP supports any social login provider that function as an OAuth 1.0a, OAuth 2 or SAML 2 provider so services such as Google+ , Facebook, LinkedIn, Twitter, Instagram and more.
- Does your Identity Provider allow users alter, correct or delete their profile data?
- Yes, the Profile management/edit screen are fully customisable and allow end users to edit fields such as name, organization, profile picture, password, mobile number, email address, etc.
- Can you apply data validation (address/email address/ profanity etc.?)
- Yes, e.g. email and password validation is a built-in feature (by means of configuration).
- Are users able to reset their own password?
- Yes, an easy but very secure process is provided out of the box.
- Can you restrict access to some of the user's data fields from different apps / sites using the sign in system (e.g. one app could collect info not seen generally)?
- Yes, this is possible using consumer scope privilege configuration (consumer = connecting application + user).
- Can you delete users e.g. if needed for legal reasons. Can you also retrieve their records and history?
- Yes, complete delete and full audit trail features are available.
- Is there any integration with email service provider / notifications provider?
- Yes, e.g. AWS based messaging is available out of the box.
- Does your platform offer diagnostic capability and if so, how granular is this (e.g. can we see down to an interaction)?
- Yes, detailed event based logging and reporting is supported.
- Can you have multiple identities linked to a single user profile?
- Yes, for example you can allow the same user to access your apps from a social profile, such as Facebook, but also directly using an email/password combination. These IDs can be reconciled as one profile in the IdP database.
- Do you provide a customisable database schema for a single user profile store?
- Yes, 10Duke's Dynamic Schema implementation enables a flexible data access service.
- Can all information relating to an individual be easily extracted to ensure that Subject Access requests can be met within statutory time limits?
- Yes, the 10Duke IdP has uses a normalized data model, which makes such actions straightforward.
- Can the service/solution easily record where information comes from and where it may be disclosed to?
- Yes, activating an audit trail and logging to track such information routing covers this and related requirements.
- Does your Entitlement API support the use of digital signatures? If not, what would need to be done to include these?
Digital Signatures are used generally in the domain of cryptography and usually their use is related to ensuring that data has not been changed between the provider and the consuming end. The Entitlement Service uses certificates, encryption and digital signatures in relation to many things, including:
- Encrypting and signing authorisation tokens (licenses) delivered to clients. Clients have a separate public key by which they can decrypt and validate authorisation tokens.
- Hosting a set of trusted certificates, which allows client applications to validate that the service endpoint they are interacting with is in fact the entitlement service. This prohibits setting up a "fake" entitlement service to provide positive answers to authorisation checks. Client applications are built to include a public key that they use to validate the "trusted certificates" response from the Entitlement Service. This mechanism can be used in the system generally to establish trust on client side for any web service in addition to the Entitlement Service.
- Https as protocol scheme.
- How does your Entitlement API govern concurrent usage? For example, can it be set to allow a user to access an application via a web-browser and also access the same application via a mobile client application, but prevent that same user from accessing the application using a second mobile application?
Yes, our Entitlement API can be configured to reflect certain constraints and one of these can be concurrency. Other constraints can include geography, time, device, counting of content access and user state (i.e. logged in, not logged in).
- If we are trying to reward different user types or users who access our content from a particular device, such as a mobile phone, can your Entitlement API be configured to allow 10 pieces of content be delivered to a mobile device and only 1 to web browser client?
Yes, for our Entitlement API, this is a particular entitlement that would simply need to be configured to reflect those particular constraints - a user from a mobile device can access 10 pieces of content and a user from a web browser can access 1 piece of content.
The recommended way to implement this is to define separate product packages for each client / device type, which further allows to use different license models for each.
It could also be extended to different types of content - for example, a user from a web-browser client can access 10 articles and 1 video clip while a user from a mobile device can access 10 articles and 10 video clips.
- Many of our users are just browsing our content and have not registered with us. Can your Entitlement API limit their content access even if we don't know who they are?
Yes, this is possible by means of our Identity Provider and Entitlement API working together. A 'browsing user' is simply a type of user as defined by the Identity Provider.
We define "pseudo roles" for users including categories:
- authenticated user
- last editor
In this scenario the "viewer" role (meaning unauthenticated user) would be allowed certain things, which may be more limited than authenticated user. One such "viewer" Entitlement configuration may define the ability to access (eg.) 3 pieces of content before the client application directs the user to a payment wall.
- Your Identity Provider and Entitlement API are APIs to which we would connect our client applications. The underlying applications for your APIs are proprietary software and are not open source. What happens in the event that we choose to deploy one or both of your APIs, but then 18 months later for whatever reason, we decide to move to another provider? To what degree are we locked in? With open-source we have no lock-in.
If you deployed any of our APIs and then subsequently choose to move to another provider for whatever reason, you are not locked-in, either commercially or technically.
- You own the data.
- Commercially, our APIs are provided on a monthly subscription basis with a one-month notice period so you have flexibility in terminating our commercial relationship. Technically, all of our APIs are standards-based and therefore it is straightforward to transition to a new provider. For example, if you wanted to move to a different Entitlement Provider, the product package definitions can all be exported from our Entitlement API and ingested into a new provider given that they support all requirements that you have. Similarly, user IDs within the Identity Provider can be moved to another Identity Provider. Each migration would involve a migration project, but this is something that we would help you with as you would like us to.
An additional benefit of our APIs, that is not easily found with open-source products in the Identity and Access Management sector, is expert support. Our company provides multiple support channels and packages should you need further assistance after the initial deployment. With open-source IAM projects the integration cost often far exceeds the cost of a commercial solution because disparate, point-solutions are being made to work together. By contrast, our APIs are composable services, designed from day 1 to work well with each other, integrate simply into other, standards-based systems and all stem from the same Java-based development framework, that is itself a mature product with a development guide, roadmap and support packages.
- We use AWS as our default infrastructure provider. Can you deploy your APIs on AWS?
Yes, this can work in two ways. Either you deploy our APIs yourselves onto your AWS instances and then your operations team can manage them. Alternatively, if you prefer, we can deploy our APIs onto your AWS instances and manage them on your behalf each month accordingly to an agreed SL.
This would incur an additional monthly fee on top of the monthly API subscription fee and depends on the size of the deployment. You would pay Amazon directly for your infrastructure usage.
- How scalable is your Entitlement API?
Currently, one customer example has more than 275,000 users generating 15,000+ API license checks per day. Another customer, a video creation service, has 500,000 users generating 50,000 license checks per day. The Entitlement API (and the Identity Provider) can scale easily. We have one proof of concept project underway in which the potential customer has more than 30 million users and our IdP/ENT combination in that project scales well.
- Where does the 'configuration' take place and where are the define product packages and policies (constraints) stored?
Configuration can be done using the REST API or alternatively using the Entitlement Service's configuration UI. Product packages, license models, licensed items, etc entities are stored in the Entitlement Service's database.
- How would your Entitlement API work with the Hybris Entitlement engine?
You wouldn't deploy the two together. Our Entitlement API is an alternative to Hybris entitlements.
- The Hybris Entitlement Engine charges per API call. Do you do that?
No, we offer a per user per month fee, or a flat monthly fee for larger customers. Client applications can optimize the number of API call needed and the value of an API is not related to the number of calls that may be made to it. Particularly in the case of a digital product that is licensed monthly, the client application can be configured to make a license check only a few times each month in order to verify that a valid license existing. With a well-designed Entitlement API, this license validity information can be stored locally and therefore require minimal license checks (via API calls) at the end of each calendar month (or defined subscription period). This allows you to creating a better user experience for your customers.
- If I become a customer using the 10Duke Entitlement API and a year from now a new device is released, for example the Apple iWatch, and I want to deliver a variant of my newspaper's app for that device, what would I need to do?
Once you have your new 'Newspaper' App for iWatch, you would need to define a new licensable product package (eg. 'Newspaper App for iWatch;) and then configure the Entitlements Service (using its API) to include that new package. (As an iOS app, this may be exactly the same as your existing 'Newspaper App' Product Package for iPhones and iPads in which case nothing would need to change, but if the 'Newspaper App for iWatch' product package was unique then it would need to be added as a product package). Once the entitlement rules for this new product package have been defined and configured, that it is ready to be included in the overall product set. This configuration process with take 5 to 10 minutes to do.
- What are some user case examples for the 10Duke Entitlement Service to help me understand it better?
Here are three example use cases:
You sell digital content online via a monthly subscription model.
- users can subscribe to a free account
- once subscribed they are able to access 10 pieces of content
- once they hit the 10 piece limit, they are pushed to paywall where they are required to subscribe to a paid account in order to maintain access to content.
In this scenario, our Entitlement service provides the metering on the subscribed user and tracks their usage before pushing them to the paywall. What is particularly neat is that it supports a 'constraints-based' model which then supports metering against a number of factors including:
- access device type: you may want to provide more content to users on iOS devices than Android devices for some business reason. Our ENT service could allow iOS users to access 20 pieces of content whereas Android users could only access 5.
- content type: you may want to provide un-subscribed users with access to 10 pieces of video content and 3 text articles. Our ENT service will support this.
- user origin: similarly, you may want to provide unsubscribed users, accessing content from the UK, with 10 pieces of video content and 10 pieces of text content before pushing them to a paywall. By contrast, users from other parts of the world can only access 3 pieces of video content and 3 pieces of text content.
- concurrency: if you need to allow a user to access the same content, but from more than one device, our ENT service supports this.
If you think of Spotify, they have a piece of software built in-house which governs which users can access Spotify's catalogue (with or without ads) and on how many devices for each users. Our ENT service can provide exactly the same functionality out of the box.
Selling digital content to 'anonymous' users
Similar to the example above, it may be the case that you have a lots of users visiting a website but you don't know who they are. Our ENT service can still be used to apply a meter to them. The ENT service is an 'identity-based' Entitlement so it has the ability to gradually build up a user provide even if we don't initially have access to their email address. The ENT service can do this initial from an IP address and then build the user profile from there. So this means:
- you can use the ENT service to provide a certain number of pieces of content to an anonymous user before pushing them to a Registration wall, after which they can then be given certain access rights to other pieces of content before being pushed to a paywall (as per example 1).
Selling software applications on a subscription basis to one user with multiple devices.
- You selling anti-virus software.
- Each license you sell allows your customer to use the software on one PC and 2 mobile devices.
- Our ENT service would govern the access of the customer to the application from each device over the defined subscription period. When that period ends, the applications on each device would no longer function without renewal.
- You sell digital content online via a monthly subscription model.
- What is Identity Bridge?
- The 10Duke Identity Bridge is a cloud-based service that provides Single Sign-On (SSO) capability for companies using Google ID to allow their employees to seamlessly access both Google Apps for Work and Microsoft Office 365 without the need to login separately to each service.
- How does it work?
- It is very simple to set up. A companies IT admin team only needs to provision those employees requiring SSO access to both Google and Microsoft applications in Office365/Azure AD. Then the domain in Office365/Azure AD needs to be configured for federation. That's it.
- Is it an API?
- No, it is not an API but more of a translation or relay service that makes sure that Azure AD can understand the user/profile information that is coming from Google and use it for authentication.
- How do I configure Microsoft AD to use it?
- It a very straightforward process and step by step instructions can be found on our Identity Bridge product page
- What applications can I use it for?
- It can be used with any online application that can serve as something called an OAuth 2 consumer. If you have any application to which you'd like SSO access, get in touch and we can let you know if we can connect it to Identity Bridge.
- Is there a User Interface or portal that my employees will need to log into?
- No, Identity Bridge is a background service so there is no portal that your employees will have to access or login to separate. Once Identity Bridge is configured, it works seamlessly and invisibly in the background so there is no change or disruption to your companies normal working practices.
- What SLA is provided with it?
- Identity Bridge comes with a target 100% uptime guarantee and is run on Amazon Web Services.
- How is it priced?
- It is priced per provision user per month.
- What are some typical use cases for File+?
File+ case be used for:
- Video transcoding tasks such as accepting user-uploaded videos or generating output video file to support playout on multiple devices.
- Audio transcoding to allow uploaded audio files to be played back on a variety of device types, regardless of format.
- Mashing or producing composite media from several input media assets.
- Creating thumbnail images for videos and images automatically on upload.
- Inserting and updating metadata in media files.
- Image manipulation including common tasks such as cropping, resizing, rotating, etc.
- Doing CAD file format conversions.
- What industry sectors is it typical used in?
File+ can be used in any market where there are large datasets and have a need for file storage or management across a wide geographic coverage and a need to transfer large amounts of data from A to B. These include:
- Media companies, particularly with large video assets.
- Gaming companies, needing to push executables as well as updates to executables.
- Anti-virus companies, needing to push executables as well as updates to executables.
- Law firms storing and managing large amounts of documentation in the cloud.
- Architects storing and managing large design files in the cloud.
- Healthcare companies storing and managing large image files in the cloud.
- Building and construction industry storing and managing large CAD models or BIM files in the cloud.
- How does it compare to using web upload form for placing files into the cloud?
- A web-upload form normally receives a one file at a time or occasionally multiple files upload. The scalability of such a solution is limited. As File+ is available via a RESTful endpoint, it can be incorporate much more flexibility, into a client application and cover a much wider range of use cases.
- Is File+ an alternative to FTP?
- ftp enables file transfer/copying and is much more limited in scope than File+. There are a number of known issues with FTP including security, poor scalability in terms of limitations of the size of file that can be transferred and how many files that can be transferred. By contrast, you can use File+ as a more flexible, scalable solution that gives you as a developer a dedicated file management application rather than just a limited transport mechanism.
- Is File+ an alternative to Rsync?
- Yes. Rsync has well-know scalability issues. It has limited efficiency (for example, just building an index of what needs to be synched, is slow) whereas File+ has much broader scope and can be applied to a wider variety of use cases, in addition to being able to keep files in sync.
- Is File+ an alternative to AWS S3?
- Yes, File+ offers very similar functionality to S£ but can be used on premise or in private cloud deployments. AWS is secure, as it uses client-side encryption, but if you encrypt data before transfer then they are equally secure. The AWS S3 API doesn't offer conversion features as well as file management features so with File+ you arguably get more out of the box. If you wanted to run a hybrid cloud, using AWS S3 but also another set of storage servers, you could use File+ to manage both.
- What deployment models are supported by File+?
- File+ can be deployed in a variety of ways including on-premise, in a private cloud or in a hybrid cloud.
- What is the 10Duke Reporting API?
- It is an Enterprise-grade application that is capable of distributed reporting, data storage, analysis, and processing. It also provides a framework for developing reports and implementing specific business intelligence or related reporting analysis from collected data
- What output formats does the 10Duke Reporting API support?
- It supports XML and JSON
- Why would I used the 10Duke Reporting Service rather than Google Analytics?
- The 10Duke Reporting API is an API, so you can create a tailored front end to show exactly the type of data that you want to analyse, rather than being limited by Google pre-defined reporting framework. You can also deploy the 10Duke Reporting API on premise, in a private cloud or to a public cloud so it is more flexible that Google.
- How are analytics runs scheduled?
- They can be triggered either by configuration or by external scheduling using cron.
- What databases does it support?
- The 10Duke Reporting API supports MySQL, PostgreSql and HSQL databases.
- How is it priced?
- It is normally priced on a usage-based model, according to the number of reporting events generated.
- What is it?
- The 10Duke SDK is a rapid application development framework. It has been developed and refined to enable to rapid and inexpensive development of advanced online applications. Our SDK present developers with the ability to quickly, build and deploy, quality, stable and scalable web applications. The 10Duke SDK also allows easy integration with 3rd party applications and expansion to other platforms.
- Why should I use it?
- Increase development speed - Reduce the time it takes to get to market, and utilise developer resources more efficiently.
- Increase stability - applications built with the 10Duke SDK benefit from industry leading stability.
- Built in support for high usage - applications built using the SDK will effortlessly handle traffic spikes, ensuring your application stays live when you need it most.
- Easy to use - Developers will find the SDK simple to use, even with little Java knowledge or experience.
- Who Can Use It?
- The SDK is designed for anyone who has medium level Java development skills and is familiar with the existing JDK SE 6.
- What can I build with it?
- Anything you can imagine. The SDK has been used by companies worldwide to create huge online sports communities, video sharing services, online support forums, product distribution sites, and much more. To see specific examples of applications that have been build using the 10Duke SDK, please view our case studies.
- What support is provided?
- 10Duke provide free basic email support or you can post your questions in Stack Overflow and we'll respond there. Additional support is available through regularly updated documentation, and through support subscriptions. If you'd like a premium support subscription, please contact us.
- How do I buy it?
- Licenses can be purchased by contacting us.
- Can I get help building my application?
- Yes, 10Duke provides professional services in support of its core product line. For further information and to discuss your project, please contact us on firstname.lastname@example.org
- How does it relate to PHP?
PHP is a free programming language and as such is widely used. Whilst the
10Duke SDK (Java) SE and PHP can be used to create similar applications, the
10Duke SDK (Java) SE has several advantages:
- PHP has several known scalability issues, which the 10Duke SDK overcomes.
The 10Duke SDK offers you a lot more than PHP does
- We have a built in transcoding engine, CDN and lots of other great "out of the box" features and capabilities.
- PHP has major security flaws allowing hackers to easily attack applications, therefore increasing maintenance time
- Coding using PHP is more time consuming and resource intensive than using 10Duke SDK.
- How does it relate to Glassfish?
- The 10Duke SDK works well with GlassFish! GlassFish is an open source application server project lead by Oracle. They are creating an industry leading Java compatible, enterprise quality, application server that is dedicated to the efficient execution of procedures (programs, routines, scripts) for supporting the construction of applications.
- Is there a .Net version?
- There soon will be! We're developing it right now. If you want to be notified as soon as we have a release date or would like more information, get in touch with us. We have a few .net libraries already available and the SDK roadmap can be found here: https://developer.10duke.com/sdk/roadmap.jsp
- Can I buy support?
- Yes, we offer a full suite of support options. For more details on what is available and to get a price, please contact us.
- Can I buy Professional Services?
You can indeed. We offer professional services that span the whole process from planning through to technical development.
If you're looking to have a Web2.0 application built quickly, then get in touch.
- What applications have been built using the SDK?
- Applications such as video sites, social networks, forums, worldwide digital campaigns, interactive games and quizzes, video editing and mixing tools and lots more. Check out some examples here.
- Who owns the IP in my app?
- The clues in the question... "my app". You retain the IP in your app, and we retain the IP in the 10Duke SDK (Java) SE.
- What libraries are included in the SDK?
- Please visit our developer site https://developer.10duke.com/sdk/api/
- Why would I use the 10Duke SDK when I can use PHP or RoR for free?
- The 10Duke SDK is tried and tested and has built in stability and scalability that RoR and PHP don't. When your app starts to take off, you need to make sure it doesn't go down, and with R0R and PHP you will need to spend a huge amount of time ensuring that doesn't happen. With the 10Duke SDK you can sit back and relax in the knowledge that your application will scale.
- What's the difference between Smart Feeds and me just collecting the data in a big Hadoop-based data lake and executing queries against that data?
Smart Feeds offers much more flexibility. It supports several ways of processing received data, including:
- Storing data to a big data database, e.g. for analytics and data mining
- Rules based processing and alerts
- Publish-subscribe, e.g. for collecting interesting data to subscriber feeds
- Real-time feeds, i.e. viewing incoming data as it is received
- Does Smart Feeds support authentication?
- The API supports several authentication and authorisation mechanisms, e.g. the events can be signed and/or encrypted with device certificates.
- How can I incorporate data processed by Smart Feeds into my client application?
- Is there typically meta-data associated with raw event data or is this added by Smart Feeds automatically?
- Raw event data typically contains some metadata, e.g. device or user identification and some basic attributes. However, this is not required by Smart Feeds. Smart Feeds adds basic metadata like event received timestamp. Smart Feeds can also be configured to add metadata required e.g. for adding dimensions that can be used for organising and processing the events.
- Is Smart Feeds a microservice?
- Yes. It consists of several small components, with each component serving one well-defined purpose, and the components communicate via well-defined interfaces. Customer systems can be built by stacking these microservices. Existing services can be customised and new services can be added. Also, each component can be run in multiple instances for providing high availability and scalability.
- What are some typical use cases for Smart Feeds?
Smart Feeds can be used for:
- Capturing and turning events captured by RFID tags data into usable management information
- Collecting, distributing and making sense of high volumes of events generated by sensors in watches or clothing
- Gathering the data generated by gameplay and making this socially shareable, increasing engagement with the game
- Measuring distance travelled, route information, fuel consumption, utilisation rates and more from data generated by GPS sensors for use in a telematics application
- Equipping greenhouses with technology able to automatically adjust variables like humidity, heat or light and nutrients quality
- Equipping farms with technology able to automatically adjust variables like humidity, heat or light and feed the animals
- Creating smart appliances that automatically order replenished products from the Internet
- Improving the living conditions of old and disabled people by adding new methods of non-intrusive support based on specific needs and reports (automatically generated by wearable technology) like heart rate, temperature, breathing patterns, activity level or sleeping habits
- Creating technology able to monitor vital signs, habits, health conditions or activities and send data for analysis
- How is it priced?
- Smart Feeds is priced on a usage-based model, according to the volume of events generated.We offer a free tier to trial the service.
- Can Smart Feeds be deployed on-premise?
- By default, Smart Feeds is a multi-tenant, cloud based API accessed through a RESTful endpoint. For Enterprise use cases it is available to license and deploy on premise.
- Can I use 10Duke APIs myself or do I need to hire 10Duke to use them?
- Our APIs are designed to be used by companies themselves and we've tried to provide as much support information as possible to help development teams use them. If you need our help, we are more than happy to assist but this is entirely up to you.
- I am planning a completely new online application - can I use your products?
- Yes, that is exactly what our products are designed to do. Depending on what your creating, it may make sense to use one or more of our APIs in combination.
- I am based in the United States and understand you are based in London and Helsinki. Can I still use your products?
- Yes, even in cases where we work closely with our customers on an application, we normally work using a distributed team and therefore being in different locations isn't normally a big issue. We work with teams in the US (east and west coast), across Europe, India, Japan and SE Asia.
- I don't have a technical team of my own. Can I outsource the building of my application to you?
- Yes, we have a dedicated professional services team who sole focus is assembling 10Duke APIs to create new applications on behalf of our customers.
- What is 10Duke's VAT number?
- 893 8849 44
- What does '10Duke' mean?
There is some debate within our company in regard to this. Here are the
alternatives - please select the one you prefer.
- The mascot of Java is the Duke. When we named the company, there were ten of us and well.....
- 10Duke means 'cool' in street lingo
- 10Duke is a named crater on the dark side of the moon. Rumour has it there is a fully stocked fridge there
- When cool people sneeze, they say 10Duke. We like that, so we used it
- In the ancient Hittite language which ceased to exist around 1200BC, 10Duke meant "Web 2.0"
- D=UKE^10 is one of Einstein's lesser known equations for perfectly done toast.
- '10Duke!' is what members of the Finnish national hockey team shout when they score a goal against Canada. It doesn't happen very often.
- We didn't have a name, so we placed a Porcupine on a keyboard and used the first thing it spelt... (No animals were hurt making this up...)