Your instance rejects Follow requests from instances not on your ‘Allow list’, which is a pretty small list.
Edit: the list has since been expanded.
aka freamon
Codeberg: https://codeberg.org/freamon?tab=activity
Anything from https://lemmon.website is me too.
Your instance rejects Follow requests from instances not on your ‘Allow list’, which is a pretty small list.
Edit: the list has since been expanded.
This is a great list. Note, though, that lemmyverse.net (and by extension, !trendingcommunities@feddit.nl) are less useful at the current moment than before because lemmyverse needs an update before it can crawl the increasing numbers of instances on 0.19.4 or above.
Please use your mander account to inform OP that their instance is wildly behind .world - see here
The delay and eventual deletion of comments and votes will have an obvious effect on mander’s “hot” and “active” algos.
If you look at this post on mander, it’s not got any of the comments, so there’s no point anyone using a .world community to answer OP’s question.
lemm.ee have upp’d to 0.19.4, and presumably turned on the Image Proxying thing - this is what I get for: https://lemm.ee/post/34040618
{"error":"unknown","message":"Request error: error sending request for url ([http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)](http://127.0.0.1:8080/image/original?proxy=https://ichef.bbci.co.uk/news/1024/branded_news/be3c/live/2a45fdb0-20ee-11ef-a3ab-e73c00cc3104.jpg)): operation timed out"}
I’ve had that problem too (messing around with test instances) - for anyone else wondering why: it’s because the RSA keypair for me@mydomain has changed, and remote instances fail to validate message headers signed with the new private key, because they’re still using their copy of an old public key.
That’s great to hear. There’s zero API at the moment though, let alone a stable one. PieFed is a monolith, without the backend / front-end split that necessitates an API.
It easy to add one, pending the addition of some missing features and a code reorganization that needs to happen anyway. At that point, hopefully some interested app developers will also be involved, to shape the API into something they may wish that other app’s APIs were like.
It seems to be quite a lot for the server it’s hosted on though (which is not the snappiest). There are, of course, still areas in the world where - for one reason or another - people still are effectively on dial-up speed-wise.
Buster should turn their attention to the size of the images uploaded to servers like this: 1.1M is arguably overkill for this one.
There seems to be some decent channels that are local to that instance (some PeerTube integration was recently added to PieFed, so I’m going by the list on this post ). From there, you can watch stuff from other instances, if course.
I think it’s more just for discovery. They provide a guide here which recommends https://tilvids.com/ as a PeerTube instance you can sign up with.
https://fedi.video/ has organised a bunch of channels into playlists that has some crossover with your topic list.
It probably is. I’d tried Mastodon but found myself not going back. Phanpy re-invigorated my interest in it.
Thanks for this. I tried to watch a video from ‘shifter’ but there never seems to be enough bandwidth (even on 360p). I can see other people have managed though, so maybe it’s a location thing (I’m in the UK)
https://fedi.video is a useful resource.
I’ve already added !andybalaam_lectures@diode.zone and !doc@peertube.biz to PieFed.
(Lemmy users may be interested to know that the Tesseract frontend also embeds the videos)
Oh right, yeah. I was thinking more of the images that people link to with posts. Lemmy currently sends those out, with
"attachment": [
{
"href": "https://lemmy.world/pictrs/image/e798447e-a79f-45b2-b3da-3aa669cbc0e5.png",
"type": "Link"
}
]
But there’s nowhere in entire JSON for any alt-text. The plan is to add alt-text as a ‘name’ in there.
In-line images do prove a point for the OP, though. A Lemmy comment with one will be sent out as
<img src=\"[https://lemmy.world/pictrs/image/9d483052-29b6-4d34-baaf-3ee092be9718.png\](https://lemmy.world/pictrs/image/9d483052-29b6-4d34-baaf-3ee092be9718.png\)" alt=\"bear vs man in woods meme\" />
in the ‘content’ field, but Mastodon expects all images to be attachments, so it just completely ignores it. (compare https://lemmy.zip/comment/10342640 with https://mastodon.social/@Honytawk@lemmy.zip/112438348076482957)..)
That sounds like a tricky combination. Wherever you go, they’ll be a good chunk of users who are unaware of / indifferent to how well the app they’re using interacts with other Fediverse platforms. Mastodon has the userbase, and - as you say - is the place where the serious discussion of accessibility takes place.
As for Lemmy - it doesn’t yet support alt-text, but when it does, I believe that the plan is to follow Mastodon’s format (i.e. a ‘name’ field in the ‘attachment’ array)
“No”, and “No”. More info here: https://sh.itjust.works/post/18710212 (includes reply from Nutomic)
Congrats. Tesseract has always been very impressive.
This post suggests there’s a problem with Lemmy/PeerTube federation, but it’ll be good to see the videos embedded (even if they have to be brought through manually)
It should get fully back to normal in a few days - the results are averaged over 7 days so there’s still some data missing (lemmyverse was fixed 2 days ago).