HackerTrans
TopNewTrendsCommentsPastAskShowJobs

oldfuture

no profile record

Submissions

[untitled]

1 points·by oldfuture·16 giorni fa·0 comments

Pixel-Aligned 3D Generation from Images

ldyang694.github.io
1 points·by oldfuture·2 mesi fa·0 comments

Cortical Cloud – Code to Real Neurons

corticallabs.com
2 points·by oldfuture·2 mesi fa·1 comments

OpenDyslexic: A Typeface for Dyslexia

opendyslexic.org
2 points·by oldfuture·2 mesi fa·1 comments

0xBitNet

github.com
4 points·by oldfuture·2 mesi fa·0 comments

Potato OS

github.com
2 points·by oldfuture·2 mesi fa·1 comments

Thrml - Probabilistic Compute Simulation on GPUs

docs.thrml.ai
2 points·by oldfuture·2 mesi fa·0 comments

Temporal Language Models

calcifercomputing.com
3 points·by oldfuture·3 mesi fa·0 comments

Honey, I Shrunk the Coding Agent

itayinbarr.substack.com
8 points·by oldfuture·3 mesi fa·0 comments

[untitled]

1 points·by oldfuture·3 mesi fa·0 comments

OMLX – Apple Silicon Optimized Local Inference

omlx.ai
1 points·by oldfuture·3 mesi fa·0 comments

DFlash: Block Diffusion for Flash Speculative Decoding

z-lab.ai
3 points·by oldfuture·3 mesi fa·0 comments

Free Space Optical Link Utilizing a Modulated Retro-Reflector [pdf]

ntrs.nasa.gov
1 points·by oldfuture·3 mesi fa·0 comments

Mesh LLM

github.com
4 points·by oldfuture·3 mesi fa·0 comments

Run Gemma 4 in Your Browser

huggingface.co
4 points·by oldfuture·3 mesi fa·0 comments

Producer by Google

producer.ai
2 points·by oldfuture·3 mesi fa·0 comments

Grove: Distributed LLM Training over AirDrop

github.com
3 points·by oldfuture·4 mesi fa·0 comments

Epstein Fallout Tracker

epstein.observer
4 points·by oldfuture·4 mesi fa·0 comments

Distributed Llama

github.com
3 points·by oldfuture·5 mesi fa·0 comments

Resist.bot – Text your elected officials all at once

resist.bot
1 points·by oldfuture·5 mesi fa·0 comments

comments

oldfuture
·13 giorni fa·discuss
a lot of credits? we can’t predict any price change for them
oldfuture
·mese scorso·discuss
And the prospectus says it plainly: "Mr. Musk will be able to control the outcome of matters requiring shareholder approval."

Musk holds over 85% voting power through Class B super-voting shares (10 votes/share). Public investors combined will have 15%.

What Musk Controls:

- CEO removal = his consent. You can't fire him even if he destroys the company

- Take business for himself. SpaceX gets a rocket deal? Musk can say "I'll do it at Tesla instead"

- 85% voting forever. No expiration, no time limit, permanent control

- Board elections. You have no power to elect directors you trust
oldfuture
·2 mesi fa·discuss
70 points in 45 minutes and not on the frontpage anymore? anyone minds to explain why?
oldfuture
·2 mesi fa·discuss
well, I mean their goals are kind of clear https://newrepublic.com/post/207693/palantir-ceo-karp-disrup...
oldfuture
·2 mesi fa·discuss
exactly
oldfuture
·2 mesi fa·discuss
torture? https://www.youtube.com/watch?v=9ksLuRoEq6A
oldfuture
·2 mesi fa·discuss
the intentions may be good but it looks like a boost to surveillance tech in the wrong hands, time to react
oldfuture
·2 mesi fa·discuss
as if they didn’t have enough data already, good choice to lose any remaining trust from the public over this
oldfuture
·2 mesi fa·discuss
usable ai on a simple raspberrypi, quite an achievement for sovereign ai
oldfuture
·4 mesi fa·discuss
The word "fake" draws attention but I think the article obscures two real problems:

Training is missing from the analysis entirely (as someone else noted)

Inference water use is indeed minimal per prompt no argument there, but training the old GPT-3 consumed roughly 5.4 million liters of water. LLaMA 3: ~22 million. These are huge events, happening multiple times a year across the industry, folding them into national averages seems like the statistical simplification he article criticizes everyone else for doing…

"Small nationally" ≠ "fine locally"

The Dalles, Oregon is the clearest example. In 2012, Google used 12% of the city's water supply. Today it consumes a third, around 1.19 million gallons per day, and well a sixth data center comes online in 2026, in the same area.

The city is now pursuing a $260 million reservoir expansion into a national forest (!), where 95% of the projected new water demand will be industrial, not residential. Residents are looking at a potential 99% rate increase by 2036 to fund infrastructure that may exists primarily to serve one company. Apparently the city fought a 13-month legal battle just to keep those numbers secret, that’s like a community being reshaped around a single tenant.

Hays County, Texas residents sharing the Edwards Aquifer with incoming data centers voted to block one. Memphis is watching xAI draw 5 million gallons per day. Bloomberg found two-thirds of new U.S. data centers since 2022 are sited in high water-stress zones. Arizona have already passed ordinances capping data center water use.

This to me looks like a problem in the making, AI water use isn't a national crisis for now, but local impacts are already real, training costs are systematically underreported, and the five year trajectory in water stressed regions deserves serious attention indeed
oldfuture
·4 mesi fa·discuss
this should be known by everyone
oldfuture
·7 mesi fa·discuss
We should fully own what we buy, things like this are essential
oldfuture
·7 mesi fa·discuss
this can be solved by adding an external nas - for redundancy - and an opensource application or extension that manages the syncing?

making self hosting more seamless is key, we simply can't trust to be dependent on third parties for access to our own data in the long term
oldfuture
·7 mesi fa·discuss
if you don't have your data when you don't have access to third parties you don't own your data.

we should start switching to solutions like this to keep control and freedom

you can find their opensource repos here: https://github.com/getumbrel
oldfuture
·7 mesi fa·discuss
Behind Italy’s Parmigiano Reggiano is a radical tradition of cooperatives. In some areas, they make up nearly a fifth of the GDP without leaving democracy outside the factory's doors
oldfuture
·9 mesi fa·discuss
https://archive.md/MOxxV
oldfuture
·9 mesi fa·discuss
Google's removal of num=100 parameter last month makes it harder for third party tools (e.g. chatgpt, perplexity) to access beyond the first 10 results

This is incredibly hurting the visibility of any new emergent site as we can already see in the data
oldfuture
·10 mesi fa·discuss
One thing worth stressing is that the witness + executor layer is the critical trust boundary here.

In classic Ethereum, bugs are noisy: if one client diverges, other clients complain, and consensus fails until fixed.

In zk Ethereum, bugs can be silent: the proof validates the wrong execution and everyone downstream accepts it as truth.

I mean that the witness is like a transcript of everything the EVM touched while running a block: contract code, storage slots, gas usage, etc. so you can replay the block later using only this transcript, without needing the full Ethereum state.

For security, that witness ideally needs to be cryptographically bound to the block (e.g., via Merkle commitments), so no one can tamper with it.

The executor is the piece that replays that transcript deterministically. If it does so correctly, then you can generate a zk proof saying “this block really executed as Ethereum says it should.” But correctness here isn’t binary, it means bit-for-bit agreement with the Yellow Paper and all EIPs, including tricky cases like precompile gas rules. So the danger is in the details. If the witness omits even one corner case, or the executor diverges subtly, the zk system can still generate a perfectly valid proof, but of the wrong thing. zk proofs don’t check what you proved, only that you proved it consistently. In today’s consensus model, client bugs show up quickly when nodes disagree.

So while the compilation and toolchain work here is impressive, the real challenge is making sure the witness and executor are absolutely faithful to Ethereum semantics, with strong integrity guarantees. Otherwise you risk building cryptographic certainty, but about the wrong computation. This makes the witness/executor correctness layer the single point of failure in my view where human fallibility can undermine mathematical guarantees, looking forward to understand how this problem will be tackled
oldfuture
·10 mesi fa·discuss
You have more control, in theory, on a cellphone, and so do people around you. With the glasses you really have no way to say if they are listening or watching what you see. The phone has most of the time the sensors partially blocked by a bag or a pocket so it really can't be compared with eyewear.
oldfuture
·10 mesi fa·discuss
the fact that surveillance capitalism, or we should rather say surveillance oligarchy, is here does not mean we have to support it going forward, it can only be worse if nobody reacts