Already submitted to this community, a few minutes before yours, by the original poster: https://lemmy.ca/post/61609680
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
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 url entry, and buried in some of those is a tag entry 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.
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 https://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
It's mostly annoying me because it's affecting federation - not just the ability for new instances to backfill content, but for established instances to even be able to fully resolve a new post's details before the author nukes themselves. For example, the previous post (titled "Paranoia") isn't available on lemmy.ml or lemmy.dbzer0 because they would have been a few seconds "too late" to fetch the details for the author.
@lawrence@lemmy.world - if you'd like another mod to help out in the short term, I'm happy to volunteer. I realise people in the comments are being a bit defeatist about the ability to reckon with this problem, but whoever this person is should at least have to do a bit more work than they're currently doing.
The code that OP has linked to is part of a convenience function for admins to add content to their new instances. It can query individual remote instances (e.g. lemmy.world), or it can query lemmyverse.net, and fetch communities that look to be popular and active.
It's completely unrelated to routine federation, and doesn't prevent anyone subscribing to communities that may have those words in their names.
The admin function could potentially be used to fetch hundreds of communities. It runs as a background process, so you don't know what they were until after they'd been followed. The "bad words" list acts as a safeguard against bringing in things you might not want or expect. One reason is that you may want to curate the first impression you give new visitors, as there as some that will be put off by the "fuck this" and "shitpost that" reddit-isms. Another is that you don't typically want communities that are disproportionately popular than others (e.g. if you bring in the default 25 communities, and one of is 196, then it completely dominate your front page).
If there's a particular community that you are interested in (e.g. because you moderate it), using this function isn't an efficient way to add it. In addition to the "bad words" filters, it will also exclude communities that are NSFW, or below thresholds for popularity and activity. Rather than fetching a bunch of communities at the same time, and hoping that the one you want is included, it's better to just add it manually (via a ! link or by using the "Add remote community" link) in much the same way as you would on any other platform.
On RT, the TV show Pluribus has a critic score of 98%, and an audience score of 69%, so maybe the The Onion's joke about how Breaking Bad fans are not going to like it had something to it.

Okay. Well, if it's fixed, that's all that matters, I guess. I don't understand this desire to downgrade other people's answers into speculation, but it's not like this is the first time it's happened.
Language selection with Lemmy is pretty unintuitive, so others may be interested to know that OP is technically incorrect here. Despite what the UI says, it's actually impossible to deselect 'undetermined'. Whatever frontend you're using might let you, but the backend will just ignore it. I don't use this account much, but I used it here to make a very deliberate decision to send my earlier response using 'undetermined' as the language, so that OP would definitely see it, and the fact that they clearly did demonstrates for itself that what they're suggesting is nonsense.
Using a web browser, go to your account settings. In 'languages' ensure that 'English' is selected. The posts will then be visible to you when you are logged in.
You've made this post in the 'afaraf' language, so you may as well deselect that while you're there if you don't understand it. This of course means that most people here won't see this post, ironically enough.
Also, if folks could stop parroting out the same bullshit 'federation delays' answer to every question, that'd be great. It's not that. It's actually very rarely that (even if you were the very first person to discover that community, which you weren't, it'd only take a refresh to resolve it).
The problem is not feddit.org. You can still create communities there. The problem is that the 'name' field is too long - it's needs to be 20 characters max. I answered this from another account, but now I'm thinking you can't see it because you haven't selected 'English' as a language you understand. If that's the case, then it means problems with Lemmy are stopping people solving other problems with Lemmy, and the whole thing is doomed.
Unless the person replying on Mastodon removes it of course (to save themselves some characters and because they don't recognise it).
There doesn't seem any functional difference between your comment (which implicitly Mentions the community), and the original post on thecanadian.social (which explicitly Mentions it). Screenies from activitypub.academy show that replies to both include both Mentions pre-filled.
https://thecanadian.social/@mike/116234121499688717 didn't remove the Mention, and so the comment made it to Lemmy. https://mstdn.ca/@cass_m/116234270845317774 did remove the Mention, and so it didn't.
Specifically for Lemmy btw, the reply at https://mstdn.ca/@cass_m/116234270845317774 demonstrates another problem - that instance requires a signed GET request for its actors, which hasn't been fully implemented AFAIK.