The first thing when you want to use tor browser painlessly is you should configure your browser properly to use tor.service. This improves the performance and connection speed greatly for me. Follow steps in 3.2 and 3.3 and make sure you save your tor controll password in a safe place. Even you can write it down on a paper. This password will also be used when you open nyx dashboard.

It's weird because there's no official documentaion on how to configure a bridge in torrc. They only focus on the buttom-config for browser. The old documentaion site might has more detailed information on configure torrc.
For me, without using a pluggable transport will result in connection timeout, I guess this can be avoided if you're in a better network connection environment.
Here is the specifications for pluggable transports: https://spec.torproject.org/pt-spec/
Snowflake
I use a snowflake transport together with a snowflake client (aur/snowflake 2.9.0-1), and it's easy to configure in torrc (for more details see the manual):

UseBridges 1
ClientTransportPlugin snowflake exec /usr/bin/snowflake-client
Bridge snowflake xxx

Please notice that if you use a different client, the exec path should be different. Find a snowflake bridge by accessing about:config in the browser, then search for snowflake, you'll find some default snowflake bridges, then, copy-paste all the text at the second col, replacing the xxx, then it's all done. If there's no default bridge, try to find a stable one by requesting their email. Don't forget do a service restart. In general, a snowflake bridge is more stable and fast than a obfs4 in a censored area.
Obfs4
The configuration is just the same as that for snowflake. Download the client for obfs4 and replace the execution path.
Also see
- https://forum.torproject.org/tag/snowflake
- Snowflake, a censorship circumvention system using temporary WebRTC proxies: https://www.bamsoftware.com/papers/snowflake/ (pdf)

They provide a tool, Nyx. Currently I'm still using the default config, and it works just fine.

>1. don't admit anything from tor activities (especially when in illegal activities & when talking to police)
>2. use bridges when using tor (to hide tor traffic)
>3. don't get cocky & show yourself for reasons of fame or fortune
>4. & NEVER mix clear or deep or dark -net activities with each other
>5. use a password manager for tor activities & then another for clear-net activities
>6. create a kill-switch Encryption device that works wirelessly (to defeat a Ross Ulbrich scenario)
>7. drop accounts that are linked & after email-bombing them delete them to obfuscate your traffic.
>& that's how you are at least somewhat safe on tor (plus using a physically different device for tor network activities will probably be your best bet)
Btw, 4 is really so hard for me.

How?
Just use another browser (in my case, Librewolf. My main in using browsers are Mercury and Palemoon). Since the huge black frame of Tor browser is for safety concerns, i.e. normalize every fingerprints:
>Their strategy is to have all users converge towards a normalized fingerprint.
>…
>They removed plugins, canvas image extraction is blocked by default, and well-known attributes have been modifeid to return the same information on all operating systems. They also defend against JavaScript font enumeration by bundling a set of default fonts with the browser.
>arxiv.org/abs/2110.10129
So ackchyually. When you browsing some obviously safe websites, like mine, or those neocities sites, simply use a normal browser with torsocks port configured! (Even if you are too lazy to configure torsocks, you launch your Tor browser at another workspace and leave it alone; Go to another port configured browser and enjoy your journey.)