pleroma.debian.social

pleroma.debian.social

Of these, what is the coolest naming scheme?

@evan
Either of the middle ones are good for me, but the URL-shaped one is most familiarily pleasing.

@silvermoon82 which is that? The XMPP one?

@evan
I think so, user@domain/resource. That's close enough to user@domain/path to be a partial URL.

@evan

It DOES depend on what the scheme means.

To me:

"@" reads "at" and means, essentially, "belongs to" in a hierarchy, implying there is a M:1 relationship.

"/" is unpronounced, and means a subdivision (as per filesystem folder use), so implies 1:M relationship - a fan out.

Intuitively, I expect "user@domain" to be a proxy for a person. But "user@domain/resource" is something that person owns. Perhaps a software they've deployed? If that's the intent, then that seem intuitive to me.

Of course, I likely have computer/programmer brain, so IDK when it comes to the general public. gonzo

@evan Wow, I haven't thought about Vines in decades! Not that I voted for it (or any of them, since I don't have a strong or useful opinion).

@mweston if you recognize a Streettalk address, you are obligated to vote.

@evan my bias towards came through in my vote, but that X.500 thing looked pretty intriguing too. I think I've seen something like that somewhere...maybe ?

@badrihippo either LDAP or SSL certificates, I'd guess.

@evan I wouldn't have if you hadn't said what the four choices were. X.500 was slightly more accessible in my memory.

I was at Convergent Technologies when they produced the Server PC based on the then hottest CPU in town, the 386 (Intel used benchmarks run on it in ads). And Convergent produced what I think was just a port of VINES running on their Unix on the Server PC.

See https://ia904504.us.archive.org/3/items/bitsavers_convergentxchangeVinesSWProductSpecJun87_618683/CTIX_PC_Exchange_-_Vines_SW_-_Product_Spec_Jun87_text.pdf

I mostly worked on the Server PC BIOS, modified from Phoenix code. And debugging issues with DOS programs running on it, since saying the Server PC was IBM compatible was a marketing thing that probably didn't really matter in the end. I would have been in my 20s, in my second post college job.

@mweston I want to remind you of how low the stakes are in this poll

@evan @badrihippo Both, yes.

@evan uucp mail routing is even cooler

"User barbox!user would generally publish their UUCP email address in a form such as …!bigsite!foovax!barbox!user. "

https://en.wikipedia.org/wiki/UUCP

@hakona I'm saving that for a future poll!

@evan This was fun, and you made me look up Banyan Vines. Amazingly, I've used all of the other 3 and recognized them

Next time, I would love to see my two favorite email options:

user%realhost@relayhost.com

node1!node2!ucbvax!decwrl!user

And a Fidonet bonus: John Goerzen@1:291/51

@jgoerzen you got it

@jgoerzen also, big props for knowing the arch/baz/bzr format. It's one of my faves.

@evan Oh yes, I was a fan of distributed version control from the very early days. Arch, tla, and baz -- then in about 2005 I migrated to darcs, writing https://github.com/jgoerzen/arch2darcs to convert a repo's entire history.

@jgoerzen darcs was the first version control system I used for Laconica (now GNU Social). I really liked darcs!

Thank you everyone! I find this topic kind of interesting. I have a nostalgic fondness for Streettalk addresses; I remember scrolling through hundreds of them in a company directory, learning about the physical and organizational topology from the naming structure.

@evan
I have similarly fond memories of running `traceroute` in the 1990s—back when networks were much more open—being able to visualize how the packets actually got from my desktop to some server in Finland

@evan
My eyes! Take take the DN away!
replies
0
announces
0
likes
1