Is Pixelfed sawing off the branch that the Fediverse is sitting on?
Fediverse
66
Posts
31
Posters
417
Views
-
This post did not contain any content.
I can understand the reservation against an AP-Platform not making clear that they display only a subset of messages, but not against the practice by itself. After all, it's a platform specifically for showing images. A notification when following a non-pixelfed account that only image posts will be shown would do the trick too, but implementing the option to view text posts gives the user more agency, which is normally the best path as long as it doesn't mess with usability.
-
This post did not contain any content.
this is a dumbest opinion out of all the dumb fediverse opinions i've read.
I go to pixelfed to post my art and view other peoples art. that's it. I don't go there to read posts or what's going on in peoples lives. For that I have Akkoma/Mastodon. If I want further interaction and discussion I have Piefed/Lemmy.
this blog post just reeks of "I need my voice to be heard on all the various platforms at the same time and I don't want to go to each individual platform to do it" well I'm sorry cupcake that's now how things work. Why isn't this person complaining about Piefeed posts not showing up on Mastodon or vice versa?
If I sign up to Instagram I don't expect to see facebook posts. Most people understand this concept. People aren't going to go to Pixelfeed and then assume they instantly have access to view Mastodon and Lemmy at the same time.
-
This post did not contain any content.
I read the post and understood the problem. Then I read Dan's reply. And he's fixing it. In fact, he's fixing it in the exact way the blog post says it should be fixed, "... but those filters should be manually triggered and always removable."
Here's Dan's reply:
"... I hear the community: you want text-only posts. We are going to build this as an opt-in feature. If you want microblogging, turn it on. If you prefer the classic media-only experience, nothing changes."
Why was this blog post even written then? Now it's seeming to be personal.
-
This post did not contain any content.
Imagine a new client, TextFed, that will never display posts with pictures.
Sign me up!
-
This post did not contain any content.
The thought behind the post is worthwhile to ponder and discuss.
Personally, I don't think it's as dire as the text makes it seem. The speculation that a steadfast refusal of showing text only on PF might lead the AP protocol guardians to include a dummy pic in every post seems to me to be in the "possible but outlandish" category.
If the premise of AP was that every user should be able to see everything everywhere then defederating from certain instances shouldn't be possible. But that's a feature, not a bug.
The tree of the fediverse is big and nobody needs to saw off any branches. A picture only branch can sit next to a hypothetical text only one. I can see an argument that newbies to those particular branches could be more explicitly made aware of the filtering they will experience. While I was reading the text about the users who thought they saw everything from Mastodon on PF, my first thought was: this strains credulity. But then again, users are dumb. I hadn't realized for a while that shared posts don't show up in my PF feed on the app either.
I don't think anybody could become too big for their breeches on the fediverse because the fediverse is in no position to challenge the incumbent corporate platforms. Don't get me wrong, I love it here and on Mastodon (and on PF). But if you come from those polished centrally organized platforms and you're not willing to invest at least a little bit of time into learning how federating works (also refer to users are dumb above), you'll already be disappointed and put off before you realize you now need to also become your own algorithm. The threat scenario that PF could become so big that it can dictate protocol also presupposes that AP is the protocol that will endure forever. And with AT it already has a competitor waiting in the wings. As I said up top, the thought about how one dominating branch could damage the whole tree is worthwhile. But in a dramatic shift from this metaphor: we are in no position to have to cross this bridge any time soon.
Another reason why PF won't be getting out the chainsaw is its usability. It's only great for looking at pictures. It's terrible for having discussions about them unless you only use the website. I'm using the Android app and it's not great. Features came and went. The UI leaves a lot to be desired for me. It currently feels a bit abandoned because Dansup is more preoccupied with challenging TikTok. I still like PF because I go there just to look at pictures. I go to Mastodon for memes and dry remarks. And I don't feel like I'm breaking the protocol.
This image may be a bit wonky but convenience stores don't go out of business just because 24h supercenters exist. They both exchange ice cream for money but one of them has a bigger selection of flavors. PF is 7/11, Mastodon is Walmart.
-
This post did not contain any content.
Does this person not understand how media specific sites work? If you want a mixed media website, there are plenty out there on the fediverse. Saying every site should host every media type gives users less options, not more.
-
Come on, the whole purpose of pixelfed is to be an image federated platform.
If you want something different, use something different.
You ordered a pizza and are complaining it isn't a salad.
The problem is not "you ordered a pizza yet are complaining it isn't a salad". The problem is you are selling pizzas and salads, but the middleman is undercutting you on the delivery of the pizzas, leaving your clients with the fake impression you sell only salads and/or provide a bad service.
All that said, from an interface design perspective the current mode is exactly how it should happen. Pixelfed and pretty much everything else are purposefully subset-specific apps. All that's needed is the reminder (as visible as possible) that content you are looking at is incomplete and you can find the more complete version on this or that URL or app. Same principle as if I wanted to eg.: design a "hashtag explorer" for the Fediverse. I'd focus on that instead of the posts (and pictures); but what I can't ethically do is prevent my users from discovering their existence.
-
This post did not contain any content.
The Fediverse has plenty of problems but...this ain't it.
A bigger problem would be the inevitable outcome of what happened with Instagram; people just post pictures of text to get more reach (and probably also to circumvent Mastodon's stupid character limits).
It's a stupid and arbitrary limitation, but I digress.
-
This post did not contain any content.
Would you settle for a mail provider which silently drop all emails you receive if they contain the letter "P"?
Yes, if the mail provider is advertising the fact that they are dropping everything containing "P" AND if I'm currently not in the mood to read anything containing "P" AND if there are enough good alternative mail providers that do show me things containing "P".
What a weird take.
-
Would you settle for a mail provider which silently drop all emails you receive if they contain the letter "P"?
Yes, if the mail provider is advertising the fact that they are dropping everything containing "P" AND if I'm currently not in the mood to read anything containing "P" AND if there are enough good alternative mail providers that do show me things containing "P".
What a weird take.
And if it didn't tell you and you had to find out via an article?
-
This post did not contain any content.
Expecting an photo centric app to display text only post is really ridculous. What's thr point of making pixelfed just another mastodon type app. With the same logic , why not complaining about mastodon only allowing micro blogging short text?
-
I read the post and understood the problem. Then I read Dan's reply. And he's fixing it. In fact, he's fixing it in the exact way the blog post says it should be fixed, "... but those filters should be manually triggered and always removable."
Here's Dan's reply:
"... I hear the community: you want text-only posts. We are going to build this as an opt-in feature. If you want microblogging, turn it on. If you prefer the classic media-only experience, nothing changes."
Why was this blog post even written then? Now it's seeming to be personal.
Seems like the article was written first maybe?
-
The Fediverse has plenty of problems but...this ain't it.
A bigger problem would be the inevitable outcome of what happened with Instagram; people just post pictures of text to get more reach (and probably also to circumvent Mastodon's stupid character limits).
It's a stupid and arbitrary limitation, but I digress.
It's totally a problem: If I take a look at my Mastodon account from Pixelfed, there are a lot of screenshots shown and some other random images. Which totally does make sense as I do post stuff like that on Mastodon and screenshots totally make sense there. But if you take them to the center of the stage into a photocentric app, that really does look like shit
-
No, you as a poster in the Fediverse are selling pizzas and salads. PixelFed is "misrepresenting" you, for lack of a better word, by telling people you only sell pizzas. The thing is, it wasn't doing that before. It was purposefully made to hide useful information that was there before. IMO there should be a sticky "this user has other content which is not images" headbar or something. Only removable as an opt-in per account followed, so that it is not possible for people to say that PF purposefully hid information.
-
I think OP has a valid point - it's not about experienced users, but newcomers to the fediverse, who may think they are following an account, when actually they only see a small part of it - there could be some indication of what's missing.
No it doesn't. Just like someone don't expect to see images on tiktok or long form text on x. Nobody would expect to see text only posts on Pixelfed
-
This article's core argument seems to be that Pixelfed is violating the ActivityPub protocol by not displaying posts that do not contain images. That's just not true at all. I'm interested to know where the protocol ever has such a requirement.
The principle behind a communication protocol is to create trust that messages are transmitted.
And they have been transmitted. They've been filtered out after transmission, but the protocol did its job.
If a message is not delivered, the sender should be notified.
Perhaps. But that's not in the spec. There's no obligation to notify iirc that a post got filtered out on the target instance.
Even if Pixelfed sent Reject(Note) back for every post without an image, would Mastodon even display that to the user anywhere? Would most users want to see that for every post not containing an image multiplied by every Pixelfed instance it got federated to? I'd personally interpret that as spam.
If that guy was right there wouldn't be defederation and many defederation are not announced
-
The problem is not "you ordered a pizza yet are complaining it isn't a salad". The problem is you are selling pizzas and salads, but the middleman is undercutting you on the delivery of the pizzas, leaving your clients with the fake impression you sell only salads and/or provide a bad service.
All that said, from an interface design perspective the current mode is exactly how it should happen. Pixelfed and pretty much everything else are purposefully subset-specific apps. All that's needed is the reminder (as visible as possible) that content you are looking at is incomplete and you can find the more complete version on this or that URL or app. Same principle as if I wanted to eg.: design a "hashtag explorer" for the Fediverse. I'd focus on that instead of the posts (and pictures); but what I can't ethically do is prevent my users from discovering their existence.
But pixelfed is only selling pizza and the cudtomer complains that he didn't find a salad option
-
Expecting an photo centric app to display text only post is really ridculous. What's thr point of making pixelfed just another mastodon type app. With the same logic , why not complaining about mastodon only allowing micro blogging short text?
Well, Mastodon will show everything in the feed, no matter if it's a video, a short blog, a long blog, a picture, a podcast, whatever. Mastodon is (primarily) microblogging in terms of output, but an everything platform with a chronological feed in terms of input.
This is where this user seems to get confused - they expect everything on the fediverse to display every type of content, just like Mastodon strives to do. Which is, as you said, ridiculous. If PixelFed was to display audio content and Funkwhale was to display pictures, what would be the point of these services in the first place? If they want everything to be Mastodon, why don't they just stick to Mastodon? Maybe Pixelfed users have no interest in reading their dumb blog posts?
-
And if it didn't tell you and you had to find out via an article?
Then you probably should have double checked before signing up to an e-mail server dedicated to "Explore + Share beautiful e-mails without the letter P in them". Pixelfed is extremely open about being a picture platform.
-
This post did not contain any content.
The consideration you should pay to other software should depend on your power and influence in the network.
If PixelFed was dominant in the fediverse, and other apps did feel the need for a dummy pic workaround, that would clearly be a problem. No client feels the need to do that because PixelFed is not dominant, but if it was, it would be fine to criticise them for not "playing nice" and helping the rest of the ecosystem.
I think there's much more scope to criticise Mastodon for the workarounds other software have to use to be interoperable, than PixelFed, purely because of its power in the network.
We need different apps to experiment and work out what users want. It's totally fine to experiment with different models and ways to view content. Only when you have a lot of influence over the ecosystem should you have extra responsibility.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@anthony@forum.unfinishedprojects.net did you just remove the privilege from "fediverse"? Leave it on for "registered-users"
Edit: oh I see what you mean. Let me take a look at this tomorrow.
-
@julian@activitypub.space - Sorry to always bother you with questions. But according to the github issue suggestion: https://github.com/NodeBB/NodeBB/issues/14019#issuecomment-3974850252
I unchecked the "upvote" & "downvote" section that holds the federated communities. Instead of just on federated users, I did it on all of them.
It still seems to not be working. Is this a bug or user error?
-
Well, Darn. That didn't work.
A few more upvotes please. I adjusted a setting - hopefully it fixes it.
[Edit]
Well, Darn. That didn't work.
A few more upvotes please. I adjusted a setting - hopefully it fixes it.
[EDIT 2]
Well the numbers havn't changed here. So maybe it is working. do these numbers show different on anyone elses instance/community?
-
Hey, I tried to make it so that upvotes people give this post and my comments won't actually affect my nodeBB forum reputation. Anyone mind upvoting a few times to test this out.
For my own reference to see if it changed:
-
I put together a brief explainer here 🙂
https://community.nodebb.org/topic/19218/federation-what-is-it-and-how-does-it-work
-
Actually I fear that if I tag the community, my reply might appear as a new post in the community, rather than a reply in a previous post.
According to this source it may happen that replies from Mastodon simply don't show up.
-
Thanks for the tip! let me try that :)
-
You might have to tag the community for it to show up.
