riteshpatel

Super excited to announce our Ticket Fairy 3.0 platform. We've been working on this for years. AI agents, embedded banking, credit, enterprise full-stack software for event marketing, ticketing, ops and more.

Our new dashboard rolled out officially today and all of the 3.0 features will be rolling out over the coming days and weeks. There are a LOT of them!

We are very much alive :)

https://www.ticketfairy.com/event-ticketing

We learned this a few years ago when clients starting using emojis when saving their content and it got truncated. Very quickly converted everything to utf8mb4!

You win the internet today! Coming from a British-born Indian, I hate that phrase so much.

Yikes :O

I could just never get used to Ruby syntax and how wordy it is.

PHP/C/perl-style syntax just feels much nicer/more natural to write and I've never been able to break out of that.

I guess it comes down to personal preference and what you started coding with.

We changed our tables to utf8mb4 specifically for emoji support

If you know anything about cameras and low light photography, the sensor shift OIS is a HUGE deal, especially combined with an f/1.6 lens. Instant purchase!

Is there a reason for a 10 minute cache duration? Even 1 minute would be fine from a performance point of view

Noticed this recently when doing an ES6 course. So many additions look similar to modern PHP!

It only tracks if the Zoom window has focus, not via facial recognition. How is that bad?

Sounds like missing indexes to me if outages are that frequent.

It depends on the region but it can be as high as 30% from what I've read

I say eee gee and eye eee for e.g. and i.e. when reading those out loud. Doesn't everyone?

I would say that development of JSON fields in Postgres and MySQL was accelerated by the adoption of Mongo.

Speed to market/first version using JSON stores is attractive, especially when you're still prototyping your product and won't have an idea of exact data structures until there's been some real world usage.

This site is really well made! Nice job!

Relax :)

This is what you need to know: https://www.cooleygo.com/so-you-owe-thousands-in-delaware-fr...

You should owe $400 ish based on issued shares and assets.

Pretty sure that's because in some cities the driver is dispatched by a local car company and the driver works for them, not Uber. I've seen that in a few places.

I like how you think :)

Not being PCI compliant, for one.

> These kinds of things might be just random. You see probably thousands of ads during the day, but most of them are not registered by your conscious mind. Only when there is a notable connection to something, your brain wakes up and you register the ad.

This is similar to the Cocktail Party Effect

https://en.wikipedia.org/wiki/Cocktail_party_effect

I bought it the other day :)

Something I just saw in my news feed that'll also help to give more insight:

https://medium.com/jme-venture-capital/meaningful-vc-exits-2...

VC firms invest other people's money and those people have money in a specific fund entity. Each fund has a specific structure that has various rules on stuff like minimum investment sizes, ownership and time to return the investors' money.

Also, as 9 out of 10 investments, on average, will fail, the 1 that wins has to be big enough to balance out the losses, plus make a profit for the investors that's much greater than putting their money into public stocks, bonds, banks, etc. That's why each investment has to have the potential to be a billion-dollar-plus company, or it doesn't make sense to make the investment in the first place.

Very different from angels who are a) happy to wait b) happy to get 3-4x on their money.

The reason single co-founder companies are less likely to be accepted is that, once you start to get to a certain scale, there's just FAR too much work for one person to do.

We're already experiencing this. There are two of us and we need an extra 24 hours in the day to get everything done.

Get a co-founder if at all possible, it'll save your sanity.

Exactly, or their phone only syncs emails back a week/month and they bought the ticket months before the event. Loads of scenarios where this can happen when you run a consumer-facing ecommerce platform

As a platform that sells tickets to events (https://www.theticketfairy.com/), I feel that I should make a counterargument to not making users create an account.

Our checkout process requires no existing account, so you click on the buy button, enter your name, email address and billing info, and you create a password at the end, after which you DO have an account. We feel that this is much better UX than most other ticketing sites that send you to registration forms before you can continue the checkout.

We used to receive many, many support requests from people who'd lost the email containing their tickets. We then added order history and the ability to download their tickets by logging into their accounts and this resulted in a massive drop in support emails.

Another key point is that most people realise they've lost the ticket email only a few hours before the event is about to start, so we get very panicky last-minute emails from people freaking out that they're not going to be able to get in. Just giving people the option to log into an account and retrieve their tickets not only dramatically reduces our workload but also provides them with peace of mind.

We're adding 3rd-party login shortly (primarily Facebook) but will keep email/password as an option. However, even with 3rd-party login, we'll still need to confirm the email address as most people are used to email as their delivery method.

Saying all this, most of the advice in the article is valid and we follow many of the points. Our username is the email address and we enforce HTTPS on all pages (with HSTS headers).

It's nice having cheap/free DNS from people like Rackspace and Amazon, but situations like these make you realise that it's sensible to use a company like Dyn (http://dyn.com/) that are experts in highly-available DNS, rather than something that's a small part of a hosting provider's services.

It's easy to forget that you can have redundancy in your load balancers, web servers and databases (replication, multiple data centres, etc), but DNS is how you're found by the rest of the Internet.

No DNS resolution = no one reaches your expensive, lovingly-crafted infrastructure.

Hey Patrick,

Any chance this is possible for us as well? This is the only reason we're using PayPal for the majority of transactions at the moment.

Thanks, Ritesh

A+ without any changes, whoop :)

https://www.ssllabs.com/ssltest/analyze.html?d=theticketfair...