Threads I follow
Threads I follow is your private list of forum conversations, with an unread mark when a new reply is waiting. During the trial, only invited members post in the forum.
Threads I follow
The list is empty for now.
Beginner
What following a thread means
A thread is one conversation: a title, a first post, and the replies under it. Following means you add that conversation to a list that only you see.
Each thread will have a Follow button. Press it to add the thread. Press it again to take the thread off the list. A followed thread stays until you remove it, including when nobody has written for a while.
An unread mark shows that the thread has replies you have not opened since you last read it. Open the thread, read those replies, and the mark clears. The mark is how you spot change without opening the whole forum.
There are no threads on the list yet. Until there are threads, start with these three pages, and follow the matching threads once they exist:
- What is AI? and the glossary for words that show up in every thread.
- How to talk to AI and the prompt course. A prompt is the instruction you type into a chat.
- Infrastructure for graphics cards, memory, and deskside machines.
The list will have three starter folders: Prompts, Code, and Hardware. A folder is a label on a followed thread. Put lesson threads and saved prompt collections in Prompts. Leave Code and Hardware empty until you are working on a program or a machine.
Keep the first list short. One lesson series, one glossary thread, and one guide you are using is enough to check. Follow every new title and you get more unread threads than you can read.
My first follow rule
I am an adult learning AI from scratch. I have a private list called Threads I follow. I can press Follow on a thread, sort threads into folders named Prompts, Code, and Hardware, and I get an unread mark when a followed thread has replies I have not opened. Email is off unless I turn it on. Write a five-line rule for my first month: what belongs in Prompts, what I should leave alone, and three questions to ask before I press Follow. Use plain words. Do not invent thread titles, member names, post counts, or quotes.
Intermediate
Alerts, email, and the three folders
The follow list and the alerts are separate choices.
Browser notifications are notices the browser can show outside the page. The site may ask only after you click a button, and only on https. Before you answer, permission is default and nothing is shown. Allow means granted. Block means denied, and you change that in the browser's site settings. Notices while a Polaris tab is open use that permission. A notice after you close the tab needs a second yes: a push subscription held by a service worker, a small script the browser keeps for the site.
Email starts off. Turn it on for mail about new replies in threads you follow, and turn it off again later. The Swedish Marketing Act lets a company email you marketing only after you have agreed, with a narrow exception after a purchase. Thread mail is a notice you asked for, and the switch still starts off.
Put each followed thread in one folder:
- Prompts: instructions, lesson series, and guides you reuse. Keep the prompt library beside that folder.
- Code: a program, a library, an error message, or a tool update.
- Hardware: a graphics card, memory, a home build, or a shared machine if Polaris buys one.
In Discourse, a widely used forum program, replying to a thread sets it to Tracking, which shows a count of new replies. On Polaris the same control stays off. Press Follow yourself when the thread belongs on your list.
Set my alert rules
I follow forum threads about AI. Browser notifications require me to click a button and choose Allow, and they work on https. A notice after I close the tab needs a separate push subscription through a service worker. Email about replies starts off. Replying does not put a thread on my list. Folders are Prompts, Code, and Hardware. Write a one-page personal policy: which folder gets which kind of thread, when I allow the browser, when I turn email on, and when I leave a thread unfollowed. Plain words. Do not invent threads, member names, or activity.
Expert
What to watch when a job runs for days
Pick one level per thread. These four names are what Discourse uses for a single topic, their word for a thread.
Watching alerts you to every new reply and shows a count. Use it for a training log, a benchmark, or an official Polaris note. A benchmark is a fixed test that scores a model. A log records the job's settings, errors, and results.
Tracking alerts you when someone replies to you or writes your name, and still counts new replies. Use it for a long hardware-build thread you open when you have time.
Normal alerts you only about a reply to you or your name. The thread can stay off this list.
Muted sends nothing and hides the thread from your latest list.
Watching First Post applies to a category or a tag, not one thread. It pings the first post of a new thread, then drops back. Use it only for a tag you already care about, such as hardware.
VRAM is the memory on the graphics card. NVIDIA's CUDA runtime returns cudaErrorMemoryAllocation when a call cannot allocate enough memory. Follow a hardware thread that records the model name, the precision, and that error. Precision is how many bits each stored number uses. Fewer bits use less memory and can change answers slightly.
A reply does not follow the thread. Discourse sets a thread you answer to Tracking. The Polaris switch stays off. If Polaris buys a shared machine, notes about its queue can go on Watching in Hardware.
Choose a level for a long job
Help me choose a notification level for forum threads about local AI. Levels: Watching (every new reply, plus a count), Tracking (an alert only if someone replies to me or writes my name, plus a count of new replies), Normal (an alert only for a reply to me or my name), Muted (no alerts, and the thread stays off my latest list). Auto-follow when I reply is off. VRAM is graphics-card memory. cudaErrorMemoryAllocation means a CUDA call could not allocate enough memory. For each situation, pick one level, name the folder (Prompts, Code, or Hardware), and give the reason in two sentences: (1) a multi-day training log I am responsible for, (2) a hardware-build thread I check weekly, (3) a benchmark thread I answered once, (4) an official note about the queue, if Polaris buys a shared machine. Do not invent results, quotes, or member names.
Rules for the list
- The list is visible only to you.
- Follow is a button you press. Taking a thread off the list is the same button again.
- Writing a reply does not add the thread. Turn that on only if you want it.
- The unread mark means replies you have not opened. It clears when you read them.
- Browser notices wait for a click and your Allow. Email stays off until you opt in, and you can opt out again.
- Each followed thread sits in one folder: Prompts, Code, or Hardware.
- Mute a thread that has left the question you came for.
Levels at a glance
| Level | What reaches you | Also documented |
|---|---|---|
| Watching | Every new reply | A count of new replies |
| Tracking | Replies to you, and your name | A count of new replies |
| Normal | Replies to you, and your name | Set this when the thread can stay off your list |
| Muted | Nothing | The thread stays off your latest list |
Watching First Post belongs to a whole category or tag. It reports the first post of a new thread, then steps back. Use the four rows above for one conversation you already have open.
A shared community DGX Station would give a followed hardware thread a public queue on a deskside machine with up to 748 GB of coherent memory, so a model that stops with cudaErrorMemoryAllocation on a home card can run where the memory fits. About the shared station
Sources
- Using the Notifications APIMozilla's guide to asking permission on a click, the three states default, granted, and denied, and the https requirement.
- Push APIHow a service worker subscription can receive a message and show a notification after the tab is closed. The subscription endpoint must stay secret.
- Configuring default notification settingsDiscourse's five levels, and the default that a reply sets the topic to Tracking.
- Understanding Discourse for new usersHow a forum shows a new topic you have not opened and a count on a topic that has new replies. A topic there is a thread.
- Marknadsföringslagen for consumersSwedish Consumer Agency page, in Swedish. Email marketing needs your agreement first, with a narrow exception after a purchase.
- DGX Station system overviewNVIDIA's description of the deskside machine: up to 748 GB of coherent memory, a GB300 GPU with up to 252 GB of HBM3e, and models up to about 1 trillion parameters.
- CUDA runtime error codesOfficial meaning of cudaErrorMemoryAllocation: the call failed because it could not allocate enough memory or other resources.
- AI infrastructure on PolarisPlain-language page on the graphics card, VRAM, and numeric precision, to read while the forum has no hardware threads.