Thanks for these suggestions! Dark mode: working on it. This is a limitation of the search index engine and how it handles individual tokens. There are multiple 'strategies' to use and the one that fits most use cases looks like 'size' and 'sizze' as two different words. There's not much I can do about that without significantly changing the index configuration. I believe the solution might be to up the 'fuzzy' settings and I'll take a closer look at that - I do need to do better in terms of getting closer to a UX that folks expect from Google. That's a tough one. I actually agree with this concept but I worry that any type of messaging opining about content can put a lot of Bitcoiners off. Transparently: I am removing a bunch of 'inappropriate' words from the search marquee at the bottom (you won't see this if you're using Safari due to marquee performance issues on that platform) but if someone types in a word and that word is somewhere in the index, it will come back with results. Luckily I'm only dealing with text and not images. Additional transparency: I have a censor flag I can flip on a tx in case there is something that is clearly 'very very bad' - if I flick that switch for a tx, the encoding results won't be shown in the UI - so you'll still get a result - you just won't see the decoded text. Thanks for the reference - I took a look at that and I think I'll skip that for the moment - not sure the juice is worth the squeeze unless lots of people start asking for it.
Thanks for these suggestions! Dark mode: working on it. This is a limitation of the search index engine and how it handles individual tokens. There are multiple 'strategies' to use and the one that fits most use cases looks like 'size' and 'sizze' as two different words. There's not much I can do about that without significantly changing the index configuration. I believe the solution might be to up the 'fuzzy' settings and I'll take a closer look at that - I do need to do better in terms of getting closer to a UX that folks expect from Google. That's a tough one. I actually agree with this concept but I worry that any type of messaging opining about content can put a lot of Bitcoiners off. Transparently: I am removing a bunch of 'inappropriate' words from the search marquee at the bottom (you won't see this if you're using Safari due to marquee performance issues on that platform) but if someone types in a word and that word is somewhere in the index, it will come back with results. Luckily I'm only dealing with text and not images. Additional transparency: I have a censor flag I can flip on a tx in case there is something that is clearly 'very very bad' - if I flick that switch for a tx, the encoding results won't be shown in the UI - so you'll still get a result - you just won't see the decoded text. Thanks for the reference - I took a look at that and I think I'll skip that for the moment - not sure the juice is worth the squeeze unless lots of people start asking for it.

Thanks for these suggestions! Dark mode: working on it. This is a limitation of the search index engine and how it handles individual tokens. There are multiple 'strategies' to use and the one that fits most use cases looks like 'size' and 'sizze' as two different words. There's not much I can do about that without significantly changing the index configuration. I believe the solution might be to up the 'fuzzy' settings and I'll take a closer look at that - I do need to do better in terms of getting closer to a UX that folks expect from Google. That's a tough one. I actually agree with this concept but I worry that any type of messaging opining about content can put a lot of Bitcoiners off. Transparently: I am removing a bunch of 'inappropriate' words from the search marquee at the bottom (you won't see this if you're using Safari due to marquee performance issues on that platform) but if someone types in a word and that word is somewhere in the index, it will come back with results. Luckily I'm only dealing with text and not images. Additional transparency: I have a censor flag I can flip on a tx in case there is something that is clearly 'very very bad' - if I flick that switch for a tx, the encoding results won't be shown in the UI - so you'll still get a result - you just won't see the decoded text. Thanks for the reference - I took a look at that and I think I'll skip that for the moment - not sure the juice is worth the squeeze unless lots of people start asking for it.

Thanks for these suggestions! Dark mode: working on it. This is a limitation of the search index engine and how it handles individual tokens. There are multiple 'strategies' to use and the one that fits most use cases looks like 'size' and 'sizze' as two different words. There's not much I can do about that without significantly changing the index configuration. I believe the solution might be to up the 'fuzzy' settings and I'll take a closer look at that - I do need to do better in terms of getting closer to a UX that folks expect from Google. That's a tough one. I actually agree with this concept but I worry that any type of messaging opining about content can put a lot of Bitcoiners off. Transparently: I am removing a bunch of 'inappropriate' words from the search marquee at the bottom (you won't see this if you're using Safari due to marquee performance issues on that platform) but if someone types in a word and that word is somewhere in the index, it will come back with results. Luckily I'm only dealing with text and not images. Additional transparency: I have a censor flag I can flip on a tx in case there is something that is clearly 'very very bad' - if I flick that switch for a tx, the encoding results won't be shown in the UI - so you'll still get a result - you just won't see the decoded text. Thanks for the reference - I took a look at that and I think I'll skip that for the moment - not sure the juice is worth the squeeze unless lots of people start asking for it.