Skip to content

Commit

Permalink
add March 1 blog post
Browse files Browse the repository at this point in the history
  • Loading branch information
misslivirose committed Mar 1, 2024
1 parent 8053c56 commit 7d0a466
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions docs/_posts/2024-03-01-memory-cache-and-ai-privacy.markdown
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
layout: post
title: "MemoryCache and AI Privacy"
date: 2024-03-01 07:08:57 -0500
categories: developer-blog
---
_Author: Liv Erickson_

It's been an exciting few months since we first shared [MemoryCache](https://memorycache.ai/developer-blog/2023/11/06/introducing-memory-cache.html), a home for experimenting with local-first AI that learns what you learn. While we'll be sharing more updates about what the team has been working on in the coming weeks by way of more regular development blogs, I wanted to share a podcast that I recently recorded with [Schalk Neethling for the Mechanical Ink Podcast](https://schalkneethling.substack.com/p/privacy-ai-and-an-ai-digital-memory) that goes in-depth about the principles behind MemoryCache.

[![Watch the video](https://img.youtube.com/vi/CGdxLfcU9TU/0.jpg)](https://www.youtube.com/watch?v=CGdxLfcU9TU)

In this podcast, we go into the motivations behind the project and how it was originally created, as well as the overall challenges that are presented with the growing creation of synthetic content and preserving authentic connections online in an area of unprecedented, generated personalization.

At it's core, MemoryCache is a project exploring what it means to urgently, yet collaboratively, envision futures where AI technologies enable us to build a more authentic relationship with information and ourselves through small acts of insight and [embracing friction](https://foundation.mozilla.org/en/blog/speculative-friction-in-generative-ai/) as it presents novel outcomes.

More coming soon!

0 comments on commit 7d0a466

Please sign in to comment.