Nick Doty @npd@octodon.social

@qubyte looks cool, thanks!

@qubyte this Glitch link you posted in GitHub doesn't work for me:
https://glitch.com/edit/#!/mastodon-webmention-relay?path=README.md

Is it possible you didn't finish publishing the glitch yet? I'm definitely interested in it.

@aparrish yeah, that's such an important way to think about it! And maybe the monthly patronage model encourages that, since you aren't writing code transactionally.

If you had a Liberapay, I'd definitely support it.

@aparrish would being paid for your work on open source make you more or less likely to enjoy doing it? There's a danger of crowding out incentives.

@esp @gargron well, I think it's awesome for people on either (sending/receiving) side that *want* to engage in conversation.

Bloggers that don't want a conversation won't have any interest in that functionality either, although the side-effects for them are pretty miniscule.

@ajroach42 @gargron
yeah, I had the same thought
https://github.com/tootsuite/mastodon/issues/6074#issuecomment-378446786
it marks it as an explicit reply/mention and not just a passing link.

@esp @gargron yeah, I see how it's a privacy issue, even for toots that are explicitly public.

I was just providing the positive use in case you weren't aware of it. I'd like to be able to reply to bloggers or micro.blog folks from my account here and have some chance of their seeing it. Maybe if it were framed as a reply (like with an @ preceding the link), that would be more consistent with user expectations.

@esp @gargron thanks for the reply, I hadn't realized the concern.

To your question, I think an average user who toots publicly about someone's blog post would benefit from notifying them so that there can be a better chance of a conversation with the author, or with other people reading the blog post.

@gargron I'm curious why some people are opposed in the straw poll, since to me it seems like a great way to add interoperability and increase the visibility of Mastodon instances. Is there a GitHub issues where this is being discussed?

@gargron maybe refer to TLS rather than SSL.

Generally looks good to me, and an improvement. Thanks for working on this.

@mala I wonder if the Signed Exchanges work at IETF would help with these microCDNs. Sites can provide signed versions of their sites for easy caching and delivery by others, either the Google AMP cache or maybe a small CDN device delivered to a rural area.

@ajroach42 @Brennan when I last looked into this, the Amtrak towing rate seemed surprisingly reasonable. You don't have to do it in the super luxury way, although of course WSJ is more interested in reporting on that.

I like the idea of cross-country hackathons where we attach a private car to an Amtrak train.

@bortzmeyer reading this now, I think 2.3.4 specifically does *not* claim that operators have such a right. Instead, it notes IAB guidance (RFC8165) that suggests host-based alternatives to network-based metadata insertion.

@bortzmeyer yeah, I wonder if that would work for IETF or W3C groups and if the staff/tools teams would be willing to do it. I think the issue is that groups aren't just using git (decentralized), but also pull requests, issue lists, wiki pages, gh-pages-generated sites, etc.

W3C has produced tools that work with the GitHub repos to make sure content is backed up elsewhere and summarized to mailing lists.

@bortzmeyer I think the largest single group in her metrics was large companies (and I would be confident that it's the majority of the funds), but I'm not sure it was the majority of member organizations.

@bortzmeyer I felt like I didn't have time to get into that during my short presentation, but I absolutely agree that it's a concern. Email participation has the advantage of being a federated open protocol (no particular account needed), but access/usability is important and some people report email/mailto being more confusing to them than Github issue lists.

@cwebber I think it's a very valuable project to iterate on codes of conduct, describe the important details of implementation and propose other community safety processes.

Nonetheless, it's hard to read this post as any of that; the author says that a Code of Conduct document alone won't solve all problems (true!), therefore, CoCs are preventing an unspecified better alternative (citation-needed!).

@CobaltVelvet when I just logged in on octodon, the 2fa code page was in Chinese, while the rest of the login was en-us, as I'd expected.

WIP: the IETF's working groups, as seen/connected through mailing list traffic
#ietf #infoviz #gephi

@brennen those are more than quibbles, though! "We should never build a tall building" is not just an old-fashioned, unworkable architectural preference, but also the motivation that drives both sprawl and the urban housing crises we face.

Worse, I think, the tone is apparently just extra insulting to try to sound like critique. I think there's an important, interesting history to explain brutalism and this papers over it.