User profile about mycorrhiza HOT 6 OPEN

Another idea I have is to introduce user hyphae as a separate hypha kind, along with textual hyphae, hyphae with attachments (+ optional description) and forthcoming alias hyphae.

Additional file type with extension .mycouser can be introduced. I have no idea why would we need such a file. Drop users.json file in favor of such .mycouser files? Why? Store links to profiles on other sites? Why?

By the way, there is no such concept as hypha kind in Mycorrhiza code base. Introducing it means making a big and a pleasant refactoring.

I don't expect everyone to agree with this message. Please discuss.

from mycorrhiza.

Sadly, we can't store users' passwords in .mycouser files, so we'll have to have some storage for them anyway. Otherwise, sounds like a good idea to me.

from mycorrhiza.

Sadly, we can't store users' passwords in .mycouser files

Passwords are to blame, right? Damn these passwords. Bring back the days before they became a thing...

from mycorrhiza.

a simple "username" field on edit pages when

from mycorrhiza.

Here is a sudden advantage of storing users as hyphae in git: new users appear in history!

This is cool imho.

from mycorrhiza.

Identicons

While checking out Syncthing, I noticed cool 5 by 5 pixel monochrome images.

Many websites have similar things, but I liked this implementation more because of the lack of colors.

Turns out, this pattern is called identicon.

And so I thought, why not have them? A little SVG image beside every link to a profile, isn't it cool?

You can take a look at Syncthing's implementation of identicons, but it is of little interest.

from mycorrhiza.