Using a plus sign is subaddressing [1] and most ESPs[2] will route to the main address ( multiple@addre.es) . So you can use use multiple+email@adress.es, multiple+xyz@adress.es and both will route the email to you.
In my experience most SaaS apps do not filter this out and allow re-sign ups with sub-addresses.
Gmail has an additional behavior that dot character is ignored in local component of the address . multiple@gmail.com, mult.iple@gmail.com mult.ip.le@gmail.com all route to the same inbox as well.
This is not true (anymore?). I have a rather unfortunate exact naming collision with a family member. They use the full name without dot for the local gmail component, I use a dot between the first and last name.
Two or three mails have been misplaced in a decade.
It would be feasible to change something like that without breaking security now.
Google can hardly start allowing/routing a new account for first.last@gmail.com when you were getting it for years even though your account is firstlast@gmail.com and sensitive communication like say from your bank would routed there.
The main llm will refuse to scan for issues flagged or not, and the cheap model not do a good enough scan on its own.
For models designed/marketed for cybersecurity defensive uses, any predictable refusal mechanism is a vulnerability. It is like being able to cause a kernel panic or segmentation fault .
Even if the gate is fail-reject, an attacker can overwhelm HITL reviews with many false positives and use DoS vectors here.
> by spending more time on the project and testing it yourself
> a human would generally spend a lot of time here,
This was always the hard part - game engines, asset libraries and all other services / SDKs were always making code-generation cheaper every generation.
Releasing a bug-free, thoughtfully built product requires a lot of attention and product skill.
Yeah, I feel like nobody realizes you can put together premade/open source game base + assets in a weekend. And before LLMs there were guys who specialized in this and got really popular on social media for "making a game in a weekend".
Always interesting reading threads about topics you know deeply and everyone else has no familiarity or understanding about what they are seeing. Stark reminder of how easy it is to be impressed when you don't understand a topic.
Apple will deploy the same security/ privacy / ease of use /packaging strategy they have done for every other product.
Same reason developers continue to use Apple payments even when they have to shell out 30% of the revenue.
I can see Apple, setting App store rules around declaring AI usage, or could start labeling apps not using their models with strong language designed to amplify the increasing user concerns around AI and so on.
The product strategy has to be better the product itself does not have to be objectively better for the developer for them to have to choose it.
Backrooms was a quite successful web series on YT which in turn originated in 4chan boards.
Only the medium being sourced from is changing from successful Broadway shows, popular novels or comic books in the years past. The calculus remains the same - properties with name recognition even from other formats tend to be green-light.
The web series and the film also defaulted to a very SCPified generic horror formula with conspiracy, "containment" and monster jumpscares.
But the original element that set backrooms/liminal spaces apart wasn't what was in them, but what wasn't. Sure it's creepy to be all alone, you may be afraid to get jumped, but you aren't. Some of the backrooms-inspired video games stay true to this concept.
So point is, the "Backrooms" film author may be an outsider, but he sticks to a very well-tried formula - one mainstream authors probably avoid for being too cliche more than anything.
Trust of a project long term always was and continues to be of concern when choosing a critical dependency .
The concern basically boils down to how large and serious is the team and what if they abandon the project in few weeks or months .
These were always the risks, many here have been burned by betting years of their career building against promising but what turned out to be weak projects
OP is alluding to the fact that today commit frequency, lines of code or how active the contributors in the issue trackers are no longer good signals to use as proxy.
When the underlying project to yours is few million lines of code written by machines only it is not going to be feasible fork and maintain or in-house it if the maintainers abandon it
To be clear users of a library or a tool aren’t owed anything when it available gratis and fully open source .
However not everyone has access to unlimited tokens to disregard the quality (in terms of history and usage ) or size of the underlying project completely
I think the primary value of a project like this is the demonstration that this is possible and a proof that it does not incur some unknown tradeoff you'll discover after spending resources doing it.
IMO the maintenance story is more or less solved if you can keep AI agents refactoring and improving it in a loop.
> However not everyone has access to unlimited tokens
Apologies. I did not consider this when writing my comment, being spoilt by unlimited 'free' AI.
Free in quotes because, presumably, training agents on AI usage from developers is worth more than the cost of providing free AI.
> IMO the maintenance story is more or less solved if you can keep AI agents refactoring and improving it in a loop.
That’s a weak argument, though, if the future of AI is totally unreliable when it comes to cost and quality. Right now I definitely wouldn’t want to depend on being able to infinitely access AI tools for such an important part of the toolchain.
Aside from that it’s just not attractive to trust a project made by one person.
> rather than the optimizations involved in rendering the text.
Any views they have on this topic is going to come across as quite opinionated given their choices for text rendering for this post and general aesthetics of website.
Naw, the truth is I'm not really smart or intelligent enough to build a semantic diff system. For that you'll need to wait on a post from one of our smarter devs, this was a post about rendering diffs in a browser.
Using the keyword “Workflow”like “Ultrathink” is problematic?
Ultrathink is uncommon enough that it is unlikely to be used in code or prompt outside its intended purpose.
Workflow is generic keyword and used in so many contexts both inside the codebase and orchestration tooling like say temporal.io or others that name their constructs “workflows”.
In my experience most SaaS apps do not filter this out and allow re-sign ups with sub-addresses.
Gmail has an additional behavior that dot character is ignored in local component of the address . multiple@gmail.com, mult.iple@gmail.com mult.ip.le@gmail.com all route to the same inbox as well.
[1] https://datatracker.ietf.org/doc/html/rfc5233 [2] Less common in work hosted ESPs but almost universally default enabled in public ESPs for consumers.
reply