Daniel Iser

Founder & Lead Engineer @code_atlantic. Our software has powered 31.5B+ interactions across 700K+ websites. Building WordPress plugins, developer tools & SaaS.

[Daniel Iser @daniel_iser]

@KatieKeithBarn2 @WisprFlow @tryvoiceink FYI parakeet processes 1hr of audio in ~30s, and a 1 minute audio sample should take less than ~0.25s.

So faster than you can talk by a lot unless you add AI enhancement latency.

[Daniel Iser @daniel_iser]

Make sure your using this model, and turn off AI enhancements if you want raw speed. AI Enhancements here will do things like remove extra ums, or smooth out transitionals in your sentences etc. It can of course also trigger automations based on prompts but it adds latency either way.

If you use AI Enhancement, ensure you choose a really fast model like Haiku or GPT 5.5 fast to reduce the processing delay.

[Daniel Iser @daniel_iser]

@NeuralForges @EXM7777 It’s all AI slop no matter the percentages haha. 🤣

[Daniel Iser @daniel_iser]

Then your neglecting like the media to include gang violence in your conclusions. Gang violence accounts for majority of “mass shootings” in the US but don’t get headlines. And nearly all of those are non-white offenders.

All of the reports claiming whites made up majority of ~200 mass shootings over 4 decades ignored the 30+ mass shootings per year in just Chicago to make that point. They literally have to change the definition from “mass shooting” to “mass casualty event” and even still report the findings under “mass shooting”. Further they purposefully ignore gang violence with a narrower list of criteria for “motivation”.

Simply put they boxed in the stats to overrepresent whites and underrepresent anyone else.

Every gangland shooting has potential to be a mass shooting for fuck sake. They spray indiscriminately into crowds to hit one person (or no target at all).

[Daniel Iser @daniel_iser]

True, it was originally just intended for the crazy stuff my own agent was trying to generate, hence "agent" not "agents", but as a micro service was quite useful to all the persistent agents in our mastermind group.

Historical connotations aside its actually fairly accurate description.

[Sean Taylor @seantaylor___]

@SharrellAnne2 I would love to get you a round trip flight to DC to visit him. Please message me.

[Daniel Iser @daniel_iser]

@rnelson0 Exactly. Also playing with a clean check from @patchstackapp or @wordfence before an update is allowed to be installed.

Currently calling these checks "Gates". More gates between update and your system the better likely.

[Daniel Iser @daniel_iser]

For a long time #WordPress has pushed auto-updates, but that needs to change.

What used to be the secure thing to do has now become the vulnerability.

Based on recent supply chain attacks (NX Console specifically), things like signing & verification means nothing if the developers git SSH keys were compromised.

Are there any other changes that can the #WordPress community and https://t.co/GgYapw2c8h specifically do to mitigate these attacks in our space?

https://t.co/AV7IvTGNZ1

[Daniel Iser @daniel_iser]

@Nascaline5 Similar, just put this together.

[Daniel Iser @daniel_iser]

@WarrenLNaida None of our ecommerce sites would dare auto-update. Too many bad experiences over the past 15 years to trust that any longer.

[Daniel Iser @daniel_iser]

@photomatt How about something like this, simple solution, still allows auto-updates.

MVP working already.

[Daniel Iser @daniel_iser]

@rnelson0 Working on something that handles this nicely.

[Daniel Iser @daniel_iser]

Great to hear.

The thing that would prevent issues like this on NPm is automated scans sitting between release publish and distribution. A delay in distribution of just 20 minutes would have prevented the most of the damage.

Something like Sentry or PatchStack scanning before they are served would be ideal.

That on the table?

[Daniel Iser @daniel_iser]

@framerius @DanielBlancoSWE @thibaultbessonm Until it has the info in its vector store already (which it does). Also if you rely on the visitor to come to your site for them to buy or even sign up for your mailing list based on that question, Google is now going to keep that traffic and conversion for themselves.

[Daniel Iser @daniel_iser]

@carlhancock @techjewel Interesting. Someone actually knows legal terms & processes that you insinuated they must not understand and it must be an AI.

Funnily enough only thing AI did was make it nicer sounding.

Ask me how I know "Kit" has no bearing on the marks protect-ability... (Popup "Maker") 🤷‍♂️

[Daniel Iser @daniel_iser]

@carlhancock Agree with most of what you said, WP repo allowed another "Popup Maker" plugin which constantly causes issues.

But @techjewel is right in this tweet,. FluentBoards superseded it, by a lot. Further you both make forms, definitely checks all the boxes you pointed out.

Which immediately made me wonder should you be considering name changes for GravityBoards as well?

https://t.co/UtP127aZYW

[Md Shahjahan (Jewel) ⓦ @techjewel]

By the way, we released FluentBoards long before GravityBoards. So not sure how that will work.
I am bit confused about the Kit only and how that is creating confusion as it's just a free addon (not a business).
I am searching for a new name as I truely respect you and your opinions.

[Daniel Iser @daniel_iser]

I appreciate the detail, Carl. For the record, I’ve been through the trademark process myself, including appeals and defending denied applications, so I’m not unfamiliar with how painful or expensive it can be.

Also worth saying: Zack is a friend, and I have a lot of respect for him, Katz, and GravityKit’s right to protect their brand.

My only disagreement is with what the registration proves. It proves GravityKit is a protectable unitary mark. It does not automatically prove that FluentKit is confusingly similar, nor that the broader [brand] + Kit construction is off-limits.

That still turns on the normal confusion analysis: the marks as a whole, the strength/weakness of the shared element, commercial impression, product proximity, buyer context, and actual marketplace confusion.

And “Kit” is doing a lot of work here. In software, it’s a common/suggestive term for a bundle, toolkit, suite, or utility set. So I agree the strongest concern is not “Kit” alone, but the combined pattern of FluentKit + FluentWiz sitting near GravityKit + Gravity Wiz.

That’s a fair concern. I just don’t think “GravityKit is registered” gets all the way to “FluentKit is clearly infringing.” It gets to “this deserves a serious look,” which I think is where we actually agree.

[Daniel Iser @daniel_iser]

I agree the stronger argument is the combined pattern, not any single word. But that cuts both ways.

FluentKit + FluentWiz resembling GravityKit + Gravity Wiz may be a fair concern.

But Gravity Forms + GravityBoards also resembles Fluent Forms + FluentBoards, especially when FluentBoards came first.

So if we’re judging patterns and ecosystem proximity, FluentBoards can’t be dismissed as irrelevant while FluentKit is treated as obvious confusion.

Either common/category words under different house marks can coexist, or the pattern argument applies consistently.

[Daniel Iser @daniel_iser]

I think the stronger point is the combined pattern of FluentKit + FluentWiz sitting near GravityKit + Gravity Wiz, not “Kit” by itself.

“Kit” is widely used and descriptive in software. If Jewel is already acknowledging the concern and considering a rename, that feels like the practical win without turning this into a fight over common naming conventions.

I get protecting a brand. I’ve dealt with similar confusion myself. But there’s a difference between defending distinct marks and implying ownership over naming patterns used all over the software space.