[snarfed][manton] out of curiosity, micro.blog currently federates to the fediverse, but syndicates to bluesky. do you know if you'll switch it to federate to bluesky instead once they enable that?
[manton][snarfed] I don’t know yet. I’m going to at least explore Bluesky federation. I’m not really sure if I can reconcile all the different worlds together, though.
[snarfed]we'd probably want to think through the UX of default-on federation. eg for AP, afaik there's no alternative AP-style frontend to micro.blog accounts, it's just micro.blog, so it's really whether fediverse people can follow and interact with micro.blog people by default, right?
[manton]There’s also a 3rd option that I’ve considered (1st being just syndicate, 2nd being full Bluesky federation): allow signing in to a Bluesky account from within Micro.blog, so Micro.blog becomes a kind of super-client that can interface with multiple services. I don’t think that’s the right solution, but it would separate things a little.
[manton]I’ll probably add federation for my own account (if I can technically) and see if I like it. If I do, then we can decide what to do. If I don’t, we’ll just syndicate.
[snarfed]heads up though, as far as we can tell, implementing ATP federation is not easy, definitely harder than eg implementing AP. the MST and repo chain are fairly deep CS/eng
[snarfed][manton] good q's. ATP is definitely web-y in spirit, arguably more than AP itself, but modern web-y. eg latest info we have is that ATP federation will use websockets too, not plain HTTP
[manton][snarfed] I think my concern is that too much of the service might be hidden away instead of on the web. That is also a concern for parts of AP, but most pages and feeds in Mastodon are public. Already we’re seeing Bluesky URLs inaccessible unless you’re signed in.
[snarfed]ah, understood. user-facing web frontends and other clients aren't really part of the protocol. the API they use to talk to PDSes, yes, but those serve JSON, not human-readable HTML
[snarfed]that one is interesting! but pretty narrow, just lets you use a Mastodon client app with your own Bluesky account. it isn't an actual bridge between the two services, despite the name
[tantek]also capjamesg, well done for being the source of multiple TLD additions to the CASSIS auto_link_re (regular expression), so far .coffee and I suspect soon .link if/when I implement auto-link-wrapping of bsky.app links with bsky.link
[tantek]what will be more challenging is figuring out the link vs embed semantic, like when someone puts a bsky.app link in a plain text note, is the intent/desire "merely" for a public-usable hyperlink? or do they intend a link-preview-like/quote-like embed?
[tantek]right now, I do auto-embedding for things that "make more sense" embedded than linked, like images & video (including special-casing youtube and vimeo video permalinks by detecting them)
[tantek]the brackets around something look like you're framing it, which evokes a visual embedding, so that both "looks right" in plain text, and is an easy syntax to remember
[tantek]yeah the markdown scrawl of [ ] ( ) { } has no meaning behind the characters, they're arbitrary and hard to remember and look like line-noise in plain text
[tantek]so, adding alt text to a [URL] frame would be followed by parenthetical text, which is "normal" punctuation that fits the alt semantic quite well
[tantek]aaronpk, what I don't like about "text"(link) is two things: 1. it's overloading plain text quotation marks to mean something other than quoted text, which "looks" wrong when reading in plain text, and 2. the link isn't really a "paranthetical" to the link text
[tantek]and since text hyperlinks are traditionally underlined, something like `_link_text_<URL>` or even with a space for readability `_link_text_ <URL>` would work fine
[tantek]"work" as in makes sense / is readable *both* in plain text (i.e. the punctuation doesn't look like random gibberish the way the bang-bracket nonsense does in markdown), and is a clearly explicit enough pattern that hyperlinking it makes sense too
Loqi[preview] [Tantek Çelik] One of the fun things about #IndieWeb notes & replies is that how we post is actively evolving! Like how should we @ someone?
#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.
Now, some have a domain, or an @...
bkilI support @-mentions in my chat app by just typing @nick as you name your own followers with your own nick shorthand anyway and disambiguate their full profile URL within your feed.
[snarfed]agreed, I don't love discord either. fwiw the company originally set up the developer community chat on matrix. community people themselves later made the discord and largely migrated there 😐
[tantek]a-ha, looks like aria-label is the preferred attribute for providing "alt" text for an iframe (better than "title" which has other visual presentation effects)
[KevinMarks] There's an analogy with the ActivityPub server API and the mastodon client API there
@leo60228 ↩️ IndieAuth is the closest thing to a solution but it assumes every user has a personal website which is probably not true (twitter.com/_/status/1653552448345128962)
@vanzasetia I write a blog post to help you implement Webmention on your website.
#webmention #indieweb
https://vanzasetia.site/blog/beginner-guides-for-applying-webmention/ (twitter.com/_/status/1653681605104529409)
[snarfed] hah, I think it's mostly a non-technical problem, as you've described, which I'm less equipped to handle for online communities. https://snarfed.org/2023-04-15_im-not-eating-my-own-dog-food
[manton] There’s also a 3rd option that I’ve considered (1st being just syndicate, 2nd being full Bluesky federation): allow signing in to a Bluesky account from within Micro.blog, so Micro.blog becomes a kind of super-client that can interface with multiple services. I don’t think that’s the right solution, but it would separate things a little.
capjamesg aaronpk Have you seen this error before? https://breakfastand.coffee/
gRegor Maybe interesting for Mastodon -> Bluesky bridging: https://github.com/videah/skybridge
Loqi It looks like we don't have a page for "skeet" yet. Would you like to create it? (Or just say "skeet is ____", a sentence describing the term)
[tantek] why not bleet? as in https://enwp.org/bleet