@cwebber @emacsen I'm listening to the third episode of @librelounge and I'm impressed by how naturally and (visibly) effortlessly you are discussing topics like exclusion and depression. I'd definitely recommend listening to this episode to anyone, whether subject to exclusion or depression or not.

(I believe I've never come close to depression myself and I started sympathizing with the Free Software movement and culture because I've seen cool people do cool things 🙂 )

@sandro @npd Sorry my response to yours was a strawman because I thought your idea was good as I misunderstood it aside from one thing!

I'll have to re-read what you wrote, I'm happy for feedback on what I wrote even if it's not the same thing

I'll write up my proposal on the AP issue tracker anyway when I get some time to breathe

@thelovebug I thought I did but I can look again, I'm currently swamped but added it to my todo list

printer isn't working right for some documents for whatever reason so I print to pdf then open in the gimp and print the raster images

stress Show more

@therealraccoon I think there's a reference being made here I don't know about

@npd the mutable web is fragile and pieces of it go down and rot all the time

just once... just ONCE... i want to play a 3D platformer where the final boss is literally a camera

Anyway @garbados @zack and @freakazoid all wanted to read this when I wrote it up, so there you go.

I'm not sure how clear it is, I'd be curious for feedback.

Another, maybe overly nerdy way to put it is to look at Zooko's triangle and see that hashes of names are decentralized and globally unique, but not human meaningful. We need to bring back the human meaningful'ness mapping in two places: a place for devs to look it up (the git repo) and the keys for human readability on the document itself (brought by the context mapping)

This can be managed as a normal git repo for the project that cares about these terms. Obviously, the hashing mechanism / URN type has to be explicitly agreed upon by the group. But you don't have to "wait" on the group to agree that it's okay for you to "take over" this shortname.

- We have a git repository full of all the well known definitions
- Terms are stored in files like
Person-693bd494bd6d46773c100cd0a60b47ef7b29c962.txt
- There are three directories for terms:
--- stable/: terms that have been around for a while, have significant community uptake and fair understanding in this domain
--- wip/: terms that are "in development" in the community. The community is still "converging" on the exact definition and
functionality.
--- dustbin/: terms that didn't "make it"

Ok, so but how do people map from a hash to a term definition? Ie, how do people find and coordinate on the meaning of terms?

There are a couple of ways to do this; one might be that we actually hook it into a peer to peer CAS filesystem and there you go, you can get it. But that's too futuristic. There's a simpler route...

Of course we can put the context somewhere else so we don't need to inline it every time; how and where we should host contexts is a whole topic of its own (hint, content-addressing is actually also the ideal answer)

Show more
Octodon

Octodon is a nice general purpose instance. more