I've found using a subdomain helps with that, spammers will try everything@domain.tld but won't bother trying to brute force subdomains.
However be warned some surprisingly large websites don't support subdomains, for example eBay will silently send user@sub.domain.tld to user@domain.tld and you'll only figure it out by looking at your server logs for rejected mail.
In those cases I have to specifically alias that username@domain.tld to the subdomain.
With this new Apple privacy subdomain maybe eBay will finally fix this.
Because the world runs on incompetence, so it's ultimately unavoidable (best case, you don't know that something important that you're relying on is run incompetently).
> The only awkward thing is when I am in person or on the phone and have to explain that my customer email address
I had one small business aggressively threaten me that they fully owned their business name and I wasn't allowed to use it in my email address.
My solution was to keep my wonderful aliases and dump them. If a business is concerned but nice about it I'll offer an alternative such as plumber@
> The other downside is that it's forward-in only, wish I could proxy responses without setting up a whole new inbox (and outbox).
If you have your own domain most mail providers don't care what username@ you use on your sent mail so you shouldn't need any additional mailboxes (especially if they already offer inbound catch all)
I also use the ReplayAsOriginalRecipientUp [1] extension in Thunderbird which takes the recipient address and puts it as the sender for ongoing communication.
> I had one small business aggressively threaten me that they fully owned their business name and I wasn't allowed to use it in my email address.
I haven't had that, but before I switched to Hide My Email I've had many businesses ask if I was an employee of the business - many people don't intuit the difference between john@bank.com and bank@john.com.
The challenge I have is getting a large enough context window so tool calls work reliably, the local models easily slip into hallucinated JSON tool responses and won't trigger the tools as a result.
Same here. I'm curious what others loving Qwen are doing differently, because it constantly hits this issue for me. It's been great for autofilling blocks, but difficult for me to use agentically.
Can't say I agree with Costco anymore, staff are now rude and needlessly petty at multiple locations which I can only assume is because they're getting squeezed from the top in a similar way to the grocery stores.
It used to feel completely different a decade ago, no teenagers that couldn't care less, now few of them seem to care.
Tyre centre moved to bookings only but you can't call because there's never anyone on the tyre desk. I know because it's always unattended whenever I walk past.
Gas station staff just chat to each other and put out the traffic cones 30 mins before close leaving a small gap.
Everyone now has to scan their card with a single scanner leaving a huge queue outside just to get in.
Register queues go right down to the back of the warehouse with half the registers closed.
Queue again to get your receipt checked and all you get is departing grunt if you're lucky.
It's sad because I used to rave about Costco and bring the cool new snacks to share at work.
Prices are mostly comparable at the grocery store if you are willing to wait until they go on special so I've given up on Costco.
Retention and legal holds: Data can still be deleted even if a retention policy or legal hold is in place, unless licensing or billing is restored first. Do not rely on holds alone to protect unlicensed data.
Surprising it doesn't automatically move into an admin or company lawyer's drive so it can be dealt with rather then a few notifications which will probably be missed and the data permanently deleted.
I can’t see any suggestion that accounts already 12 months since they were deactivated won’t be nuked in July. You’re potentially getting a months notice in the short term.
Looking into the actual announcements, they're not 100% clear but I'd be shocked if they skipped the archival period for old accounts. But also they originally announced this a long time ago and the official page says they've been rolling it out since January last year.
True, but if I was worried about having too many accounts to track down in the next week I would go ask them and also I would have probably started doing something in the last year plus.
I'm seeing so many of these come in with "this is 95% done, just need a couple of minor tweaks for production release"
"Minor tweaks" being fix the layout so it's not messed up if the browser isn't exactly 1920px wide, sometimes these filters and sorting don't seem to work right and the app doesn't seem to refresh new values properly after an action.
No matter the issue it's pre-estimated by the business as "should be a quick fix, for an experienced dev" because they (allegedly) did 95% of the work already.
Just wanted to check in on how we're tracking, I've booked a quick sync meeting for 4:45pm on Friday followed by a release cadence checkpoint meeting for 9am on Monday.
However be warned some surprisingly large websites don't support subdomains, for example eBay will silently send user@sub.domain.tld to user@domain.tld and you'll only figure it out by looking at your server logs for rejected mail.
In those cases I have to specifically alias that username@domain.tld to the subdomain.
With this new Apple privacy subdomain maybe eBay will finally fix this.
reply