Based on the feedback I will follow the opt-in way. I initially thought unset means "doesn't matter" or "not important maybe I will decide later" at least that was my reason. Obviously I was very wrong:) Thanks @moid, @sunset 19:36.

@Daan you give me a fresh angle to think. Indeed I agree with you bigger != better and faster != better neither. "Growth at the rate of trust" probably will not be very popular in a board meeting but I enjoy it and I will take it in mind when I build for SSB. Ideally there are two kinds of people I wish to bring in. One is people like you who share similar beliefs and who also would join the dev. Hopefully they will ease the resources constrain problem you mentioned and they will find a home. Everyone will be happy. The 2nd kind is more personal as I have a science background. I want to bring scientists here. The immutable feed history is perfect for scientists. This is the reason I will support latex in the website.

The tech part is hardly cool:) Many people here probably can redo it in two weekends and in a better form. I used hugo as the static site engine and python for other parts. I have close to zero knowledge in html, css, java-script and my design taste will not help me either. Therefore the look and function of the website itself is minimized and probably very boring for many. Also I want people to really use SSB clients rather than my website. I intentionally did not implement many functions which can easily achieved with clients of SSB.

I use google cloud for serving the content but I think one can also serve with a pi. The resource consuming part is hugo building as hugo is not targeted to big site yet. I tested for all current SSB content of 20K feeds and one needs a machine with 30GB RAM currently. Hugo also does not support incremental build so I have to regenerate the whole thing when new messages come in. Therefore, I plan to only update the site daily at least for the moment to reduce cost.