mijkal
Joined 8 years ago
Joined 8 years ago
When in Rome ...
I wrote an app and had it running in both iOS and Android in no time (with minimal iOS dev and zero Android xp prior to that).
My app included the Jitsi video extension (with very customized Jitsi controls and self-hosted backend), so not just a simple CRUD app.
(To be fair, my background is mostly Node and React, but those skills made it a breeze.)
Amazon's 'explicit instructions' on keeping messages visible: either a move for clarity or a masterclass in corporate subtlety.
https://www.dobs.pa.gov/Documents/DoBS%20Forms/Bank%20Forms/...
* Chinese et al have entered the chat
This pattern is fairly common around the world.
It's amusing to me that in the Western world, the original Latin designations are off by two as we moved the start month but never adjusted the corresponding month numbers (so DECember (10) = 12, etc).
Mycellm can verify that inference happened: signed receipts, reputation tracking (success rate, speed, contribution history), admission control that cuts off freeloaders. Each network sets its own policies on top; a private group might trust everything, a public network might add spot-checks or consensus routing.
Directions I'm exploring for public verification: fast-of-N routing, spot-checking with known outputs, consensus at temperature=0 where inference is deterministic. But the verification logic should be pluggable — different networks, different standards. That's a design area where I'd welcome input.
Curious about Runfra — when you say 'Uber for GPU', is that an orchestration/marketplace layer where independent GPU owners sell compute time? And what does 'batch-first creative workflows' look like — image gen pipelines, video, or broader?