Continue reading on Unthread

@airglow.run @semble.so I'm not sure anymore if that might be an Airglow or Semble problem... Or even both... So I have an automation that fetches the stars I give on Tangled repositories, builds the Tangled URL for that repository (permalink), creates a Semble card, and adds it to my collection for atproto repositories. It worked just fine before Tangled changed the lexicon for stars and the composition of the permalink for repos. I edited my automation according to those changes, but since then, I noticed the data is mostly correctly created into my account repository (the only wrong part I'll address at the end, probably an Airglow bug), but the card never shows up on my Semble profile or Semble Collection. My Semble Profile: https://semble.so/profile/did:plc:fip3nyk6tjo3senpq4ei2cxw My Semble Collection: https://semble.so/profile/did:plc:fip3nyk6tjo3senpq4ei2cxw/collections/3meymyrbuxn2q My Airglow automation: https://airglow.run/u/vicwalker.dev.br/3ml5ixicbos22 Practical example from today: • Tangled Star: at://did:plc:fip3nyk6tjo3senpq4ei2cxw/sh.tangled.feed.star/3mm7hgbvd5222 • Semble card created: at://did:plc:fip3nyk6tjo3senpq4ei2cxw/network.cosmik.card/3mm7hgda7ma2i • Record adding the card to the collection: at://did:plc:fip3nyk6tjo3senpq4ei2cxw/network.cosmik.collectionLink/3mm7hgdb4i52p -- About the likely Airglow bug. My automation was designed to build the Tangled repository permalink, which is currently composed like: https://tangled.org/[repository DID] The automation fetches the repository DID from my star record, nothing complex, but if you see the Semble card created by the automation, you can see the URL saved is not the same, it's using the regular URL: https://tangled.org/[owner.handle]/[repository name] Since both the owner's handle and the repository name can change anytime and break the card link (it already happened before), I really wanted to avoid not using permalinks. If I manually create the Semble card using the permalink, it works just fine without changing the URL by itself, so that makes me believe it's not a Semble bug, but Airglow's.