-

Fri, 19 Jul 2019 08:51:39 -0300 última edição: Fri, 19 Jul 2019 12:26:33 -0300

Mario Vavti via Zotlabs|Hubzilla Development

mario@hub.somaton.com

Since we now redirect https://hub.tld/item/uuid to https://hub.tld/channel/channelname/?mid=b64_encoded_mid does anything speak against using https://hub.tld/item/uuid as plink instead of https://hub.tld/channel/channelname/?mid=b64_encoded_mid?

Asking because we have DB issues with too long plinks (more than 190 chars) and the https://hub.tld/item/uuid version would be significantly shorter...

!!zotlabs.org | Hubzilla Development

show all 5 comentários

Sat, 20 Jul 2019 20:25:10 -0300 última edição: Sat, 20 Jul 2019 20:25:04 -0300

M. Dent

dm42@hub.webgoeslocal.net

I ran into that a while ago as well, but wasn't in a place to think about a solution. I can't think of anything that should cause that to be a problem. I might suggest looking at the resource location independence code, though, to see if there's a way to make sure that the location independent data necessary to resolve the link if hub.tld is unavailable is somehow incorporated (I don't remember if it's all embedded in the uuid or not). That way Hubzilla by default could resolve it based on location independence, but non-location-independence-aware platforms can use the plink URL itself.

Sun, 21 Jul 2019 20:09:37 -0300

Alexandre Hannud Abdo

aleabdo@hubzilla.com.br

Hmm... I have on occasion used the mid to manually open a resource on another hub when the hub in the link is not available.

Mon, 22 Jul 2019 04:37:39 -0300

Mario Vavti

mario@hub.somaton.com

@Alexandre Hannud Abdo you should still be able to do this because https://hub.tld/item/uuid is the unencoded mid.

@M. Dent we could lookup if the item is available from its primary location before redirecting. If the primary is down we could lookup if the author has alternate locations we could redirect to. That would delay the redirect though since we would need to check if the primary location is intact first...

Mon, 22 Jul 2019 07:29:27 -0300 última edição: Mon, 22 Jul 2019 07:29:14 -0300

M. Dent

dm42@hub.webgoeslocal.net

Could we code the redirect as a JavaScript snippet so that the logic was handled on the client side? Send the list of author locations to the client and have the client cycle through?

Wed, 24 Jul 2019 17:19:29 -0300

El Dorado

mike@z.macgirvin.com

Send the list of author locations to the client and have the client cycle through?

Nomadic content is on the roadmap for Zot8 (works today, but not yet being used). It absolutely will not federate to other protocols.