It’s either redacted or not. There is no "bad". The text is either there or it isn’t, sorry but this is a binary option and not on a spectrum from bad to good.
Maybe “attempted” would be more accurate? I personally don’t mind the “bad”, I get what is meant by it.
But since we’re talking about accuracy: I don’t agree on redactions being binary. You can redact with a pen that under certain lighting still reveals the text; you can redact parts that are easy to reconstruct when you have additional information; you can redact with a pen color that over time loses its function; etc. The “perfect” redaction would perhaps leave no clues as to even how much text was redacted? It seems to depend on the goal and context of the redaction, whether it achieves its purpose or not.
I still think that the word redacted is meant to destroy the original text, it might not remove the metadata (e.g. length).
Redaction is done mostly in ways with a possibility to reveal the underlying text, but all this is not redacted in my understanding of the word. I always liked the english word for this – the german word "schwärzen" just means to "blacken" the text and this was never the same for me.
But after further research I must agree with you, it just means to obscure or remove, but not clearly just remove. I have been using it for years in a stronger meaning that it's really meant.
One more but: we hopefully can all agree that putting a black bar over some text which still is just copy/pasteable is not even obscuring.
I've been in the enterprise sector for over 20 years, seen everything, started as Linux guy, now project lead, also started with AI. I'm doing mainly contracting within the EU, but I'm open for everything.
Ah yes, we haven't spent as much effort on it as we could. Mostly been building the product itself!
Pricing is still to be determined. I imagine we will charge for infra usage (processing, storage, etc) in line with other providers like Supabase. We will also charge per-seat for developing inside Specific, which will likely be a fixed price with some token usage limit.
As for what's part of the beta, we currently offer hosting for the API and processing of requests, as well as a database to back it. We are planning on expanding that to support more use cases like background jobs, cron jobs, and object storage.
We don't offer built-in authentication and aren't planning to at this point. That's because we think there are much better providers (like Auth0, Clerk, WorkOS) that you can easily integrate in your Specific app by just specifying it!
That's the main difference to something like Supabase. We provide the infra automatically for your app to do what you need it to, but aren't opinionated around user-facing aspects like authentication. We also have the opportunity to be quite a bit more flexible. Building integrations with external APIs on Supabase for example often requires writing edge functions. In Specific, you can simply make it part of your specification.
Why is every second article about this claiming that it’s automatic? It needs to be turned on or at least there was no mention of automatic in the original blog post.
I really hope that we can continue training AI the same way we train humans – basically for free.
I don’t think one is still „old“ if they died. The oldest person is normally the oldest person alive and that’s the opposite of dead.
So, no: there is still an oldest person. It just switched to someone else, happens all the time. It’s a bit more apparent with the youngest person, everyone was the youngest person at birth - at least for a short amount of time and then it switched to the next one.
A test email is a request sent with a development API key. The email is processed just like in a traditional send but isn't actually delivered. Instead, it ends up in a "virtual outbox," which prevents damaging your domain's reputation while still allowing you to intercept the emails. It's a bit like Mailtrap.
The pricing might not be the clearest. My apologies.
My wish list:
1. iOS native sync, preferable without Active Sync. This includes syncing of read states.
2. Custom domains for families and small business without shelling out $10 per user and month.
3. A shared mailbox within the custom domain as „family“ contact mailbox. At least two people should be able to read it, possibly sync read states AND answer from that address, including sent mails need to be stored in this mailbox.
4. A very simple way to setup the accounts on different systems, especially iOS.
AFAIK, except 4 those are already solved, but not within one provider - without paying those mentioned $10/u/m.
> 4. A very simple way to setup the accounts on different systems, especially iOS.
On iOS, at least, you can do this using a `.mobileconfig` profile (which is just an XML plist file). Create that, get your user to access it via HTTP, messages, etc., and iOS will configure the mail account for them. I've used it when family members have lost/forgotten/wiped their details.
Last time I checked it wasn‘t possible to configure multiple aliases via this method and it wasn‘t possible to add aliases after adding an account this way.
This is a few years back, so it might have changed.
I get that subscriptions pile up, but email is the cornerstone of your identity online. Your login and recovery for most services. Getting your mails through requires work these days. I think overall is good value.
A really great article about the state of vibe coding at the end of 2025.
This guy produces real software, ships it, and — as he claims himself — often don’t read the code anymore.
reply