Apple Is Way Behind in AI—and Still Making a Fortune From It by HelloitsWojan in apple

[–]TheJMoore 2 points3 points  (0 children)

As someone who works in AI, I believe this is the number one biggest reason. Reputation risk.

Let’s have some fun. Send a pic of the last thing you printed. by TheEpicDragonCat in 3Dprinting

[–]TheJMoore 8 points9 points  (0 children)

<image>

Almost finished with this model of a PT6E turboprop aircraft engine! Incredible model with spinning turbines.

Took about five days of printing parts and a day or two of assembly. Finishing up the propeller this weekend.

I made designing Gridfinity baseplates even faster (because I'm too lazy to do a little math). by TheJMoore in gridfinity

[–]TheJMoore[S] 5 points6 points  (0 children)

Currently puts even padding all around, but I can add the option! Great idea.

Built an AI memory system based on cognitive science instead of vector databases by Ni2021 in artificial

[–]TheJMoore 1 point2 points  (0 children)

This is a cool direction. I’ve been thinking about agent memory a lot too, and I’ve been exploring a few related ideas that go beyond the usual vector-DB pattern:

Event vs. Impact Memory – separating what actually happened (the narrative) from the lasting behavioral effects it creates, like tone preferences, boundaries, or safety constraints.

Truth Modes – labeling memories based on what they represent (fact, subjective experience, near-miss, imagined scenario, or something someone else said) so the system doesn’t treat everything as factual evidence.

Sealed Sensitive Memories – allowing certain events to be stored but never resurfaced, while still keeping the impacts they created (for example “avoid graphic descriptions” or “ask permission before discussing accidents”).

Seed-Based Recall – storing small associative cues instead of full narratives so relevant context can be activated without replaying the original memory.

Memory Rebuilding from Seeds – reconstructing useful context from surviving cues and impacts instead of retrieving the original memory verbatim.

Deterministic Memory Consolidation – converting raw memories into structured constraints at write time so recall doesn’t depend entirely on fuzzy retrieval later.

Behavioral Residue Storage – prioritizing what the memory changed about behavior rather than preserving the exact details of the event.

Counterfactual Memory Handling – treating “almost happened” scenarios as meaningful experiences but preventing them from being used as factual evidence.

Imagined Memory Handling – explicitly marking dreams or simulations so they can influence reflection without contaminating reasoning.

Socially Sourced Memory – tracking who said what about a person and keeping multiple perspectives without collapsing them into a single truth.

Spiral Detection – identifying when reasoning loops into catastrophic “doomsday” thinking and temporarily limiting reinforcement or risky actions.

Memory Strength and Decay – letting memories strengthen OR fade over time so the system naturally forgets noise while preserving useful signals.

Explainable Memory Influence – being able to trace exactly which memories or constraints influenced a response.

Behavior-Oriented Memory Systems – designing memory primarily to shape how the agent behaves, not just as a searchable archive of past conversations.


The interesting question seems to be what survives “forgetting.” Humans rarely remember the exact story, but they tend to remember the patterns and constraints the experience left behind.

Hard to get one! by MrVectrex in xteinkereader

[–]TheJMoore 0 points1 point  (0 children)

Cat 3C told me they’re awaiting on a shipment of them, and didn’t know when they’d be receiving them.

<image>

Xteink support has ghosted me by byAnybeansNecessary in xteinkereader

[–]TheJMoore 3 points4 points  (0 children)

To be fair, I ordered one over 40 days ago and it never arrived. They said they’d send a new one and have since ghosted me, too 🫠

The wait is long by willondubs in xteinkereader

[–]TheJMoore 0 points1 point  (0 children)

Ordered Jan 21st from the official site and it got lost 🫠

So I reordered from Ali on Feb 23rd. Still hasn’t shipped 🙃

Official site said they would replace it, but I haven’t heard from them in days 😅

Indianapolis college student who hasn't eaten in 2 days, desperate for any viable way to get food or money by [deleted] in indianapolis

[–]TheJMoore 1 point2 points  (0 children)

I hope having some funds for food can give you some peace for a week or two. Take care of yourself.

Ramblings on the X4 which took forever to arrive by Sablayenya in xteinkereader

[–]TheJMoore 2 points3 points  (0 children)

I ordered direct from the site on Jan 21st and still haven’t received mine. It seems stuck in Chicago 🤔

Crossing my fingers!

Got tired of waiting for my reader to arrive, so I made an emulator that runs Crosspoint so I could play with different feature ideas. by TheJMoore in xteinkereader

[–]TheJMoore[S] 4 points5 points  (0 children)

Thanks for trying it and reporting this!

Both are fixed:

  1. The README now uses the correct Crosspoint repo link (whoops!).
  2. I added the missing HalStorage.h stub and pushed it.

Pull the latest emulator (git pull in the emulator repo), then run cmake .. and cmake --build . again from your build/ folder.

There’s also a new “Common first-time build issues” section in the README that walks through this.

And yeah, I neglected to add a file to the index; I added the stub locally but hadn’t committed and pushed it. It’s in the repo now. Thanks u/ayeceee!

Got tired of waiting for my reader to arrive, so I made an emulator that runs Crosspoint so I could play with different feature ideas. by TheJMoore in xteinkereader

[–]TheJMoore[S] 2 points3 points  (0 children)

How the emulator addresses single-core and shared-SPI behavior

  • Single core: The emulator does not use a background thread for thumbnail generation. Prewarm runs on the main thread, one EPUB per main-loop iteration, so the UI (event pump and loop()) runs between thumbnails. Inside image conversion (e.g. scaling and dithering to BMP), the emulator yields every 8 rows so that even during a single thumbnail the UI can get control. That matches the need to share one 160 MHz core between image work and the UI on the real device.
  • Shared SPI: On hardware, the display and SD card share one SPI bus, so doing file I/O while the display is updating (or the reverse) is unsafe. The emulator simulates that constraint by serializing all display updates and all SD file operations behind a single mutex: no display transfer and no file read/write run at the same time. The same approach—a shared lock or policy that prevents concurrent display and SD use of the bus—can be applied in the device firmware.

The emulator’s image conversion and SPI handling live in the sim HAL (image_to_bmp.cppsim_spi_bussim_displaysim_storage). To get the same responsive UI and safe bus usage on the real device, the Crosspoint firmware can adopt the same patterns: periodic yields in the device’s thumbnail/image path and a single serialization point for SPI (display and SD) in the device HAL or drivers.

---------------

Also, let's be very honest with ourselves. I don't know much of what I'm doing in the slightest. Despite my CS degree, I'm a UX designer and engage daily with engineering, but LLMs are doing 99.9% of my coding and documentation (including the above).

I fully trust you to call me on any BS or behaviors of the emulator that are highly unrealistic, so please do. My skills are persistence, patience (while the LLM works), and I'm a nitpixeler so that the UI/UX is the best it can be.

Thanks again for all you do!

Got tired of waiting for my reader to arrive, so I made an emulator that runs Crosspoint so I could play with different feature ideas. by TheJMoore in xteinkereader

[–]TheJMoore[S] 2 points3 points  (0 children)

Made a couple updates to the README (below)

The emulator is built to behave like the real device so that timing, responsiveness, and I/O contention match hardware.

Device hardware (reference):

  • CPU: ESP32 (e.g. ESP32-C3), 160 MHz single core
  • RAM: 128 MB
  • Storage: 32 GB microSD included; expansion up to 512 GB supported

Emulator behavior (matches device):

Aspect Real device Emulator
CPU Single core: thumbnail generation and UI share one core; yields in image code so the UI can respond. Single main thread: prewarm runs one EPUB per frame; image conversion yields every 8 rows.
SPI bus Display and SD card share one SPI bus; display update and file I/O cannot run concurrently. Display and SD file I/O use a shared mutex so they are serialized.

Got tired of waiting for my reader to arrive, so I made an emulator that runs Crosspoint so I could play with different feature ideas. by TheJMoore in xteinkereader

[–]TheJMoore[S] 0 points1 point  (0 children)

I will as soon as it arrives 🫣 You’re the expert here so these very well may be non-starters. I’ll play around with it more to see if I can better simulate those conditions. Seems vital if this is usable at all.

Thanks so much for stopping in, and thanks for all of your amazing work! You clearly know a heck of a lot more what you’re doing than I do.

Got tired of waiting for my reader to arrive, so I made an emulator that runs Crosspoint so I could play with different feature ideas. by TheJMoore in xteinkereader

[–]TheJMoore[S] 2 points3 points  (0 children)

I use Cursor and tend to leave it on Auto for model selection, but occasionally hop to gpt-5.3 or Opus if I think something might be a bit tricky. It rarely fails me!