Feed aggregator

Article URL: https://fastretro.app/blog/how-we-improved-rails-response-times-by-87-percent

Comments URL: https://news.ycombinator.com/item?id=46941530

Points: 1

# Comments: 0

Article URL: https://www.reuters.com/world/europe/paris-prosecutors-cybercrime-unit-searches-french-office-musks-x-2026-02-03/

Comments URL: https://news.ycombinator.com/item?id=46941525

Points: 2

# Comments: 0

Article URL: https://cipscorps.io/#

Comments URL: https://news.ycombinator.com/item?id=46941508

Points: 1

# Comments: 1

Article URL: https://www.reuters.com/science/musk-says-spacex-prioritise-building-self-growing-city-moon-2026-02-08/

Comments URL: https://news.ycombinator.com/item?id=46941505

Points: 2

# Comments: 0

Article URL: https://www.bloomberg.com/news/audio/2026-02-03/odd-lots-the-us-and-chinese-internets-similarities-podcast

Comments URL: https://news.ycombinator.com/item?id=46941494

Points: 1

# Comments: 0

Reality Asset Existence Manifesto (RAEM) – v0.1

Author: Janus Pater

Objective: To establish an engineering-based asset existence framework, replacing credit, discounting, and valuation estimates with physical executable capability, defining whether an asset truly exists, can generate value, and can be traded.

Chapter 1: Hard Criteria for Asset Existence

For any asset to be recognized as “real” by the system, it must satisfy four hard conditions:

1. Executability

The asset must be able to output real-world function or value.

Function types include:

Energy (kW, MJ)

Computing power (TFLOPS, GPU-hours)

Space / Capacity (m², tons)

Services (transportation, repair, manufacturing, etc.)

Determination formula:

if Output(t) = 0 → Asset Invalid

2. Measurable Lifecycle

The asset’s lifespan must be quantifiable:

Design lifespan

Consumed lifespan

Remaining lifespan R(t)

Cannot rely on promises, insurance, or future compensation.

3. Observable State

Asset state S(t) must be real-time or periodically observable.

Data sources:

Sensors

Logs

Manual verification protocols

Update frequency ≥ transaction frequency

4. Deliverability

Usage rights must be transferable

Independent of asset owner credit

No third-party guarantees required

Chapter 2: Core Asset Data Structure

Each asset corresponds to a state vector S(t):

S(t) = { R(t): Remaining lifespan O(t): Current output capability M(t): Maintenance cost per time unit F(t): Failure probability function E(t): External environment dependency factor }

Time is consumed, not discounted

Value is based solely on current state + remaining lifespan + output capability

Chapter 3: Value Calculation (V(t))

(

) =

(

) ×

(

) − ∫

(

)

−

(

(

) ) V(t)=O(t)×R(t)−∫M(t)dt−Risk(F(t))

Explanation:

Maximum potential output = O(t) × R(t)

M(t) = Maintenance and operational cost

Risk(F(t)) = Deduction due to failure probability

Future promises, discounting, or credit are excluded

Chapter 4: Trading Rules Trading Objects

Only remaining life usage rights ΔR are traded

Ownership, promises, or future income are not traded

Usage Contract Structure Contract { Asset_ID Usage_Type ΔR State_Snapshot S(t₀) Settlement_Rule }

Settlement Principles

Instant delivery

State-driven dynamic pricing

Expired or failed assets → contract value = 0

No leverage, no collateral, no reliance on credit

Chapter 5: Minimal Executable Architecture (MVP)

Asset State Acquisition Module

Updates S(t)

Ensures data is real and timely

Lifecycle Engine

Input: S(t)

Output: R(t), V(t)

Usage Rights Market Matching Module

ΔR ↔ Instant demand

Real-time transaction settlement

Clearing Module

Life consumption → automatically deducted

Failed assets → contract cleared

Chapter 6: Engineering Examples Off-Grid Compute Unit

O(t) = available compute power in TFLOPS

R(t) = remaining stable operational hours

M(t) = maintenance + energy cost

Trade: 100 hours compute usage, instant delivery, independent of future revenue

Computable Building

O(t) = usable space / compute / energy output

R(t) = remaining operational lifespan

Trade: usage rights transfer + instant settlement

Chapter 7: Core Principles

Assets must generate value immediately

Value derives only from current state and remaining lifespan

Time is consumed, not discounted

Credit and promises are invalid

Failure → cleared; no bailout from the system

Core concept: Real existence ≡ Executable ≡ Tradable

Chapter 8: Practical Significance

Prevents “virtual asset scams”

Survives during macro credit contraction cycles

Transparent, real-time asset value

Simple, trustless trading model

Engineering implementation of Digital Materialization → Lifecycle-Anchored Asset execution model.

Comments URL: https://news.ycombinator.com/item?id=46941486

Points: 1

# Comments: 0

Article URL: https://www.techdirt.com/2026/02/06/the-cia-erased-the-world-factbook-with-no-warning-and-told-everyone-to-stay-curious/

Comments URL: https://news.ycombinator.com/item?id=46941460

Points: 2

# Comments: 0

Article URL: https://www.youtube.com/watch?v=aCN9iCXNJqQ

Comments URL: https://news.ycombinator.com/item?id=46941454

Points: 1

# Comments: 0

Article URL: https://www.youtube.com/watch?v=TiwADS600Jc

Comments URL: https://news.ycombinator.com/item?id=46941451

Points: 1

# Comments: 0

Article URL: https://www.mklogo.sh/

Comments URL: https://news.ycombinator.com/item?id=46941426

Points: 1

# Comments: 0

Applying to X26 (deadline is tomorrow).

I built this because I got rejected from W25 (AI tutor idea) and wanted to sanity check my future apps based on what empirical indicators I could find.

Here is how it works: Vector Search: Checks your idea against 5,000+ past YC companies (successes and failures). Rubric Analysis: Evaluates the startup mechanics based on criteria extracted from YC Startup School and Paul Graham's essays.

Tested it on a few friends building stuff. Correctly identified a VS Code docs extension as a nice-to-have / low urgency (Fail). Gave a pass to a campus sublet marketplace, but correctly flagged the chicken and egg supply risk.

Comments URL: https://news.ycombinator.com/item?id=46941413

Points: 1

# Comments: 0

Article URL: https://www.nytimes.com/2026/02/07/us/politics/doj-prosecutors-recruiting-trump.html

Comments URL: https://news.ycombinator.com/item?id=46941405

Points: 2

# Comments: 1

Article URL: https://publicdomainreview.org/collection/japanese-snowflake-book/

Comments URL: https://news.ycombinator.com/item?id=46941383

Points: 2

# Comments: 0

Article URL: https://smallcultfollowing.com/babysteps/blog/2026/02/08/fun-with-dada/

Comments URL: https://news.ycombinator.com/item?id=46941366

Points: 1

# Comments: 0

WriteMore helps writers write more. Built by writers, it turns daily prompts into a shared creative practice—write, post, and explore what others are creating every day.

Comments URL: https://news.ycombinator.com/item?id=46941358

Points: 1

# Comments: 0

Article URL: https://github.com/joshLong145/ambits

Comments URL: https://news.ycombinator.com/item?id=46941347

Points: 1

# Comments: 0

Article URL: https://www.cnbc.com/2026/02/07/south-korean-crypto-firm-accidentally-sends-out-44-billion-in-bitcoin.html

Comments URL: https://news.ycombinator.com/item?id=46941345

Points: 2

# Comments: 0

I feel like a lot of discussion on this topic comes down to apathy or just giving up. People say they'd start pirating their entire library if Steam ever went down, but that feels like more of a knee-jerk reaction than an actual plan. For Steam to simply cease existing, something critical would have to fail on a worldwide scale. It's not a realistic near-term scenario to be clear but I just wanted to talk about it and see how other people feel about it.

Even if you wanted to preserve your library, many people's collections have outgrown any commonly available consumer storage. We're talking libraries that would require multiple terabytes, maybe even tens of terabytes, to archive completely. The infrastructure to back that up isn't cheap or simple. So the "I'll just pirate it all" response starts to feel hollow when you think about the actual logistics.

To me this raises an uncomfortable question: what was the point of accumulating all those games in the first place? How many people have libraries packed with Humble Bundle extras, impulse buys from Steam sales, and games they swore they'd play someday but never touched? Just note that I'm guilty of this too.

I've spent a lot building a half decent gaming collection but a huge chunk of it sits there gathering dust.

So when the hypothetical happens and your library becomes inaccessible, how do you rationalize it? Will you actually miss most of those games, or will you realize you only ever cared about a handful?

Will you seek out a new platform to start buying from?

I have a slight shift in perspective now that buying games and never playing them is essentially a 30% donation to keeping Steam existing, and a 70% donation to the developers / publishers to keep doing what they are doing.

When you rationalize it like that it feels a bit less painful but I'm curious what HN's take on this topic is.

Comments URL: https://news.ycombinator.com/item?id=46941331

Points: 3

# Comments: 1

Article URL: https://www.frametoolkit.com/tools/video-to-gif

Comments URL: https://news.ycombinator.com/item?id=46941155

Points: 1

# Comments: 0