@fabrohl Dunno. I’ve felt like I’ve been promoted to general instead of being on the front lines. Different thinking, different learning.
If a tool can quickly solve a problem, move on to the ones it can’t do by itself?
I’ve been a @WordPress supporter for 13-14 years straight, but after having built a couple Shopify stores and a Laravel application with little more than my voice, I doubt I’d start a project with WP at this point.
So weird to finally have that sink in.
I buy software for support and bug-fixes, not just the code/ui. If these alternatives slow me down even 30m because the 'hacker' missed my edge case, it’s already costing me more than just subscribing.
Do you, but I’m not firing my housekeeper just cuz dude vibe-coded a better mop
A famous link building agency ("one that everyone in YC uses") is charging founders $1,500/mo for "25 backlinks"
I pulled their @Ahrefs report today:
- only 3 real links after months
- 22 unindexed spam directories
😬😬😬
Very common in WP. Few things you can do:
1. accept it as 'leakage' and understand that’s the price of being able to sell code for money on the internet. Plenty of people will pay, some dipshits will exploit the system. Walmart accepts a certain amount of shoplifting (billions) every year. They're doing ok, last I checked.
2. per @SM4B_eu, key that shit (but a savvy dev could work around that, but a savvy dev probably isn't buying your theme anyways). @gravityforms does this well.
3. Sell a platform with a theme activated on the site, not the theme. Include hosting and use multisite or multi-tenancy. If they don't pay or cancel, website gets shut down. You can do this on top of your current offering.
No refunds is harsh and the purchaser can just chargeback anyways. Banks will side with the purchaser more often than not. It also threatens your relationship with your paying customers. Some people will want refunds for perfectly valid reasons, and you don't want to ding those relationships (and your rep).
My suggestion? Code in a backdoor to the theme where you can brick the db if a public user visits a specific url query (or redirect the home page to your favorite NSFW website).
Half kidding on that last one ;)
I’m a 14-year WordPresser but I’m not a dot-commer.
Interested in what the .com onboarding looks like, what search looks like, if there's dark mode, what the AI options are right now.
I don’t think that’s what you’re asking for, but I’d be interested in meeting you and seeing what problems you’ve been tasked with solving.
Might be some insights in the exchange. If you have a slot for a kindred spirit, holla at me.