FlareWP is solidly in a beta phase, and I’m using it on a few personal sites of mine with success. Has anyone done a pre-launch plugin sale before? Thinking that it might make sense to put this in public beta for others to tests out before we go fully public.

FlareWP is beta ready, and I’ve been trying to think about my next move. Does it make sense to do a beta program? Sell licenses, and allow people to lock in a deep discounted rate? I think that’ll allow me to ensure there’s interest, and also get some feedback before it’s “done”.

Quick update on FlareWP. I refactored the entire flare system to make it possible to create flares based on a search query, instead of grouping by event type. This adds a TON of flexibility. Spent a fair amount of time making the interface extend-able. Super excited about this! https://t.co/tno7ORYxcX Moments after this recording, the flare fired, sending an email:

The interface has started to shape up a bit further now. events, event logs, and requests can all be filtered with a powerful search syntax. You can click on most params to automatically filter by that param. This makes it possible to quickly see similar events. The search syntax was crucial because it makes it possible to do the upgrades to flares. Currently, you can only fire flares based on event types. It works alright, but I quickly found I wanted a lot more control over what events were auto-sending in my flares.

FlareWP’s interface is starting to come along. There’s still much to-do, but it’s cool to see the app starting to take shape.

Hey I know what this plugin needs! ANOTHER meta table!

Hermes: With a warning label this big, you know they gotta be fun! #futurama

(Alt text, and context in the thread) alt: Dear Developer, This class is a powerful tool that can query the database tables in FlareWP directly, however
it does not utilize a cache in any fashion, and as such should be used only in the rare circumstances
the existing database model absolutely cannot do what you need.

Beta testing FlareWP has been really interesting. You just kind of let it run, and it sends reports back with errors that happen on the site, including its own bugs. So it’s been a lot of activate, wait for flares to fire, take notes.

It’s been Really cool.

A rather curious challenge with FlareWP is going to be what happens when a site is being DDoS’d? The system adds a relatively light load onto a site during runtime, but if events are being written like crazy because of an attack, what should happen? #WordPress I think that FlareWP is be in a unique position to not-only detect when an attack is happening, but also change its own behavior based on the attack, and send a flare to let someone know “hey, your site is drowning here!”

FlareWP has logged about 637,000 on a particularly busy site we maintain @DFS_Web – almost all of those are doing_it_wrong notices. Evidently the people who built this site before us didn’t build the site with WP_DEBUG enabled. Oof. The cool thing, however, is I was able to break it down into 9 distinct errors, and make GitHub issues for each one. Now we can target them one at a time, purge the log, and be good to go.