-

Thu, 25 Jul 2024 12:35:23 +0200

Streams

streams@fediversity.site

Giac El Vecio wrote the following post Thu, 25 Jul 2024 03:35:21 -0700
Another problem I keep having lately is that of images in posts originating in new versions of streams.
https://diversispiritus.net.br/cloud/giacelvecio/IMG_20240725_122942.jpg

@Giac El Vecio

show all 40 comments

Thu, 25 Jul 2024 22:14:45 +0200

Bill Statler

billstatler@forum.statler.ws

I am seeing this frequently too, but not always. I haven't figured out if there's a pattern.

Thu, 25 Jul 2024 23:06:09 +0200

Varanda

varanda@varanda.online

I believe I have never seen that.

Mon, 29 Jul 2024 02:18:37 +0200

Bill Statler

billstatler@forum.statler.ws

Okay, I found something. I'm looking at a flower photo posted privately by @Mike Macgirvin ?️ a few days ago.

In my stream, I can see the image in the post, and its URL is at fediversity.site:

https://fediversity.site/.well-known/apgateway/didxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/photo/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-1.jpg?token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&zid=billstatler%40forum.statler.ws

However, if I look at recent posts by Mike (on my instance), the image URL points at the cache on my instance, and the image is not displayed (returns a "403 Forbidden" error):

https://forum.statler.ws/ca/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx?url=https%3A%2F%2Ffediversity.site%2F.well-known%2Fapgateway%2Fdid%3Akey%3Axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx%2Fphoto%2Fxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-1.jpg%3Ftoken%3Dxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

If I enter this same image URL manually, but omit the "?" and everything following, I can see the image:
https://forum.statler.ws/ca/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

So, this brings up three questions:

I thought that private images were never cached, but it went into my cache.
Why is the image URL different (original vs cached), depending on where I am viewing the post on my own instance?
Why do I get "403 Forbidden" only when the cached-image URL contains the extra stuff at the end?

Let me know if I can provide any more data.

Mon, 29 Jul 2024 02:46:46 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

Will do.

Mon, 29 Jul 2024 09:32:46 +0200

By the way, is the new URL format with /.well-known/apgateway/did:key: the new standard and set in stone, or will it change again?

I'm asking because Hubzilla is completely incapable of handling anything with such a URL. Not only can't it search for and import any content from (streams) posted under such a URL, but it can't handle (streams) content with such a URL even if sent from (streams) to Hubzilla contacts. It's queued indefinitely because Hubzilla doesn't know how to handle it, and I can't exclude that it increasingly clogs up the queue worker.

If this is intended to be and stays the new standard, it must have caught Hubzilla off-guard.

I've started a forum thread about this already, but with zero reactions so far.

Mon, 29 Jul 2024 11:19:22 +0200

Giac El Vecio

giacelvecio@diversispiritus.net.br

but even here on streams I am having problems starting from these fairly recent changes in the code, and, in addition, serious problems in the server when I try to send for various activitypub people, while up until I think the version of July 9th everything was going smoothly, and given that some have not had the same problems as me, we are trying to understand with enormous difficulty how to solve it, one thing I know for sure is that here we still use php 8.1.

Mon, 29 Jul 2024 13:43:55 +0200

silverpill

silverpill@mitra.social

@billstatler @giacelvecio @streams The URL format is not set in stone, but if there is a bug on Hubzilla side it would be better to fix it (streams IDs look like valid URLs to me)

Also, are we interoperating now? This Note has a DID-secured proof and my server has successfully verified it @mikedev

Mon, 29 Jul 2024 14:10:41 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

If software doesn't know what to do with a gateway url, just treat it like any other ActivityPub URL. There's no special handling required. If it's a GET endpoint, fetch it. If it's a POST endpoint, post to it.

Mon, 29 Jul 2024 14:20:23 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

I think we're "mostly" interoperating.

At the moment, only brand new streams accounts have nomadic ActivityPub accounts. Pre-existing accounts have traditional ids, however some content will be using gateway resolvers before they fully transition. I've got a couple of fully nomadic accounts that I've been testing with. I've seen a couple of http-signature issues that I'm currently trying to resolve - where the legacy url was signed but the gateway url was verified. But those are edge cases; most stuff is working. I can see your stuff just fine.

Mon, 29 Jul 2024 22:18:04 +0200

At the moment, only brand new streams accounts have nomadic ActivityPub accounts. Pre-existing accounts have traditional ids, however some content will be using gateway resolvers before they fully transition.

Ah, that would account for part of it. I've created this account under 24.07.20, shortly before @elmussol installed the 24.07.20.1 hotfix. So I'm kind of an early adopter.

So I think I'll see how this plays out before pestering Mario and/or Harald into building parts of Hubzilla against something that may not even be finalised yet.

Tue, 30 Jul 2024 00:06:22 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

For Zot6/Nomad connections, only the content inks have changed. Remember we already have nomadic identity. What the recent work did for Zot/Nomad folks was to add nomadic content.

This content should be completely compatible - it's literally just a different url that points to the same place; so it's worth figuring out where the bug is and smashing it. Could be signature mismatch - there's a fix for that in the dev branch now.

But let's just say there's stuff going on in development land which changes the whole picture. Zot/Nomad is/are gone and it's ActivityPub from top to bottom. It will be a long while before this stabilises -- so don't hold your breath.

Tue, 30 Jul 2024 00:51:55 +0200

DerPepe (streams) ⁂ ⚝

derpepe@nomad.pepecyb.de

@Mike Macgirvin ?️

But let's just say there's stuff going on in development land which changes the whole picture. Zot/Nomad is/are gone and it's ActivityPub from top to bottom. It will be a long while before this stabilises -- so don't hold your breath.

Did I understand that correctly? (streams) is throwing zot/nomad overboard in the medium term and switching completely to AP?

Tue, 30 Jul 2024 00:59:07 +0200

Bill Statler

billstatler@forum.statler.ws

Bye-bye, Zot/Nomad!

So, will the "Enable ActivityPub protocol" channel setting become meaningless?

Tue, 30 Jul 2024 01:53:13 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

Semantics. "in development land" does not necessarily equal "streams". Likewise "throwing overboard" sounds a bit harsh. More like "retiring after many years of service" and passing the torch.

Tue, 30 Jul 2024 02:17:22 +0200

DerPepe (streams) ⁂ ⚝

derpepe@nomad.pepecyb.de

@Mike Macgirvin ?️

The ‘throw overboard’ was not meant in a bad way. ? That's so typical of my ‘Berliner Schnauze’... I can't deny my origins ? , even though Hungary is now my new home.

Tue, 30 Jul 2024 02:52:27 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

Right now I'm just doing a proof of concept. I haven't really figured out what to do if/when it actually works. But I thought it was worth sharing that it looks like it's probably going to work.

The things that won't work out of the box are (1) detailed delivery reports (we'll only be able to report whether it was accepted or rejected and/or still queued).

And (2) we probably won't be able to provide real-time sync of clones. Will probably end up with some endpoint that will fetch all the database changes on your channel since a specific timestamp - and a client process can pull these and sync as often as desired. Kind of like the content-importer does now.

Otherwise, you shouldn't see any difference in behaviour and it shouldn't really matter what protocol you use. The message payload is exactly the same.

Tue, 30 Jul 2024 03:30:34 +0200

Bill Statler

billstatler@forum.statler.ws

I have only checked a few posts, but it looks like the invisible-image bug has been squashed as of dev 75148b984. Cool! Thanks.

Tue, 30 Jul 2024 03:58:15 +0200

Varanda

varanda@varanda.online

I am curious. ;-)

Tue, 30 Jul 2024 04:19:21 +0200

silverpill

silverpill@mitra.social

@mikedev @giacelvecio My current account is not nomadic, but I've just sent a reply from a nomadic one, are you seeing it?

https://mitra.social/.well-known/apgateway/did

z6MknVmyPtQmD2SaGnqyGgTVEqfqkkJJnY3YVKBmbzSUNCcX/objects/0191016c-d98f-b294-92b9-b1b947a4c61c

Tue, 30 Jul 2024 05:02:28 +0200 zuletzt bearbeitet: Tue, 30 Jul 2024 05:02:56 +0200

Streams

streams@fediversity.site

The json looks fine and it validated, but was bounced for permissions. You're in a contained conversation owned by the streams group and is only commentable by members. It was sent to my channel (mikedev) but I won't accept it because it isn't my conversation and it wasn't added to the conversation by the owner.

Tue, 30 Jul 2024 10:15:54 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

Yeah, it will have to go. But it does mean I'll need to finish off the "block project" functionality. At some point we'll lose Mastodon to spammers and will need to jettison them.

Fri, 02 Aug 2024 05:43:45 +0200

silverpill

silverpill@mitra.social

@streams @giacelvecio I also tried to follow @jupiter_rowland but the inbox endpoint returned 403

Fri, 02 Aug 2024 08:42:44 +0200

So maybe your pre-nomadic main account and this fairly new nomadic (streams) channel of mine are incompatible in some ways.

For the record: I can see your comment just fine here on (streams), name, profile pic, Mitra being the source and all.

Fri, 02 Aug 2024 08:43:34 +0200

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@silverpill I've just commented on your comment from (streams). Just in case my comment doesn't arrive.

Fri, 02 Aug 2024 17:34:52 +0200

silverpill

silverpill@mitra.social

@jupiter_rowland I can see it, thanks.

@mikedev this is the URL of inbox where I'm sending Follow activity: https://streams.elsmussols.net/.well-known/apgateway/didz6Mkmc3YmgUu5jTyhc6YqC8VjnMwmFtdjFFA45MHTqyBFaA2/actor/inbox

Same result with Like activity, the server responds with 403

@giacelvecio @streams

Sat, 03 Aug 2024 11:11:36 +0200

Giac El Vecio

giacelvecio@diversispiritus.net.br

After the today update this part seems solved ?

If you have problems with pics try to update

Thu, 08 Aug 2024 20:12:51 +0200

silverpill

silverpill@mitra.social

@jupiter_rowland @mikedev By the way, this nomadic actor can be retrieved from my server too (it's cached there):

https://mitra.social/.well-known/apgateway/did

z6Mkmc3YmgUu5jTyhc6YqC8VjnMwmFtdjFFA45MHTqyBFaA2/actor

Per FEP-ef61 it is also a valid actor object, the location doesn't matter

Thu, 08 Aug 2024 20:19:08 +0200

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

Seriously, I think I kind of begin to like the way how Hubzilla inserts a key emoji (

) into the new ID addresses...

Mon, 19 Aug 2024 00:37:40 +0200

Papa Dragon

thomas@caselibre.fr

The problem is still present here. Only for a channel cloned elsewhere. With a non-cloned channel, everything works fine.

(website is running the latest Streams release, of course)

Mon, 19 Aug 2024 01:05:28 +0200 zuletzt bearbeitet: Mon, 19 Aug 2024 01:09:34 +0200

Giac El Vecio

giacelvecio@diversispiritus.net.br

I can see the other streams people pics now ,but having a clone, when I try to attach I still have problems yes

Mon, 19 Aug 2024 22:12:04 +0200

Papa Dragon

thomas@caselibre.fr

Not a critical issue for me, but still a bit annoying. I'll take a closer look after my holiday and if I have enough relevant logs, I'll open a ticket on Codeberg.

Mon, 19 Aug 2024 23:09:08 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

I just created a channel clone and posted an image from one clone instance and viewed it (locally) on the other. So clones are working, clone sync of files is working and clone sync of files with nomadic URLs seems to also be working. Is there anything else you can tell me about the image issue (?) because I feel like I'm missing something obvious.

Mon, 19 Aug 2024 23:35:30 +0200

Giac El Vecio

giacelvecio@diversispiritus.net.br

venturing hypotheses,

maybe because the clone is old while if it is new it has no problems?

Mon, 19 Aug 2024 23:43:54 +0200

Papa Dragon

thomas@caselibre.fr

Here's what happens when I try to attach an image to a post (just when getting the preview - where the image is missing)

2024-08-19T21:38:52Z:LOG_INFO:1f0e163e2f:network.php:93:http_status: .well-known/apgateway/did:key:z6MkjBBEC14Eeax4iXXXtf9TGFukqkh45m4FLPXXXwMujxgB/photo/e7e70b2e-7f02-4935-95da-2b67cb5e23e6-1.png?token=0dIUkCxeXXXSE3sK65TRCSDghsuUxCjRGF8qXXXgCAldiUY:404 Not found

Mon, 19 Aug 2024 23:51:27 +0200

Papa Dragon

thomas@caselibre.fr

And if I publish the post I get those two lines:

2024-08-19T21:44:20Z:LOG_INFO:1f0e163e2f:network.php:93:http_status: .well-known/apgateway/did:key:z6MkjBBEC14Eeax4iXXXtf9TGFukqkh45m4FLPXXXwMujxgB/photo/e7e70b2e-7f02-4935-95da-2b67cb5e23e6-1.png?token=SI0XXXSdy3tHgMnLwY0rmTvVBv1DX8on9XXXlkmhzb3V86h:404 Not found
2024-08-19T21:44:20Z:LOG_INFO:1f0e163e2f:network.php:93:http_status: .well-known/apgateway/did:key:z6MkjBBEC14Eeax4iXXXtf9TGFukqkh45m4FLPXXXwMujxgB/photo/e7e70b2e-7f02-4935-95da-2b67cb5e23e6-1.png?token=SI0XXXSdy3tHgMnLwY0rmTvVBv1DX8on9XXXlkmhzb3V86h:404 Not found

Also I get those on the clone:

2024-08-19T21:45:57Z:LOG_INFO:c47940f981:network.php:93:http_status: .well-known/x-nodeinfo2:404 Error
2024-08-19T21:45:57Z:LOG_INFO:43302bc923:network.php:93:http_status: .well-known/nodeinfo:404 Error

Mon, 19 Aug 2024 23:57:38 +0200

Papa Dragon

thomas@caselibre.fr

Oh, also, I have this in the nginx conf, I think it should be fine:

    # make sure webfinger and other well known services aren't blocked
   # by denying dot files and rewrite request to the front controller
   location ^~ /.well-known/ {
       allow all;
       if (!-e $request_filename) {
           rewrite ^(.*)$ /index.php?req=$1;
       }
   }

Tue, 20 Aug 2024 01:21:58 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

I think I see. The photo permissions change when you post a photo, but this permission change activity isn't synced. Will try and sort that out.

Tue, 20 Aug 2024 11:07:18 +0200

Papa Dragon

thomas@caselibre.fr

Still no luck with today's release update. Again I get the 404 error.

Here's a full log of what happens when I add an image in a post (not yet published) :
https://apps.caselibre.fr/privatebin/?ee432721442f1c73#8whq5JVzH1uoM9nKoMgDDZNFWZUDmx7MpmknLDdiRKRQ

I hope this helps.

Thu, 22 Aug 2024 11:32:58 +0200

Papa Dragon

thomas@caselibre.fr

Just ran a few tests. This problem only seems to exist for my older channels. The more recent ones are not affected.

Good news: my servers are not broken.
Bad news: could my older channels (including the one I'm using now) be broken?

@Mike Macgirvin ?️ if you have suggestions on where I should look to see where this could come from, I'll be glad to continue the search.

Thu, 22 Aug 2024 12:09:39 +0200

Mike Macgirvin ?️

mikedev@fediversity.site

What's happening is that you have two brand new identities. The /.well-known ... identity and also the did

identity. On top of your Nomad identity and Zot/6 identity and ActivityPub identity and your webfinger identity. There's only one of you, but we have to reconcile which identity is being used where. I've found and resolved most of the places where this needs to happen - but there are apparently one or two additional places remaining elusive.