I am not sure, if you mean bookmarks or bookmarklets. You can have as many bookmarks as you want, but they will always link to an external source.
If you mean bookmarklets, which are stored directly in the browser, you will have no luck.
Tiddlywiki is too big for a bookmarklet. Bookmarklets are URLs and can be about 64k.
So can you be more precise, what you need?
Can we create our own TiddlyHost? Because in the Q&A for this TiddlyWiki host, we could.
My goal is to create a hosted TiddlyWiki, and register each hosted wiki as an Internet favorite. That’s why I’m asking you if we can create our own TiddlyWiki host.
The power of TiddlyWiki is its interconnections. Having many tiddlywikis in a “library” of them ends up being really demanding in terms of storage and bandwidth (since each one would include the TiddlyWiki “engine”, though the “external core” option reduces this effect a bit). And it also undercuts the value of interconnections. Comparing multiple TiddlyWikis is possible (if CORS is enabled, and you have the right permissions set up), but awkward. t’s much easier to make an explicit link, or to look for patterns, within the same wiki.
However, it certainly makes sense to have a single TiddlyWiki in which to store all one’s internet bookmarks and associated ideas.
How many wiki’s do you think you will want to set up?
ChatGPT is not a good source of information when there is very little training material.
As far as we know here, there are no specified limits on TiddlyHost. Maybe @simon can clarify.
However, in my experience, a TiddlyWiki file slows down when it is about 10Mb size and becomes unusable at 30Mb. That is why it is better to not embed images but instead link to them.
To answer the question I think you’re asking: If you make a TiddlyHost account, you can make multiple “separate” wikis from that account, and each of those wikis can be independently configured to be private, public, or public-and-searchable on the TiddlyHost hub. And you can of course make a separate browser bookmark to take you directly to each wiki. Browser bookmarks don’t “host” anything, and no one else actually has any idea what you’ve bookmarked. They’re just a way to save a link for your own convenience.
All of this is possible with a standard free TiddlyHost account.
However, as @Springer says, if you subdivide your wikis too much, they may actually become less useful to you. While it makes sense to separate wikis with wildly divergent purposes (like a recipe app vs. a daily journal vs. a personal contacts manager vs. a wiki you’re using for work), if your goal is to create a personal knowledge base, it may be more useful to keep your various notes in the same wiki and simply tag them with their relevant topics.
Additionally, while @simon generously offers TiddlyHost as a free service for the community, it’s polite not to abuse that generosity by wasting too much of his bandwidth. So again, you may wish to consider how many separate wikis you really need… and if the answer is “a lot”, and if you do need them to be available online (rather than saved on your phone/computer/local server, which is free and only limited by your disk space — and you can make browser bookmarks to local files), you may want to explore an alternate hosting solution. TiddlyPWA might be a good option if these are intended to be truly private/personal wikis, though you’d need to see whether @valpackett has any updated recommendations for free hosting.
If you’re willing to take a chance and wait for something better, then I think MWS is the best answer. Although MWS was developed with multiple users in mind, I believe it’s also great for a single user in many different areas. Currently, I have many TiddlyWikis that need the enhanced management that MWS provides.
Speaking of MWS, because it uses SQLite to store data, you’ll need a server. On the plus side, you can create as many TiddlyWikis as you want, and each one can be configured individually. I’m not sure how far along MWS development is or if it’s ready for official use, but I’m really looking forward to its release.
check the docs: https://mws.tiddlywiki.com/
and @Arlen22 may tell more details
Are you saying that until a better solution comes along, I should turn to MultiWikiServer? It’s just a temporary solution, right?
I think we could give you more help if we understood what or why you want what you are asking.
I is really not clear to me, and I have being making bookmarklets a lot.
Could you explain what content your wiki or bookmarlet’s will contain. Just so we know what you are trying to achive in the end. perhaps describe what you would do day to day if you have what you are asking for?
I think MWS is the best solution. It’s not fully developed yet, so you’ll have to wait a while longer. However, you can start using it early, as long as you make sure to back up your files. MWS makes it very easy to manage a large number of TiddlyWikis. You could have one bookmark per TiddlyWiki file, which is no problem as long as you have enough storage space. I tried MWS a few months ago and was very impressed. For now, TidGi is completely sufficient for my needs, so I’m willing to wait for MWS to be more plug-and-play before I start using it.
Actually, my main focus is writing about the lore of my favorite video games, followed by writing about topics that interest me, such as culture, science, technology, etc… I mainly need the advanced features of TiddlyWiki, not Obsidian, because Obsidian doesn’t have any of the features I’m looking for, namely the fact that it’s open-source and 100% customizable.
If you’re just writing, then a single TW should be fine, and you can probably make a dozen at TiddlyHost without causing problems.
The problem is if you’re also adding imagery or attachments. Then the wiki’s become very large. The best way to handle this is to post the images somewhere else and use image links to reference them.
TiddlyHost is not the only way to use TiddlyWiki. Are you using TiddlyHost because it is easy to set up, or because you need to access your files from different machines?
I was looking at Obsidian yesterday. It is amazing. But, yes, it is not open-source 
Good luck!
But it’s to do an in-depth analysis of each character, each element of the game. So each topic I’m going to write about is equivalent to a big tome, and I’m not sure a TiddlyWiki would be able to handle all the topics! However, it is worth mentioning that I will be creating tons of archives that will be consulted at any moment.
Keep in mind that if the main content is text you can store a lot of text in a tiddlywiki. Some time a go I guestimated that we could store one or two encyclopedias of text without straining a single file wiki. Media is always a lot bigger, but there are a range of approaches to minimise the memory requirements.
As @Mark_S says, I suggest start with one wiki, keep your text well organised, such as using tags and it will be easy for you to split it if needed (I think very unlikely).
That’d be my guess too.
The King James Version bible is reasonably well understood as “a lot of text”, and that clocks in at only a little more than 4 meg of text - about 770 thousand words.
Otoh, a decent image is maybe 100kb minimum - meaning the same 4meg will only store 40 images at that size.
From this we can calculate that the old adage “a picture is worth a thousand words” is wrong.
In the digital era, an image is worth (rounding up slightly) about 20,000 words.
But I need to create a wiki for each character, including media (images, sounds, videos, etc.)! I just write everything I know about each element, and you’ll see that I’m very thorough in my research on this subject.
My TiddlyWiki is around 35Mb and no problems, it is used on my android phone, tablet and ten year old laptop (which was considered fast in the day but not so much now).
I avoid embedding images, I link to them as you say - on Android I have to use RCX server to get this to work properly.
I have found Telmiger’s details widget invaluable for performance, I haven’t gone into it in detail but it seems that when content is hidden within the HTML details tag then it does not take up resources until it is opened to be viewed. Example I have a tiddler which gives me a word count, back link count and other stats on my knowledge base TW - these are obviously computationally demanding and the lag when displayed on the storyriver, even if out of view is appreciable - simply putting the code that does the counting inside a reveal section clear this up completely. Pretty much all of my longer text based tiddlers have a reveal around the main content, some have a few lines of text outside as an intro, this works better for me than the native open-close tiddler functionality.
In fact, all I wanted to tell you was one subject per tiddler. Afterwards, so that I can reorganize my files and folders in a tree structure on my PC, because I’m picky about storage. But MWS seems to be the best for organizing TiddlyWikis by folders and subfolders. So I think the best approach is to install Raspberry Pi and wait until 2030 to get a DNA hard disk.
File storage on disk is really just a virtualization.
You can create virtual “folders” in TiddlyWiki using tagged tags. See the table-of-contents as an example.
Offhand, I think only Obsidian and Qownotes reflect the structure on the disk.
I don’t think we’ll have DNA hard disks by 2030. If we do, they’ll be archive-only.
If you’re serious about waiting for MWS (I wouldn’t), you could start now using visual code editor to create your documents. Or qownotes.
In any case, that’s how I work. One wiki per subject. I’d be completely confused if I put all my topics in a single wiki.