tantek!tell snarfed re: "still not signed up for bridgy github 😂" - yeah I could sense that I would immediately get sucked into wanting to fully implement it, so I think that's going to be the weekend project. very excited about this.
[eddie]!tell aaronpk Are API Tokens restricted/linked to specific channels in Aperture? I’m looking at the database but I don’t see anything that specifically links a source token to a channel
LoqiIt looks like we don't have a page for "difference" yet. Would you like to create it? (Or just say "difference is ____", a sentence describing the term)
aaronpksource tokens (called api key in the ui) are for writing content into sources, and it's expected that those sources will only be mapped to one channel, but technically that is not a requirement
Loqisnarfed: tantek left you a message 3 hours, 13 minutes ago: re: "still not signed up for bridgy github 😂" - yeah I could sense that I would immediately get sucked into wanting to fully implement it, so I think that's going to be the weekend project. very excited about this.
GWGGithub issue filing in Bridgy is a good reason for me to support issues, isn't it?
AngeloGladding, tantek, KartikPrabhu, [kevinmarks], KevinMarks, KevinMarks_, ScalaWilliam, barpthewire, Kyle-K and leg joined the channel; Kyle-K left the channel
Zegnat!tell jeremycherfas I was able to create a bookmark on Known through the Known API (not Micropub) that has a custom title and description. Happy to exchange code.
sknebelan interesting point is "issue" vs "the post creating an issue" - e.g. an issue has state like open/closed, current tags, ... that can change through others and over time, kind of as a result of a sequence of posts
Loqi[jeremycherfas]: Zegnat left you a message 56 minutes ago: I was able to create a bookmark on Known through the Known API (not Micropub) that has a custom title and description. Happy to exchange code.