48

cross-posted from: https://lemmy.world/post/16391311

Andrej Karpathy endorses Apple Intelligence

Actually, really liked the Apple Intelligence announcement. It must be a very exciting time at Apple as they layer AI on top of the entire OS. A few of the major themes.

Step 1 Multimodal I/O. Enable text/audio/image/video capability, both read and write. These are the native human APIs, so to speak.

Step 2 Agentic. Allow all parts of the OS and apps to inter-operate via "function calling"; kernel process LLM that can schedule and coordinate work across them given user queries.

Step 3 Frictionless. Fully integrate these features in a highly frictionless, fast, "always on", and contextual way. No going around copy pasting information, prompt engineering, or etc. Adapt the UI accordingly.

Step 4 Initiative. Don't perform a task given a prompt, anticipate the prompt, suggest, initiate.

Step 5 Delegation hierarchy. Move as much intelligence as you can on device (Apple Silicon very helpful and well-suited), but allow optional dispatch of work to cloud.

Step 6 Modularity. Allow the OS to access and support an entire and growing ecosystem of LLMs (e.g. ChatGPT announcement).

Step 7 Privacy. <3

We're quickly heading into a world where you can open up your phone and just say stuff. It talks back and it knows you. And it just works. Super exciting and as a user, quite looking forward to it.

https://x.com/karpathy/status/1800242310116262150?s=46

2
submitted 3 weeks ago* (last edited 3 weeks ago) by Z4rK@lemmy.world to c/technology@lemmy.world

Actually, really liked the Apple Intelligence announcement. It must be a very exciting time at Apple as they layer AI on top of the entire OS. A few of the major themes.

Step 1 Multimodal I/O. Enable text/audio/image/video capability, both read and write. These are the native human APIs, so to speak.

Step 2 Agentic. Allow all parts of the OS and apps to inter-operate via "function calling"; kernel process LLM that can schedule and coordinate work across them given user queries.

Step 3 Frictionless. Fully integrate these features in a highly frictionless, fast, "always on", and contextual way. No going around copy pasting information, prompt engineering, or etc. Adapt the UI accordingly.

Step 4 Initiative. Don't perform a task given a prompt, anticipate the prompt, suggest, initiate.

Step 5 Delegation hierarchy. Move as much intelligence as you can on device (Apple Silicon very helpful and well-suited), but allow optional dispatch of work to cloud.

Step 6 Modularity. Allow the OS to access and support an entire and growing ecosystem of LLMs (e.g. ChatGPT announcement).

Step 7 Privacy. <3

We're quickly heading into a world where you can open up your phone and just say stuff. It talks back and it knows you. And it just works. Super exciting and as a user, quite looking forward to it.

https://x.com/karpathy/status/1800242310116262150?s=46

156
submitted 4 months ago by Z4rK@lemmy.world to c/selfhosted@lemmy.world

Hi everyone! We're incredibly excited to announce that we're launching a beta of Finamp's redesign today. This is a major update to the app, and we're looking for feedback from anyone willing to try it out before we roll it out to everyone.

The beta is a work-in-progress, there are several new features already, but we will be adding more features over time.

Looks very nice!

[-] Z4rK@lemmy.world 43 points 7 months ago

I wouldn’t use Beehaw as the standard, they are way too strict on their moderation in many’s opinion.

[-] Z4rK@lemmy.world 51 points 8 months ago

I’ve used them for extension, as it allows you to attach a second, regular USB cable to it.

[-] Z4rK@lemmy.world 136 points 9 months ago

I may sound cynical, but protecting jobs is hardly ever a good argument for blocking new technology in my opinion. You’re at best delaying the inevitable. Society is more likely better off learning early how to use the workforce for new and better tasks. Of course, this needs a healthy and working society, so I of course understand the individual concerns.

Safety on the other hand is a very valid reason to hold back new technology.

[-] Z4rK@lemmy.world 47 points 9 months ago

Man I can’t wait to get 100% out of gmail.

85
submitted 10 months ago* (last edited 10 months ago) by Z4rK@lemmy.world to c/apple_enthusiast@lemmy.world

Just in case you wondered how many photos you really can have in your Apple Photos library, I can report that I have so far added 1 000 264 Photos and 10 242 Videos without any issues.

I’m fairly impressed and happy about it since all I could find was that it should support up to 100.000 photos, with a few reasoning about the limit being increased to 300.000 on modern hardware.

1 000 264 Photos, 10 242 Videos in Apple Photos

I’m running this on my MacBook Pro M2 Max with 64 GB ram.

Most formats gets converted to HEIC and HEVC on import, which are staggeringly effective compared to their original formats. The whole library file still only takes up 1.7TB, which is much less than expected. The original source on my NAS is around 5.6 TB.

Edit: Maybe I should add that I do not recommend this, and view it as an experiment for now. I’m still importing data. If it’s still stable and performant after a year and some OS updates then I can start recommending it.

[-] Z4rK@lemmy.world 38 points 10 months ago

I literally have nothing to hide, but conveniently have just reset my phone whenever I’m flying into the US.

53
submitted 10 months ago* (last edited 10 months ago) by Z4rK@lemmy.world to c/voyagerapp@lemmy.world

Setting the app icon for Voyager seems to only apply to the icon shown for the app on the selected screen, but it does not for example apply to the icon shown for the running apps carousel.

13
submitted 10 months ago by Z4rK@lemmy.world to c/voyagerapp@lemmy.world

Sometimes I accidentally hide posts by swipe gesture.

These posts are forever gone :/

Can functionality be added so that we can see and unhide hidden posts?

[-] Z4rK@lemmy.world 38 points 10 months ago

This bug has created havocs for me. We had a “last synchronized” time stamp persisted to a DB so that the system was able to robustly deal with server restarts / bootstrapping on new environments.

The synchronization was used to continuously fetch critical incident and visualize them on a map. The data came through a third party api that broke down if we asked for too much data at a time, so we had to reason about when we fetched data last time, and only ask for new updates since then.

Each time the synchronization ran, it would persist an updated time stamp to the DB.

Of course this routine ran just as the server jumped several months into the feature for a few minutes. After this, the last run time stamp was now some time next year. Subsequent runs of the synchronization routine never found any updates as the date range it asked for didn’t really make sense.

It just ran successfully without finding any new issues. We were quite happy about it. It took months before we figured out we actually had a mayor discrepancy in our visualization map.

We had plenty of unit tests, integration tests, and system tests. We just didn’t think of having one that checked whether the server had time traveled to the future or not.

[-] Z4rK@lemmy.world 46 points 10 months ago* (last edited 10 months ago)

I’ve always found this classic the best measurement: WTF’s per minute

[-] Z4rK@lemmy.world 37 points 10 months ago

When was cryptocurrency meant to be untraceable? It literally had the complete ledger out in the public.

[-] Z4rK@lemmy.world 55 points 10 months ago

Thank you OP for providing the whole text and not just a link to a Coockie-popup-paywalled site.

[-] Z4rK@lemmy.world 77 points 10 months ago

Billet has confirmed that they sent a 3090Ti that LMG has been sitting on for 9 weeks now without using or returning.

[-] Z4rK@lemmy.world 34 points 10 months ago

Did you watch the video above? Steve spend some time explaining exactly his thoughts behind not reaching out for comments. I think he argues well.

[-] Z4rK@lemmy.world 65 points 11 months ago

Okay but could you not cross post to 10 communities or something? I hoped to leave that behind at Reddit.

3
submitted 11 months ago by Z4rK@lemmy.world to c/voyagerapp@lemmy.world

I use system auto theme on my iPhone, which means it switches between light and dark based on time of day (sun).

On dark theme, Voyager is fine, but on light theme, Voyager has a color in the top bar that does not work.

3
submitted 11 months ago by Z4rK@lemmy.world to c/voyagerapp@lemmy.world

Voyager has now reached a self-sustained rate of content generation from all the commits and pull requests to its source code repo, and no longer needs Lemmy as a source.

Singularity next!

view more: next ›

Z4rK

joined 1 year ago