HNHacker News
TopNewBestAskShowJobs

onurkanbkrc

243 karma · joined August 4, 2023

submissionscomments
onurkanbkrc··on ai;dr
LLMs are trained on vast portions of the internet.

In that sense, they are essentially systems that mimic online content.

Therefore, what an AI generates often reflects the perspectives of the people who originally created the training data, rather than the true thoughts of the person prompting it.

onurkanbkrc··on Agent Skills
If u wanna browse, search and download AI agent skills, use openskills.space
onurkanbkrc··on Show HN: Cursor for Userscripts
Installation should be easier. Why do I need to build the extension or download a release instead of installing it directly from the Chrome Web Store?
onurkanbkrc··on Show HN: SKILL.md Hub
Yes, there is a selectionbox for that below of the searchbar
onurkanbkrc··on Show HN: Agent Skills Leaderboard
We had already done it before Vercel did.

openskills.space

onurkanbkrc··on There is No Now – Problems with simultaneity in distributed systems
Thanks for the thoughtful comment!

I think there’s a small misunderstanding, though: while systems like GPS do account for relativistic effects at the clock level (and even with extremely precise atomic clocks and practical synchronization via NTP), this doesn’t mean we have a universal or perfectly shared notion of “the same time” across distributed nodes — especially once you consider network delays, clock drift, and faulty or unreachable nodes

In physics there is no absolute global time for spatially separated events, and in distributed systems this shows up as unavoidable uncertainty in synchronization.

Also, the FLP result isn’t about relativity or physical clocks at all — it’s a theoretical result about the impossibility of guaranteed consensus in fully asynchronous systems with failures.

So even with very accurate clocks and practical time bounds, distributed algorithms still have to explicitly deal with uncertainty and partial synchrony rather than assuming perfect global time.

onurkanbkrc··on Saga Pattern and Outbox/Inbox Implementation – Distributed Order Processing
A complete reference implementation showing how to build resilient microservices with guaranteed message delivery. Features MassTransit state machines, transactional outbox pattern, and automatic failure compensation across 4 services (Order, Payment, Inventory, Notification). Includes detailed docs on handling distributed transactions without 2PC.