Inspired by this, I created a study/work Discord server that is focused on frontend design and development (arata.page/circle). Unlike the article in this thread, there are a few differences in our approach: first, the server doesn't enforce regular check-ins. Because the members are strangers from all over the places, we set our own schedule and do asnychronous chat during the break. Secondly, we tend to completely mute the input and output devices (some people like myself do a screenshare to keep them focus). This works alright for a tiny community like us.
> providing they can maintain a decent level of contrast
Safari wouldn't apply the theme-color if it makes the UI inaccessible (it has a very few narrow range of color that it won't apply). Also, if the tag is not specified, Safari would not blend the website content into the tab bar.
Relevant transcript from the first two minutes of the video:
> Since very early in the evolution of the web browser, most of the browsers we've used have had a few fundamental thing in common. There's a very tall toolbar at the top with a slot for the URL that's on it's own line. And the website stays inside this space, this portal to the web, the viewport. Of course, as users, we've trained ourselves to put all of our focus on the website that we're using, but for years, the browser itself has maintained a strong visual presence. No matter how a website is designed to look and feel, the browser interface framed that design and dominated it. What if we could get rid of that frame and extend the design of the website to every edge of the window? Well, that's what we've done in Safari 15. This year we've reimagined the browsing experience as we know it. We're putting all the focus on the web content. The new Safari blends the tab bar into each website by changing its background color. The entire interface is on one line, and things naturally appear when needed. This makes your content feel more expansive. Each web page or web app takes over, extending to all four edges of the window. The browser interface yields to the content.
> Brandon Toner on Twitter[3] even introduced me to a hashtag for them ...
Is it #digitalgarden?
> I believe the most important question regarding personal knowledge bases is how to make them social.
AFAIK note taking apps often have a feature to share notes, if that counts, e.g., Obsidian (view-only), Roam (view and edit), Notion (view, edit, and comment), and so on. With sharing and comments enabled, you can even use Google Docs as your PKB (some people actually do this), given that you don't need fancy features like bi-directional links.
Just like regular blogs, some gardeners also implement a social protocol called Webmention [1]. It's more like a pingback in WordPress than a collaboration tool though.
> A good shared knowledge base would by contrast also resemble Twitter -- but more organized, more navigable.
I would love to see this implemented in existing apps. The current solutions I know either involve 3rd party plugins (e.g., hypothes.is), or you have to self-hosted it yourself (e.g., cactus.chat, based on Matrix protocol).
Another alternative, which I learned from visiting other gardeners [2], is that you can link the edit button in your note to a GitHub PR. It's not friendly to non-developers who visit your garden, but this is better than nothing IMO.
> In practice the personal knowledge bases I've seen look much more like silos.
5 months ago there is a Show HN about a decentralized knowledge graph called Agora [3]. The cool thing is, everyone is part of one large knowledge graph, which means nodes (notes) from multiple users can be aggregated around [[topic]]. I hope the project is still alive..
ps. I'm sorry if I'm not making any sense.. I only started researching on this topic recently to create my own PKB (I literally published my first note couple days ago [4]).
To add to your comment, there's also RADKFILE/KRADFILE, which is used by a lot of Japanese dictionaries out there (including jisho.org), and also IDS (Ideographic Description Sequence) data: https://github.com/cjkvi/cjkvi-ids . The latter, I believe, is not meant for general lookup, but nonetheless can be quite informative, such as identifying semantic/phonetic components.
> First there is close to no easy to read content when you begin learning Japanese and there is demand for such thing.
If you know the alphabets (that is kana), you can try the easiest graded reader such as [1] and progressing from there. It assumes little to no grammar knowledge and comes with illustrations and narrated audio that you can follow along.
I am building a free Japanese learning website at https://xn--wgv71a119e.app . It serves as a creative medium to improve my design and development skills, as well as my Japanese.
My vision for the project is to give learners the basic foundation of vocabulary, kanji, and grammar and to expose them as early as possible to native content (something that I wish I did sooner). For that reason, I utilize various media such as tweets and YouTube videos to make the content more natural (i.e. not textbookish), relevant, and engaging.
The project is still far from completion. A few days ago, I shared the early version of kanji module (https://xn--wgv71a119e.app/漢字) to a reddit community. If you are interested in the details, please check the post below:
Technology-wise, I am building the website with Next.js and wrote all sort of scripts such as asset generation, dictionary, and parser in Go. Aside from no support for utf-8 route in Next.js (I had to hack few things to make it work), the development has been smooth and pleasant.
Inspired by this, I created a study/work Discord server that is focused on frontend design and development (arata.page/circle). Unlike the article in this thread, there are a few differences in our approach: first, the server doesn't enforce regular check-ins. Because the members are strangers from all over the places, we set our own schedule and do asnychronous chat during the break. Secondly, we tend to completely mute the input and output devices (some people like myself do a screenshare to keep them focus). This works alright for a tiny community like us.