Mostly just used for moderation.Main account is https://piefed.social/u/andrew_s
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 MBIf 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 => ServiceIt'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.- JumpDeleted
Permanently Deleted
Posted by the comic author here btw: https://sh.itjust.works/post/51473460
- JumpDeleted
Permanently Deleted
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.
You might need to have the 'show nfsw' setting turned on. Anyway, they look like this:
So the theory that they were downvoted for spamming someone's feed likely has validity.
Hmmm. Speaking of Fediverse interoperability, platforms other than yours (Pandacap) typically arrange things so that
https://pandacap.azurewebsites.netwas the domain, and something likehttps://pandacap.azurewebsites.net/users/lizard-sockswas the user, but Pandacap wants to usehttps://pandacap.azurewebsites.netfor both. Combined with the fact that it doesn't seem to support /.well-known/nodeinfo means that no other platform knows what software it's running.When your actor sends something out, it uses the id
https://pandacap.azurewebsites.net/, but when something tries to look that up, it returns a "Person" with a subtly different id ofhttps://pandacap.azurewebsites.net(no trailing slash). So there's the potential to create the following:https://pandacap.azurewebsites.net/sends something out.- Instance hasn't heard of that, so looks it up, and creates a new user in its database, with the returned ID (
https://pandacap.azurewebsites.net) https://pandacap.azurewebsites.net/sends else something out. Instance looks in it's DB, finds nothing, so looks it up and tries to create it again. The best case is that it meets a DB uniqueness constraint, because the ID it gets back from that lookup does actually exist (so it can use that, but it was a long way around to find it). The worst case - when there's no DB uniqueness constraint -is that a 'new' user is created every time.- Repeat step 3 for every new thing you send.
If every new platform treats the Fediverse as a wheel that needs to be re-invented, then the whole project is doomed.
Fediverse @lemmy.world lemmyverse.net looks to be unmaintained and is becoming increasingly less useful
Fediverse @lemmy.world Quick video demonstrating that lemmy.world sends every activity out twice
Comic Strips @lemmy.world Ancient Aliens
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.