Some of the controls are a bit disorienting. All observations below are from the demo:

1) When I create a goal, theres no obvious way that the goal is "created". I just press the back button? The send-comment button was where I initially tried to confirm that a goal had been created.

2) When I create a subtask, and then exit the subtask menu to get to the first task, it gives me a blank page.

I really really like the idea, but the demo is a bit too buggy

Thanks, great observations.

1) Right now the back button saves the Ploc. You're completely right that the comment button looks like it might do that. We did not consider that this when we moved the comment button there...

2) This is a bug in the demo, unfortunately. I'm working on it!

I had not tested the demo extensively yet so this obvious bug slipped through unfortunately. It should work in the actual application / app in case you want to try it.

> I had not tested the demo extensively yet

A bit of unsolicited advice: Your demo is a potential user's first impression of the app, which means that you should give it just as much care as you do the full application. If the demo is buggy, people will assume the real app will be just as buggy because there is no reason to assume otherwise, which can ruin any chance of converting them.

The bug when exiting the subtask menu in the demo should be fixed now.

Thanks for reminding me. I planned on doing "cycles" between my favorite substackers (buy, cancel, read the backlog, switch to a new author), but i ended up with 5 concurrent subscriptions. Canceled now.

I was just reading a blog complaining about commenters not reading the article, and the next comment I read on a completely different article did not RTFQ.

> got some kind of shallow, automated message like this?

Jakob describes how after he is reminded of the person in the morning, he researches what has happened to them since he last spoke and finds some genuine content/connection to send to that person.

Actually I did RTFA (not sure what your Q means) as indicated by my direct reference of groups A-D, but stopped once I saw the JQL style query as that really sealed the deal for me.

It should be reassuring to know that most of the things you interact with are actually too bandwidth constrained to care about those things, and the algos you interact with are fairly obvious and explicit (Feeds, curated things, etc)

I used to think this, until I happened across FullStory. With that tool you can replay a website visitor's exact session as if it was recorded live on video -- everything they typed (even if it was cleared and never sent in a request), where/when clicks happened, the contents and response of every request, etc.

As a backend engineer, I had no idea that frontend monitoring was this advanced, but apparently it is. So now we all have to be extra paranoid, because _any_ website could be using this tool to "spy" on everybody.

Of course, it _was_ very helpful to us in tracking down some issues (ever tried to tell a customer how to send you a HAR?). And I assume that operating with an adblocker and blocking nonessential cookies will prevent or hamper the output for us more technical types. Even so...

> everything they typed (even if it was cleared and never sent in a request)

Okay, wow, that sounds rough...so in a way, phishing attacks don't even require you to login anymore, just typing the password or maybe 75% of it is enough to get you.

That's not new, is it? You could always have an onchange/oninput handler on the login fields and send it to your server.

Back when Facebook made their huge update to convert to a one-page-app, it was pretty obvious they were doing this because on tenuous connections the interactions with the text would be very strange, as if they are caching your text and operating on it server-side using commands sent from client-side.

Uhh... yeah, just typing the password (or letting your password manager autofill when you get cache poisoned or whatever) has always been enough to get you. onkeydown has existed longer than phishing.

This isn't reassuring at all. People also said the gov didn't have the bandwith\storage\processing to record every call. Then we found out it was also happening with our emails too

It's not and even if it were it could be pre-processed locally as to reduce the data volume. It's safe to assume that everything you do on Instagram, Tik Tok is taken into account. Those are spyware and will intrude on the filesystem, on the clipboard history and wherever else they can.

Don't get nitty about saying "my X". People say "my plumber" or "my hairstylist" or whatever all the time.

I would be willing to bet money they use the same tool.

A person yelling "fire" in a crowded theater gets in trouble, but a person yelling "there is no fire" in a crowded theater in a theater definitely on fire is... being silenced?

You say this but it still feels gross to do.

Consider that maybe the space shuttles exploding _was_ our thing. Boomers got to see the surface of the Moon. Zoomers got to see cheap flight and robotic victories. Millennials were raised by a NASA flying an explosive trailer truck.

Bicycles for the minds are only useful for minds that have a good idea of where they're biking to!