Loqicweiske: [snarfed] left you a message 2 weeks, 4 days ago: hi! just fyi, your search currently 500s on any search that ends with the / character, eg https://indiechat.search.cweiske.de/?q=xyz/ . hope it's an easy fix!
[eddie]!tell jacky so far there hasn't been a need for a "request info about this channel" action because the request for ALL the channels isn't that big and it is common for Microsub Clients to cache the Channel List, so the data is typically always available once you login to a reader. Is there a specific use case that you've run into where you need that ability?
[timothy_chamber, [schmarty], [kimberlyhirsh], deathrow1, jeremych_, jackjamieson, BenLubar, [renem], [eddie], [snarfed] and gRegorLove joined the channel
jacky[eddie]: yeah for my reader, the act of fetching all of the known channels is very decoupled from rendering each individual channel (it's not only for microsub).
Loqijacky: [eddie] left you a message 3 hours, 27 minutes ago: so far there hasn't been a need for a "request info about this channel" action because the request for ALL the channels isn't that big and it is common for Microsub Clients to cache the Channel List, so the data is typically always available once you login to a reader. Is there a specific use case that you've run into where you need that ability?
LoqiJoin the #indieweb discussions via the web, Slack, IRC, or Matrix interfaces now with additional channels for dev, wordpress, and meta specific chat! https://indieweb.org/discuss
LoqiJoin the #indieweb discussions via the web, Slack, IRC, or Matrix interfaces now with additional channels for dev, wordpress, and meta specific chat! https://indieweb.org/channels
[snarfed][renem] moving here. i don't actually see any AP `Follow` requests to bridgy fed for you. only one request to `/renem.net/inbox`, a `GET`, i'm guessing your interactive one.
[renem][snarfed] yes, I tried to follow it from my Mastodon account on Mastodon.host instance. Could this be instance specific? Or maybe a caching thing from instance because my redirects weren’t working on the first few attempts and that’s why the instance still sends the follow request to a wrong URL?
[snarfed]maybe! not sure. all i know is your site seems to be redirecting right, and bridgy fed is working ok with it, but it never your follow request, but it got mine
[renem]Tried it again, and still the same issue. Maybe I’ve to wait a day or so and get the details about that. After a refresh the “follow” button switches to the “waiting for approval”.
[renem]But thanks for checking that it’s working, I still have issues with the ./well-known/host-meta* redirects because they end in 404 and I don’t know why but the Webfinger thing is right 😀
BenLubar[snarfed]: I think there might be something related to the dots in the names because I remember having to change it for ravenvale.lubar.me's gw2 actors
[snarfed]BenLubar maybe! but the domain-based usernames like `@renem.net@renem.net` are working for other users, and for me following this one, just not for renem's user on mastodon.host, so that seems to be the broken part here
[snarfed]i haven't followed mastodon changes closely. but again, using my mastodon account on mastodon.technology, i can follow `@renem.net@renem.net` successfully, and it's running the exact same version of mastodon (2.9.2) as mastodon.host, so mastodon itself is ok. something is unhappy on mastodon.host specifically
[benatwork], [KevinMarks], [cjwillcock] and KartikPrabhu joined the channel