Unfortunately, the package is just a mono-wrapped version of keepass2, and in my experience runs equally as bad, if not worse, than keepass2 under WINE.
Having used both for several months, I found the only workable option for myself was converting the database to KDB 1.x and using KeePassX.
That's a good point. The reason for it is because this service came about from our previous Facebook pages we created for colleges that ppl could use to do essentially do the same thing. Every time someone makes a comment you can see who it is, allowing people to learn about each other and socialize in the comments, around the confession. The posts basically allow ppl to meet new ppl.
Although much simpler, this reminded me of a website from ~2008 which did the same thing with the now defunct Liberty Reserve combined with a basic coin flip game.
The site is, surprisingly, still online[1] and now accepting Perfect Money in place of Liberty Reserve. Unfortunately, they seem to still be using MD5 hashes even years later, for example:
As it stands, the majority of CA's do not verify any of this information, besides a very cursory email verification.
Exceptions would obviously include higher priced (OV/EV) certificates, which are no different cryptographically. Even the CA mentioned (GlobalSign) states this fairly clearly on their website.[1]
Very cool, is there any ETA on parallel execution and background execution (ex: Currently, you have to stay on the page while the recipe executes.)
Additionally, it seems that the more servers you have, the more you pay per server. Our use case would be several sysadmins (less than 5 users) accessing 50+ servers, which would mean we'd be paying ~$3/server/mo, whereas on the lower plan it works out to literally half that, at ~$1.5/server/mo, is pricing already finalized?
Thanks. Parallel execution and background will come at the same time. It is the next highest task in the queue after the API is completed. Additionally execution output (both stdout stderr) will stream via websockets, so no more timeouts.
In regards to pricing, our philosophy is the more servers you add, the more value Commando.io provides. Additionally our lower tier plans are discounted heavily since those are catering to smaller organizations, usually running $5 or $10 a month servers on DigitalOcean. With that said, pricing is still being tweaked and tuned, so absolutely open to suggestions.
The term 'Gig' is a registered service mark (held by Fiverr) for uses related to "Operating on-line marketplaces for sellers of goods and/or services" [1]
While this might not be a big consideration right now, this is almost a guaranteed loss in a UDRP/WIPO case against your domain, since you're in a very similar space. It might be a good idea to weigh your options prior to launch, as rebranding will inevitably become more difficult as you acquire users.
I'd rather not get distracted by potential issues like that for now. If GigYard gets enough users to upset Fiverr over a potential registered service mark conflict, I'll consider that a good thing.
Not a reseller, owns their hardware and operates their own BGP network (with route optimized bandwidth/peering none the less), provides out of band management (VNC) and direct access to MRTG graphs etc.
Although they specialize in FreeBSD/OpenBSD and market heavily toward that crowd, they also offer the ability to install your own OS/Kernel if desired.
I wouldn't say they're the DigitalOcean if you're looking price wise, but having tried quite a few KVM VPS providers with FreeBSD, they've definitely been the best so far.
I can't give you any input on the legal side of things, however I commented on a thread about 6 months ago regarding gift card fraud[1] and the assumption that it's a new phenomenon.
With gift cards, especially Starbucks gift cards, it's almost (if not literally) impossible to verify legitimacy. Generally, almost anyone attempting this type of fraud, even at the lower levels will:
- Mask the fact that funds are loaded with credit cards in the transaction log by purchasing gift cards with gift cards.
- Use services[2] which sell residential IP's by location (infected systems) as proxies
Unfortunately for the service your offering, Starbucks has an internal chain-disable feature which deactivates any gift cards "downline" of a fraudulently loaded card, hence it's entirely possible that after conducting a card transfer, even one fraudulent transfer could put the entire balance of your legitimate holding account at jeopardy, and the average Starbucks call center representative will be unable to help you.
Services like Cardpool (also offered in-store at Safeway locations) verify individuals identities prior to cash-in, however even with that the amount of fraud they experience is staggering. To give you an idea, the rate of successful, fraudulent transactions experienced by Cardpool in Safeway stores for 2012 was over 20%, compare to the average chargeback rate on an adult site, which is between 0.5 and 2%
I think you've made a smart move to put your project on hold until you have a better grasp of the entire situation.
DigitalOcean has a solid platform for the price, and we've personally had great experiences with them, with only intermittent downtime when their SFO location first launched.
In terms of the suspension you're referring to, they're an automated detection as far as I'm aware, so it really sounds like there might of been something happening that you were unaware of.
Regarding alternatives in this price point, you aren't going to find many options. If you're willing to step up your budget slightly, CloudVPS[1] and TransIP[2] in the Netherlands have both been great for us, and are still quite affordable considering what they provide.
If you're really stuck within your current budget, you might want to look at EDIS[3], whom we run several Slave DNS/MX servers with. They're about on-par with DigitalOcean pricing and offerings, with a much larger choice of locations, including the US.
Having used both for several months, I found the only workable option for myself was converting the database to KDB 1.x and using KeePassX.