ChatGPT said:
No — you cannot make your X.com bookmarks public.
Here’s the key thing to know about bookmarks on X (formerly Twitter):
-
Bookmarks are private by design. Only you can see the posts you’ve bookmarked when you’re logged into your account. No one else can browse your bookmark list. Help Centre
-
The platform does not offer a setting to share your bookmarks publicly or display them on your profile. Help Centre
-
What can be visible to others is the bookmark count on individual posts — the total number of times a post has been bookmarked — but not who bookmarked it or your personal bookmark list. Help Centre
Workarounds (not official or for full public sharing)
If you really want to share your bookmarks with others, you’d have to do something manual or use third-party tools:
-
Manually share bookmarked posts — copy links of tweets you’ve bookmarked and post them yourself (in a thread, list, or note).
-
Export or use a third-party tool that can read your bookmarks and let you publish them somewhere else (e.g., a personal blog or document). However, these aren’t official X features, and you should be careful with privacy and security when granting access to third-party apps. Chrome Web Store
But as of now: X does not allow publicly viewable bookmark lists on user profiles at all. Help Centre
If you want, I can explain safe ways to share a curated list of your bookmarks publicly (e.g., via a separate list or other platform).
You said:
ChatGPT said:
Here’s how to make a separate, public list on X that works like shareable bookmarks 👇
Option 1: Use X Lists (best built-in method)
Lists can be public and are meant for curation.
Steps:
-
Go to Profile → Lists
-
Click Create new list
-
Give it a name (e.g. Saved Tech Threads)
-
Set Privacy = Public
-
Create the list
Add posts you like:
-
When you see a post you want to “bookmark publicly,”
→ tap Share → Add to List (or add the author to the list) -
Alternatively, open the list and add accounts whose posts you want collected there
How people see it:
-
Anyone can visit the list via its URL
-
It updates automatically as those accounts post
Limit: Lists are account-based, not post-based. You can’t add individual tweets unless you add the author.
Option 2: Manual “Public Bookmarks” thread
If you want specific posts only:
-
Create a tweet like:
“Public bookmarks 🧵👇” -
Reply to it with links to posts you’ve bookmarked
-
Pin the thread to your profile (optional)
This gives you full control and works well for curated content.
Option 3: External collection (Notion / Google Doc / blog)
-
Copy links from your bookmarks
-
Paste them into a public page
-
Share the link on your profile
Best if you want categories, notes, or long-term organization.
Quick recommendation
-
Auto-updating + native to X → Public List
-
Precise curation → Thread
-
Advanced organization → External page
If you want, tell me what kind of content you’re bookmarking (news, art, study resources, memes, etc.), and I can suggest the cleanest setup.
You said:
ChatGPT said:
Short answer: only authors — not individual posts.
On X Lists:
-
❌ You cannot add a specific post to a List
-
✅ You can only add entire accounts (authors)
-
Once an author is on the List, all of their posts show up there
So Lists don’t work if you want “only these 5 posts from this person”.
Best ways to save specific posts publicly
✅ Best X-native method: Curated thread
This is the closest thing to “public bookmarks”.
How:
-
Create a tweet like:
“Public bookmarks: useful threads 🧵” -
Reply to it with direct links to specific posts
-
Keep adding replies over time
-
(Optional) Pin the thread to your profile
Pros
-
Exact post-level control
-
Fully public
-
Easy to update
Cons
-
Manual
✅ Alternative: Multiple themed threads
Example:
-
🧵 Saved coding tips
-
🧵 Saved study resources
-
🧵 Saved art inspiration
This keeps things organized and readable.
✅ Outside X (best for organization)
If you want tags, notes, or search:
-
Notion
-
Google Docs
-
Personal site
Then link it in your bio as “Public bookmarks”.
What doesn’t work
-
❌ Lists → authors only
-
❌ Bookmarks → always private
-
❌ Likes → public but messy + algorithm-driven
Recommendation
Since you want specific posts only, use:
👉 A pinned thread (or threads)
If you want, tell me:
-
how many posts you expect to save
-
whether you want categories
and I’ll suggest a clean structure (even a copy-paste starter tweet).
You said:
ChatGPT said:
A pinned thread is just a thread of posts that you pin to the top of your profile so it stays visible.
Let’s break it down simply 👇
What is a thread?
A thread = multiple posts connected by replies.
Example:
-
Post 1: “Public bookmarks 🧵”
-
Post 2 (reply): link to Post A
-
Post 3 (reply): link to Post B
-
Post 4 (reply): link to Post C
Anyone opening the first post can scroll through all the replies.
What does “pinned” mean?
When you pin a post:
-
It stays at the top of your profile
-
Everyone sees it first when they visit you
-
It doesn’t move down as you post new things
You can only pin one post at a time.
So a pinned thread means:
-
You pin the first post of the thread
-
The whole thread is easy to find
-
You keep adding replies to it over time
Think of it as a public, curated bookmark list on your profile.
How to make one (step-by-step)
-
Create a post like:
“📌 Public bookmarks: useful posts I want to save & share 🧵👇” -
Reply to your own post with a link to a post you want to save
-
Repeat whenever you want to add another post
-
Tap ⋯ on the first post → Pin to profile
Why people use pinned threads
-
Share resources
-
Save specific posts (not whole accounts)
-
Keep collections public
-
Easy for others to bookmark or follow
If you want, I can:
-
write a clean starter post you can copy
-
suggest ways to organize multiple pinned threads (since you can pin only one)
Just tell me 👍
You said:
ChatGPT said:
That’s actually a very solid idea 👍
It fits your goals well, with a few trade-offs to be aware of.
Let me evaluate it point by point and then suggest a small improvement.
Your goals vs your plan
1. Share tweets publicly, even without an X account
✅ Yes, this works.
Thread Reader unrolls threads into a normal web page that:
-
Works without logging in
-
Is readable, scrollable, and shareable
-
Is stable over time (usually)
This directly solves the “X login wall” problem.
2. All saved posts live in a single thread
⚠️ Works, but with limits.
Pros
-
One canonical place
-
Easy to maintain
-
Easy to pin
-
Easy to unroll
Cons
-
Very long threads can get:
-
Hard to navigate
-
Slow to load on X
-
Hard to scan for topics
-
-
No internal categories unless you manually label posts
Still totally usable, just something to keep in mind.
3. Use @threadreaderapp to unroll and share
✅ Excellent choice.
Thread Reader:
-
Is widely used and trusted
-
Produces clean, readable pages
-
Lets you update the unroll when the thread grows
-
Is ideal for non-X audiences
This is a smart workaround to X’s limitations.
Overall verdict
✅ This is a good, practical, and low-effort system.
It’s one of the best ways to create public, shareable bookmarks from X.
If I had to rate it:
8.5 / 10 — strong and simple.
One small improvement (highly recommended)
Instead of one giant thread, use:
🔹 One pinned index thread
Then link to multiple themed threads
Example structure:
📌 Pinned thread
“Public bookmarks index 🧵
– Tech & AI
– Writing
– Learning
– Misc”
Each reply links to another thread:
-
Thread A: Tech posts
-
Thread B: Writing posts
-
Thread C: Learning posts
Each of those can be unrolled separately with Thread Reader.
Benefits
-
Cleaner
-
Scales better
-
Easier for readers
-
Easier to update
-
Still pin-friendly
If you want, I can help you:
-
Write a clean starter index tweet
-
Design a naming/labeling system for posts
-
Decide when to split threads
-
Optimize it specifically for Thread Reader
Just tell me how much content you expect to save (dozens vs hundreds).
You said:
ChatGPT said:
Great question — you can optimize a lot for Thread Reader with a few simple habits. Below is a practical, battle-tested checklist.
1. Write a “Thread Reader–friendly” first tweet (VERY important)
Thread Reader uses the first tweet as the page title and intro.
Do this:
-
Clear title
-
Short explanation
-
No emojis spam
-
No “👇” dependency (Thread Reader removes context)
Example:
Public bookmarks — selected posts I want to share
This thread is a curated list of links. Updated regularly.
This becomes the headline on the unrolled page.
2. Use one link per tweet (max clarity)
Thread Reader renders best when each reply contains:
✅ One link
⚠️ Optional short description
❌ No multiple links in one tweet
Good:
“On learning systems thinking
https://x.com/….”
Avoid:
“Great thread + related article + video
link1 link2 link3”
3. Add a short label at the start of each tweet
This makes the unrolled page scannable.
Recommended format:
-
[AI] -
[Writing] -
[Learning] -
[Misc]
Example:
[AI] Clear explanation of transformers
https://x.com/…
On Thread Reader, this looks like a clean list.
4. Avoid reply nesting (always reply to the main tweet)
Thread Reader follows the linear reply chain.
✅ Always reply to the first tweet, not to other replies
❌ Don’t create sub-threads
This keeps the unroll complete and ordered.
5. Re-unroll when you add content
Thread Reader does not auto-update.
After adding new replies:
-
Reply again with
@threadreaderapp unroll -
It will regenerate the page with new items
Tip: You can bookmark the Thread Reader page URL and keep sharing the same one.
6. Use spacing and minimal formatting
Thread Reader preserves:
-
Line breaks
-
Basic punctuation
It does not preserve:
-
Fancy emoji layouts
-
Visual hierarchy tricks
-
X-specific UI cues
Keep it simple.
7. Don’t rely on likes, polls, or embeds
Thread Reader:
-
Shows text and links well
-
Shows images reasonably
-
Does not handle:
-
Polls
-
Quote-tweet context
-
Like counts / engagement signals
-
If context matters, add one sentence of explanation.
8. Add a “last updated” marker (optional but nice)
At the top or bottom:
Last updated: Jan 2026
Helps readers trust the list is maintained.
9. Thread length: practical limits
Thread Reader handles long threads well, but for sanity:
-
~50–100 links → ideal
-
100–200 → OK, but consider splitting
-
300+ → split into themed threads
Recommended “perfect” template
Main tweet:
Public bookmarks — curated posts worth sharing
One link per reply. Updated regularly.
Each reply:
[Category] Short description
https://x.com/…
Final verdict
Your idea + these optimizations = very clean public bookmark system, readable even outside X.
If you want, I can:
-
Draft a copy-paste starter thread
-
Suggest category labels based on your interests
-
Help you design an index + multiple Thread Reader pages
Just tell me how formal or minimal you want it.
You said:
ChatGPT said:
Here are good alternative solutions to your idea, compared honestly against your Thread Reader–based approach, so you can choose what fits you best.
I’ll focus on options that work for non-X users, support specific posts, and scale.
Baseline (your current idea)
Pinned thread → unrolled with Thread Reader
Strengths
-
Native to X
-
Zero setup
-
No login required for readers
-
Easy to maintain
Weaknesses
-
Linear only
-
Limited structure
-
Depends on a third-party bot
Alternative 1: Public Notion page (most flexible)
How it works
-
Create a public Notion page
-
Each entry = link to a specific tweet
-
Optional notes, tags, sections
-
Share the Notion URL
Pros
-
Fully public, no X account needed
-
Categories, search, notes
-
Clean reading experience
-
Scales to hundreds/thousands of links
Cons
-
Manual copy-paste
-
Not X-native
-
Slightly more effort
Best if: you want structure + longevity.
Alternative 2: GitHub Pages / Markdown list (very durable)
How it works
-
Maintain a Markdown file:
md## AI - [Short description](tweet link) -
Publish via GitHub Pages
Pros
-
Extremely stable
-
Fast loading
-
Versioned history
-
Great for technical audiences
Cons
-
Requires GitHub comfort
-
Manual updates
Best if: you like minimal, permanent archives.
Alternative 3: Telegram / Discord channel
How it works
-
Create a public channel
-
Post links to tweets with short descriptions
-
Share channel link publicly
Pros
-
No X login required
-
Chronological
-
Mobile-friendly
-
Easy to post to
Cons
-
Not great for browsing old content
-
Platform lock-in
Best if: you want a feed, not an archive.
Alternative 4: “Likes” + third-party viewer (weak but simple)
How it works
-
Like tweets
-
Use third-party tools that expose likes publicly without login
Pros
-
Zero effort
Cons
-
Fragile
-
Not reliable
-
No curation
-
Depends heavily on external services
Best if: minimal effort, low expectations.
Alternative 5: Static blog (Hugo / Astro)
How it works
-
One page = “Saved Tweets”
-
Each item = embedded tweet or link
Pros
-
Own your content
-
SEO-friendly
-
Custom design
Cons
-
Setup overhead
-
Maintenance
Best if: you already have a site.
Recommendation matrix
| Need | Best option |
|---|---|
| Fastest, X-native | Thread Reader (yours) |
| Best organization | Notion |
| Long-term archive | GitHub Pages |
| Feed-style sharing | Telegram channel |
| Maximum control | Static site |
My honest take
Your original idea is one of the best “low friction” solutions.
If you want to improve without switching:
-
Add an index thread
-
Split by topic
-
Keep Thread Reader as the public face
If you want to upgrade:
-
Thread Reader → Notion hybrid is the sweet spot
(thread for capture, Notion for consumption)
If you want, tell me:
-
whether you prefer minimal effort or maximum structure
-
how technical you are
and I’ll narrow it to one clear recommendation.