How to erase unwanted objects from photos for free, and where AI tools fall short

·3 views

Removing an unwanted object from a photo used to take a long time with manual cloning, but AI erasers now do it in seconds. These tools work by masking the object and generating plausible new pixels from the surrounding area, rather than revealing what was hidden. The guide recommends using the largest original file, masking slightly wider than the object including shadows, and removing one item at a time. Results are strongest on simple backgrounds like sky or water, and weaker on patterns, straight lines, faces, and readable text. The author also cautions against using such edits to hide real defects in evidence or property photos, since that becomes misleading.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Pomerado launches tool that turns any website into a self-healing API for AI agents

Pomerado, a Y Combinator F26 startup founded by Alan and Akshay, has launched a self-serve platform that converts websites into deterministic, self-healing APIs for AI agents. The founders say many airlines, banks, insurers, and government portals lack APIs, forcing agents to rely on slow, costly, and unreliable browser automation that companies often block for security reasons. Their platform has an agent explore a site once to record the task, then generates a repeatable tool exposed via MCP, with a separate guardian model checking guardrails and synthetic tests validating generalization. The system also handles authentication and 2FA through a deterministic sign-in process so credentials are never read by the model, and a maintenance job repairs the tool when sites change. The founders said the idea grew out of their experiences building personal assistants and deploying agents in healthcare, professional services, and telecom.

0 comments Read more at Hacker News

ProgrammingHacker News ·

Apple Research Explores Faster Retrieval to Make RAG More Efficient

Apple's machine learning research team has published work on speeding up retrieval for retrieval-augmented generation (RAG) systems. The focus is on making the retrieval step faster and more efficient, which is a key bottleneck in RAG pipelines. The post appeared on Apple's machine learning research site and was shared on Hacker News, where it gained a few points and no comments at the time of capture. The available source material offers only the headline, link, and engagement figures, so the specific techniques and results are not described here. Readers interested in the methods can refer to the original Apple research page.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Fixing a Slow Database: Work Up the Scaling Ladder Cheapest-First

The article argues that a slow database should be fixed in a deliberate order rather than jumping straight to sharding, which is costly. It recommends first confirming the real cause and adding indexes, then adding a cache such as Memorystore for repeated reads, then using read replicas for read-only traffic. Scaling the instance to a larger machine type comes next, with attention to brief restarts, replica sizing and retry logic. Sharding is reserved for cases where the single primary remains the write bottleneck, and measurement is advised at every step.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Avatar Metadata Search: Keep Object Storage for Bytes, Catalog for Queries

The article argues that object storage should hold avatar bytes under immutable, addressable keys, while content type, tags, ownership, and moderation state belong in a queryable catalog. Bucket prefix listing suits repair and audit tasks but cannot efficiently evaluate predicates such as type plus tags within a tenant. The author notes that declared Content-Type headers are only hints and should be verified by inspecting the payload with a bounded decoder. A catalog row with explicit ready, pending, and failed states can bridge the lack of atomic commits between database and bucket. The piece also names failure modes such as orphan objects, dangling rows, duplicate retries, and stale current pointers.

0 comments Read more at DEV Community