> this is not how the model should behave

It's exactly how it should behave, without any prior overriding of system prompts.

How much of this page did you write yourself?

Honestly, hard to say.

I gave it a ~2 min voice-to-text about my concept for the memo and, after retrieving relevant context via MCP—(1) my core context (claude.md, user.md, memory.md, etc. equvalents), (2) all contexts in my library from nearly a decade of writing about knowledge management, (3) knowledge of the Github repo for the project, and (4) Karpathy's post—it generated about 99% of the post (I changed a link and some formatting). That wouldn't have been possible without years of context, but this post was very much generated from such.

The beauty of the system is that knowledge, clarity, etc. compound.

If you didn't write it, why should I or anyone read it?

This is AI slop. Opposed to your claim there is nothing clear about that page. It's really sad how ShowHN is spammed with slop that drowns out people's work. Please stop being part of that problem.

While I can understand your distaste of AI slop and appreciate your feedback, if by your own admission you haven't read it, then it's hard to see your designation of my content as slop as justified. I welcome your feedback. If you choose to read it or review it with whatever AI agent you have created to help you synthesize, but I won't push you to do so if that's not something you feel called to do.

I started reading it and found it to reek of AI slop. I couldn't figure out what I'm even reading about and found the text to be unstructured or mis-structured. It also seems to contain a lot of formatting mistakes making me believe that you didn't even care to proofread it.

Sorry to be so blunt, but I have no tolerance for AI a slop. ShowHN is for showing something you built with a lot of care, that people can try out. That can be an AI product. But it cannot be an AI slopped text post pitching your product.

I just found out that in Marshallese hello, bye and love are all the same word: iọkwe

It literally translates to iọ from iia – rainbow and kwe – you: you are a rainbow.

iọkwe

You can use labels for contact scope.

You might want to read my comment again. :) If you use labels, the app will have full access to the associated contacts, not just to their names & phone numbers.

So it's not about labels, but you want the ability to restrict the fields an app has access to rather than an all or nothing – full access to a contact or none at all?

Precisely!

I'm annoyed at everyone who shares my name, phone number and any other details with Meta. I never consented to it. The behavior of their app slurping up your contacts database is despicable.

This doesn't answer your question, but in case it helps for others out there: it's possible to use WhatsApp with no access whatsoever to your contacts and I used it that way for years. Connecting with people is slightly jankier but it still works.

> it's possible to use WhatsApp with no access whatsoever to your contacts and I used it that way for years.

Yeah, that's what I do right now.

> Connecting with people is slightly jankier but it still works.

Without GrapheneOS's contact scopes, how exactly do you do that? Doesn't the other person have to message you first?

I think the key is whether they expect their underlings to be more formal or if it actually goes both ways.

Just an anti recommendation: Do not use Lastpass. Reading the security breach section of their Wikipedia article should be enough reason.

For anyone reading this who uses LastPass: Switch away!

According to the wiki, a one-click exfiltration vulnerability has existed for more than half a year and hasn't been fixed:

> In their default configurations, these extensions were shown to be exposed to a DOM-based extension clickjacking technique, allowing attackers to exfiltrate user data with just a single click. LastPass version 4.146.8 (September 12, 2025), which was intended to address the issue, remains vulnerable

https://en.wikipedia.org/wiki/LastPass#Security_incidents

Update, with Apple's 'Passwords' app, it appears all someone needs to do to get access to every single stored password, is grab your iPhone while it's unlocked, or sneak it from you while sleeping and use face id to unlock it.

Or, they could shoulder surf to get a 6 digit pin to unlock the phone, then steal it, then they're in.

Seems way less secure than 'Correct Horse Battery Staple'.

Faced is required to unlock the passwords app if you enable stolen device protection

You can do the same yourself here: https://www.europol.europa.eu/stopchildabuse

I feel like I'm gonna puke, just knowing these are all cut out from images where a child is being sexually abused makes them feel so cursed.

There is only one location shown in the images, in the past there were several and much clearer, I cannot image how difficult it must be to find it if the europol cannot find it in 2026.

Old thread for context: http://hackertimes.com/item?id=19469681

Large groups ≠ Multi Party

Encryption should be the default for anything private. But something that is configured to be public from the beginning like an open Discord server does not need E2E encryption.

Sorry for your loss.

"This is it... this is where I belong..." I know everyone here... even if I've never met them, never talked to them, may never hear from them again... I know you all...

after all, we're all alike.

Thank you. And you know, it's those quotes and concepts that really stuck me with, about how we were all in it together. And not to get off topic, but i'm so sad and disheartened to see what tech has become since those days.

i feel you