I'm conflicted.
The official #pixelfed app I'm developing, I have to decide between fully embracing mastoapi or going our own way for the app.
Both choices have their own pros/cons, it would be easier to go our own way. On the flip side I feel guilty not reciprocating cross app compatibility like masto apps do.
It's so cool pixelfed users can use mastodon apps.
No plans to drop support for mastodon apps btw, just unsure about how to approach our own app compatibility. #pixeldev #pixelfedApp
@dansup Maybe an unpopular opinion, but I actually think it would be better if you couldn't follow #Pixelfed accounts from a Mastodon account and vice versa.
They are differently designed apps, and the expectations around what people post and how they interact will naturally be different.
At least, I wish following a PF account in Masto or vice versa would warn you that you're doing something weird and not all functionality might work.
Anyway, I support you going your own way here.
@graue I've never heard that before, and I'm hesitant to limit our platform to just photo/video sharing as it basically breaks the common federated model.
When you follow a mastodon account, you'll never see text only posts, just photo/video posts in your home timeline
Federation Follow is for me one the strongest / most important things to include (for anyone and almost any purpose)... Counts for a lot and helps people away from coporate 'interests' we don't like...
@dansup @graue
For PixelFed or generally picture accounts there could be instead thumbnail summary or link as default option instead of 1 picture per post etc.
Over everything to follow other people from my one FediVerse account and centralise friends / news etc AND not need any commercial 3rd party subscription methods in between is the real winner for civilisation (like what PixelFed provides liek Instagram) and this is what increases worth across everyone inside that eco-system every second there not there but sing what is 'over here'.
