Gregory's Server
@dansup As someone who was recently explaining Pixelfed to someone, I think you should lean into photo-only posts more. It's your main selling point. Showing text-only posts takes that away.
|
8 comments
[DATA EXPUNGED]
@niko @Gargron I experimented with text posts using css like FB does, the problem is that it can seemingly encourage low-effort text posts that depreciate the experience of carefully curated photos or videos. I think the only reason that FB did that was because users tend to pay more attention to photos, so they trick users with distracting backgrounds. I'd prefer not to go that route, even though to most people they look appealing. @dansup @Gargron (edit) For me adding group is a good idea to connect people with same passions. However, adding text-only posts is not a wise move. I agree with @Gargron as photo posts are Pixelfed's selling points. Even I hate mentioning Meta products, let me compare Facebook and Instagram. The youths nowadays are preferring Instagram over Facebook as shown in my screenshot.  Maybe I am in the minority, but I really don't think that is an issue for the server software. This idea of "one account for pixelfed to post photos, another on mastodon for text posts, another on write.as for longer blog posts, funkwhale to follow music channels" just leads to excessive fragmentation and balkanization. I'd rather have only one account with a server that can create all kinds of ActivityPub objects and let the *clients/frontends* make the filtering.  @dansup @Gargron dan i think i mentioned this a while back but how do you feel about the idea of keeping text posts out of the timeline and in their own separate feature? like itunes ping, basically -- photo posts are the main bread and butter, but artists can make text-based status updates that show up on their profile and/or appear in a separate timeline. |
@Gargron @dansup Agreeing to Eugen here. Do one thing very good.