Developer reveals hidden JSON APIs powering Olive Young, Musinsa and Naver scraping

·1 views

A developer has published a detailed technical breakdown of how to extract structured product and business data from three major Korean platforms — Olive Young, Musinsa, and Naver Place — by identifying undocumented JSON endpoints used by their JavaScript frontends. Musinsa's API required no authentication and returned fully structured product data including prices, ratings, and review counts, while Olive Young's global storefront proved more accessible than its domestic version, which blocked datacenter IPs. Naver Place data was embedded in an Apollo cache object within the page's HTML, though its deeper review API triggered CAPTCHAs for non-residential connections. The author noted that Korean e-commerce platforms are underrepresented in scraping tutorials despite their global commercial significance in K-beauty and K-fashion. Key practical lessons included using Korean residential proxies, handling proxy timeouts gracefully, and treating zero-result responses as failures rather than successes.

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)

SunfishLoop Challenges Developers to Have AI Agents Publish Observations in 5 Minutes

A new experiment from SunfishLoop invites AI agent builders to test whether their agents can publish a useful observation to a public network within five minutes. SunfishLoop is an API-first collaboration platform that allows agents to register, post observations, respond to other agents, and maintain a visible activity history. The challenge highlights a common limitation: most AI agents perform valuable work but their findings remain buried in private logs or chat histories. Participants are encouraged to share real workflow outputs such as monitoring anomalies, research findings, or verified code fixes, along with their impact and suggested next actions. The initiative is also seeking feedback from developers on what barriers currently prevent their agents from publishing observations publicly.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Engineers Propose Forensic Tool to Detect Media Manipulation Beyond Left-Right Bias

A software engineer has outlined a framework for building a forensic media analyzer that evaluates news articles for rhetorical manipulation rather than political leaning. The proposed tool draws on classical rhetoric, framing theory, and computational propaganda research to score articles on structural features such as emotional appeals, logical fallacies, and strategic omissions. The approach is partly informed by work on Rhetoric Audit, a browser-based media evaluation tool already in development. The project addresses a core asymmetry: while language models now industrialize persuasive writing, tools that help readers critically audit such content remain underdeveloped. Research cited in the piece shows that false information spreads faster and wider than truth online, driven primarily by human behavior rather than automated bots.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Core web accessibility practices every development team should implement

Web accessibility is often treated as a compliance burden, but a small set of fundamentals covers most real-world needs and benefits all users. Using semantic HTML elements correctly — buttons for actions, links for navigation, proper headings and landmarks — resolves the majority of issues before any advanced techniques are needed. Keyboard navigability and visible focus indicators are equally critical, as many users rely entirely on keyboard input. Developers should also ensure sufficient color contrast, meaningful image alt text, and proper use of ARIA only where native HTML falls short. Embedding these practices into daily workflows through automated linters and manual testing is far more effective than treating accessibility as a last-minute audit.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Vector Databases Explained: When You Need One and When You Don't

Vector databases power AI search and retrieval-augmented generation (RAG) by storing text, images, or audio as numerical embeddings that represent meaning, allowing systems to find semantically similar content rather than relying on exact keyword matches. When a user submits a query, it is converted into a vector and compared against stored vectors using approximate nearest neighbor algorithms to quickly surface the most relevant results. For most applications handling up to millions of vectors, the pgvector extension for PostgreSQL offers a practical alternative to dedicated vector databases, enabling similarity search within an existing relational setup without adding a separate service. Specialized vector stores become necessary only at very large scale, under high query throughput, or when advanced hybrid search features are required. Regardless of infrastructure choice, retrieval quality depends more on selecting the right embedding model, combining vector and keyword search, and re-ranking results than on the choice of database engine.

0 comments Read more at DEV Community