#sebbuthere *was* a channel about thoses kind of question in freenode, that was #tatoeba. they still have a nice website/forum
#epochI keep finding bugs in stuff but I don't want to create an account on github again to report them
#epochso maybe I'll just make posts about them on my own website
#epochand if someone else wants to link to the bug report...
#sebbuyou could make a temp or new email, and make thoses accounts on big sites, and never check them except if you need a 2fa code or some other verification thing
#sebbuand keep a mostly empty github account, and only make bug report from the website (not even with git installed on your pc)
#GWGI was here for private webmentions, autoauth, etc... Ticket Auth is the simplest idea I've seen
#GWGThat's why I wanted to map out a plan to smooth out the edges and start some better implementations
#capjamesgI am unsure why but I have found the spec a bit hard to understand.
#capjamesgI think more supporting materials would be helpful.
#GWG[capjamesg]: I've unofficially edited the text, so that could be me. But the issue is that people expect things to be in scope that aren't usually
#sknebelone could also say that the issue is that the spec doesn't cover things you need for a practical application ;)
#GWGFor example, it doesn't say how you as a consumer might ask for a ticket... because asking is out of scope. I believe one implementation sent one to anyone who had an endpoint
#GWGMy proposal is just having a brief discussion, agree to work on some implementations and test together, then iterate.
#sknebelyeah. not convinced going through the CG isn't more distraction than help, but yes, group effort certainly helps with experimenting
#GWGsknebel: I am willing to discuss it in any forum
#GWGIncluding here to identify what we are working on collectively.
#GWGIn my opinion, it is the sending/redeeming of tickets and their usage. Requesting one, save any debugging solution we put in for testing, should be out of scope as well as how/what uses the token once redeemed... once we get the ticket flow tested we can discuss more around the periphery.
#capjamesgsknebel I made the Issue just so other people who may be interested in private posts can see we're working on it.
#capjamesgsknebel "figuring out what tokens are valid for," can you clarify?
#sknebelright now there is only one url given, does the token work for other urls? which ones? (bunch about that in questions section on the page already)
#sknebelalso "how do tokens get from the endpoint to the apps that want to use them"
#rubenwardyI can't seem to log into telegraph, just says " The authorization endpoint for the returned profile URL (https://rubenwardy.com/) did not match the authorization endpoint used to begin the login. "
monoob, AramZS, geoffo and monoob7 joined the channel
#[tantek]rubenwardy++ for a well-written and thoughtful post. appreciate the sharing of experiences good & bad and hope we can use that to improve docs & tools
#Loqirubenwardy has 6 karma in this channel over the last year (7 in all channels)
#[tantek]rubenwardy, I fear the answers to your authorship questions here (in chat) may have been given from a plumbing perspective rather than a publishing perspective, and I'd like to fix that.
#[tantek]there's a very unfortunate webdev habit of providing plumbing-centric answers to publishing-centric questions. two very experienced members of this community just did that exact thing in #microformats channel recently.
#rubenwardyWhat do you mean by plumbing Vs publishing?
#[tantek]publishing is what you are doing with your blog
#[tantek]plumbing is what tools (like validators) implement to consume things
#[tantek]they are two very different perspectives with very different use-cases, and thus very different approaches to solutions
[snarfed], ajr, eitilt and kleb joined the channel
#GWG[capjamesg]: When might you want to sync chat?
#[capjamesg]Probably not this week. I have a lot already on my metaphorical plate. Next week?
#GWG[capjamesg]: No rush. We've been waiting for a while to do it
#[tantek][snarfed] literally all of my early POSSE work was figuring out how to take relatively "rich" post types and "downscale" them into plain text notes on Twitter, then limited to ~117 characters (leaving space for original post permalink in the 140)
#LoqiText-first design refers to the practice of designing information and UIs so they are readable/usable/actionable at least as basic plain text https://indieweb.org/plain_text_design
#[tantek]so in the specific example of: "eg the fediverse, Bluesky, and Nostr don't understand bookmarks (among others), we can't yet POSSE them there, but we can happily post them on our own sites" (as [snarfed] noted in #indieweb earlier), the answer is to allow cross-posting of bookmarks to those other destinations with the plain text equivalent of a bookmark post
#[snarfed]yes! I'm definitely aware of all of your text-first design work. it's awesome!
#[snarfed]I love that for people to choose on their own sites, but I was reluctant to lean far into it in Bridgy classic, since it has more potential to surprise users if they don't expect it
#LoqigRegor has 26 karma in this channel over the last year (80 in all channels)
#[manton]Hey ActivityPub nerds… 🙂 So Mastodon recently added “Translate” links to posts that (I assume) don’t have a language set. It adds a lot of clutter because I don’t need to translate from English to English. I’m finally looking into this so I can update http://Micro.blog to spit out whatever JSON Mastodon wants.
#[manton]From what I can tell, the only language set is using “contentMap” with “en” for the content… But that means duplicate the content text in every single JSON. Seems bloated. Anyone have experience with this? Maybe I’m missing something?
#[manton]I’m seeing the same “Translate” links on Bridgy Fed posts too.
#sknebel[manton]: is that whats done in the messages your server gets?
#[manton][sknebel] Yes, I’m looking at ActivityPub JSON from other Mastodon servers and it looks like this:
#[manton]Ah, thanks. I was looking through activitystreams-vocabulary which only mentions contentMap.
#[manton]I actually discard the @context values in my logging so I’m not totally sure what Mastodon is putting there. Will have to dig deeper.
#[manton]When I request a post with Accept: activitypub, though, there’s no language in @context.
superkuh joined the channel
#[tantek][snarfed] agreed with keep Bridgy Publish simple! The special Bridgy markup makes sense. Another standards based way could be plain text p-summary markup.
bterry joined the channel
#[tantek]we have a long running thread about using p-summary for plain text fallback behavior in general, so I wonder if that's a good signal for Bridgy Publish to use on "unknown" post types as an explicit fallback
#gRegorI've tried p-summary with BF before and I think opened a github issue. I think the main thing was Mastodon (or AS?) use of "summary" as the spoiler tag
#Loqi[preview] [gRegorLove] #332 Idea: fallback to summary for other post types?
#[KevinMarks]That's a mastodon quirk. AS name,summary,content match the microformats meanings, because we converged them in SocialWG
#gRegorYeah, seems like it would be ok for a bridge to use p-summary as fallback for content
#[tantek]right, specifically as fallback for content for post types unrecognized by the destination
#[tantek]not suggesting any use of Bridgy Fed to send p-summary -> Mastodon AP "summary", because that would be a disaster due to the content warning overloading 😕