Christopher Lemmer Webber @cwebber@octodon.social

@bhaugen pump.io isn't speaking the activitypub api yet, but it's close to doing so

pump.io's "pump api" is what the activitypub api was derived from, but they aren't directly compatible

So.... soon, I hope!

@cbaines I mean, the broad area where such names most often appear, that is

@cbaines well its colonialist derived name is "new england" I guess ;)

We're in Easthampton! Arrived last night, actually...

@deadsuperhero @notclacke @schmittlauch yeah I get that, and people are fairly familiar with email-like ids. I'm not arguing against clients supporting that for composition of addressing anyway, but it does bother me that Mastodon uses Webfinger for some sources of information where it shouldn't matter for protocol'y things

I think that could hold back some exciting future things if it remains. But fortunately my suspicion is that it won't be hard for mastodon to evolve there.

@gargron @dansup @nightpool I personally hate markdown kind of but that's not relevant to this ;)

@gargron @dansup @nightpool various pump.io clients have dynamic completion of the username but use markdown in composition... rich-text rendering, but not rich-text editors

@nightpool http(s) has problems with mutability all around anyway :)

@nightpool what problems of mutability?

@dansup @nightpool You could absolutely have a Mastodon-like interface without Webfinger btw... type @, and it brings up a list of possible recipients which might not even be the webfinger addresses but people who match this in their name who are in your "addressbook"... mastodon already does this mostly. If I type "@karen" I can complete @aldeka even though she has a different username. Pump.io clients use this to select the user's id, but link with their display name as the link text

@dansup @nightpool Or rather, was pushing back against it being a *requirement* (not against implementations optionally supporting it)

@dansup @nightpool Well, Webfinger isn't specifically OStatus related, but yeah that's why Mastodon has it.

Evan Prodromou, who I think was responsible for Webfinger in OStatus, was one of the bigger voices pushing back against it appearing in ActivityPub, saying there's no need for it in a modern federated system IIRC from the SocialWG calls

@nightpool @notclacke @schmittlauch I understand the frustration with http and https. Have you ever seen Tim Berners-Lee's "Web Security - TLS Everywhere, not https: URIs"?

https://www.w3.org/DesignIssues/Security-NotTheS.html

His argument is, of course we should have a cryptographic layer, but we shouldn't have two different uri schemes for the same resource served as unencrypted/encrypted... instead, there should be one uri scheme, and the encryption selection bit should be a protocol negotiation concern. I 100% agree.

in PA and scenery is currently gorgeous

@notclacke @nightpool @schmittlauch Yes, I suspect/hope as the AP network grows, reliance on webfinger will decrease, including its current use in role of what shouldn't really apply for some federation stuff

@nightpool If you're reading that as "oh, that means I could use this to write a roguelike that just has different chaos implementations for graphical vs command line" you're completely right

@nightpool I liked big-bang except its extreme slowness and some weird things like using strings to represent what should have been characters and etc.

What's really cool about lux is it takes the core idea of a functional game engine like big-bang provides but abstracts it a bit. You can provide multiple "chaos" layers, which are really the canvas'y type layer for rendering. The default one uses the racket draw library, but there's also mode-lambda (SNES-like engine) and raart (ansi art)

@LWFlouisa I think maybe the answer is more opt-in social communities that are self-governed rather than public-by-default spaces may help?