janesconference

Fun fact, I guess: I acquired a cutting of that same Sigmund Freud begonia that was successfully propagated into three big plants that live in my house. My fiancee worked at the Freud Museum / house for a while in London, and the plant was gifted to her when she left the job.

Just came here to say "Mickey Mauser"

I saw it too in the 90s, unfortunately I can't remember the game's name.

Thanks! Re: 1, the docs are not really deep on that, but from your answer it seems it possible to self-host y-sweet on Cloudflare workers (I guess) with Durable Objects as storage? Also, if you guys are going to have a paid plan, how do you see the prices going? Comparable to, say, Supabase per user, less or more?

How does it scale? What happens if you have many users or a bunch of users with huge history on their data? If you haven't hit these limitations, what do you plan to do when (if) you hit them?

A couple of questions about y-sweet, based on the experiences I had with CRDTs:

1) Does the server keeps in memory the "active" documents? In other words, does the server need to open a document and keep it in RAM while clients are connected to it (I assume there's a websocket connection somewhere in the client that keeps it hot)? Or is the server stateless - just connects to the store when needed? I found the latter very hard to do.

2) Does the client persist entries using indexeddb? If yes, does opening many tabs cause redundant writes as they all sync with the server? If not, does the client need to fully re-sync with the server anytime it wakes up?

3) Is it possible to observe updates on the client as they come? One of the major use cases of CRDTs is to index data on the client - then you can have a dumb server that just syncs data between clients and a smart client that does search, graphs, visualizations etc. on the data it receives. To do that, the client needs to observe updates one by one and process them to create secondary indexes. Is it possible to do with y-sweet without forking its source code? I remember getting updates yn Y.js being quite inefficient as you need to replay them all or something similar, but that was a couple of years ago.

That's really cool. What is pic.sh's funding plan?

I remember it was hard-core techno with heavy basses and short spoken vocals intermixed. Very good quality, more on the "real music production" than on the "videogame track" side of things. Year might have been roughly 1993 to 1996

Long shot, but I remember a friend playing a beautiful digital tune made with a tracker from an Amiga demo. I remember the chorus had a sampled voice saying something like "Amphora" (which was probably the name of the demo authors' group). I've searched the internet far and wide but I never found it again. Does anyone remember it?