freamon
@freamon@lemmy.world
- Comment on 5 days ago:
Just come across this myself.
Long-running fediverse instances will likely have old copies of established aussie.zone actors, but federation will be broke for newer instances and/or newer actors.
Verifiable by doing something like:
WORKS: curl --header 'accept: application/activity+json' https://reddthat.com/u/lodion DOESN'T WORK: curl --header 'accept: application/activity+json' https://aussie.zone/u/lodion
I chose reddthat.com because it seems like it has similar protection, but allows for AP requests. (other instances use non-CF solutions, but I imagine they’ve had to make similar tweaks).
It’s been a couple of days, so it might be worth some pings:
@admin@aussie.zone
@lodion@aussie.zone
- Comment on Can’t see my video file sizes on PeerTube. 1 week ago:
You can get a rough idea of how big each video is via an activitypub query for each video. For example:
curl --header 'accept: application/activity+json' https://peertube.wtf/w/mhghLtY5dkLguNq5oFB2Ut | jq .Buried in there is a
urlentry, and buried in some of those is atagentry and buried in some of those are details for the size of the video and audio for each upload.Peertube’s video channels have an outbox (similar to how Lemmy’s communities do, but not limited to 50 entries), so you can step through that to find the relevant info for everything in your channel.
Doing that for your channel, I got:
Shitpost #2 video: 482 x 480: 2.27 MB audio: 0.3 MB Shitpost #1 video: 480 x 480: 8.69 MB audio: 0.94 MB Will this replace the internet? video: 1080 x 1920: 19.26 MB video: 720 x 1280: 11.9 MB video: 360 x 640: 5.23 MB audio: 16.75 MB Cat video: 1920 x 1080: 7.77 MB video: 1280 x 720: 2.14 MB video: 640 x 360: 0.41 MB audio: 0.23 MB
If you assume that the size of the audio is ignored, and that lower resolutions are transcoded as requested, and add the sizes for the highest resolutions together, you get 2.27 + 8.69 + 19.26 + 7.77 = 37.99 (which is the 38 MB visible in your screenshot).
The information is available, but it’s a pain in the arse to get, so it’s probably annoying for PeerTube themselves to show (a brief look suggests that the API response doesn’t provide it, so there’s nothing for the web frontend to display). It’s also possible that they may drop the higher resolutions for videos with low engagement, so the size of each upload isn’t static, which adds an extra complication.
- Comment on 2 weeks ago:
Not really.
Gup.pe groups were genuine ActivityPub Groups, like Lemmy communities, whereas these ‘FediGroup’ things are just Mastodon bots. They’re a ‘Service’, aka the automated version of a ‘Person’, so they’re no use to anyone on platforms (like Lemmy) that can only follow Groups.
The most similar recent thing to gup.pe is ovo.st
Compare:
curl --header 'accept: application/activity+json' https://lemmy.world/c/fediverse | jq -r .type => Group curl --header 'accept: application/activity+json' https://ovo.st/club/askfedi | jq -r .type => Group with curl --header 'accept: application/activity+json' https://fedigroups.social/@audiofiction | jq -r .type => Service