Conversation

Notices

1. Embed this notice
   pixelfed (pixelfed@mastodon.social)'s status on Monday, 15-Jul-2024 18:53:08 JST pixelfed

   Notification Filters ✨

   Now available!

   Android: https://play.google.com/apps/testing/com.pixelfed

   iOS: https://testflight.apple.com/join/dNcLnb1n

   #pixelfed #pixelfedApp

   • Embed this notice
     Lucas A. (heyazorin@mastodon.social)'s status on Tuesday, 16-Jul-2024 05:07:54 JST Lucas A.

     in reply to

     @pixelfed app crashes when tapping ‘Collections’ under settings.

   • Embed this notice
     Lucas A. (heyazorin@mastodon.social)'s status on Tuesday, 16-Jul-2024 05:17:06 JST Lucas A.

     • Daniel Supernault

     @dansup @pixelfed

   • Embed this notice
     PhilipKing (philipking@mastodon.social)'s status on Thursday, 18-Jul-2024 15:06:59 JST PhilipKing

     in reply to

     • Daniel Supernault
     • Lucas A.
     • Kyva

     @kyva @pixelfed @dansup @heyazorin I agree, it’s poor design to have an app that crashes because of a minor version number change. A change to an API that causes a crash should be a well thought out major change with plenty of notice. The current scattergun approach to development is not acceptable.

   • Embed this notice
     PhilipKing (philipking@mastodon.social)'s status on Thursday, 18-Jul-2024 15:07:00 JST PhilipKing

     in reply to

     • Daniel Supernault
     • Lucas A.
     • Kyva

     @kyva @pixelfed @dansup @heyazorin I agree, only major version numbers should break anything.

   • Embed this notice
     pixelfed (pixelfed@mastodon.social)'s status on Thursday, 18-Jul-2024 15:07:00 JST pixelfed

     in reply to

     • Daniel Supernault
     • PhilipKing
     • Lucas A.
     • Kyva

     @PhilipKing @kyva @dansup @heyazorin We never made any breaking changes, the app requires new APIs that aren't available on the older version!

   • Embed this notice
     Kyva (kyva@meetiko.org)'s status on Thursday, 18-Jul-2024 15:07:00 JST Kyva

     in reply to

     • Daniel Supernault
     • PhilipKing
     • Lucas A.

     @pixelfed@mastodon.social @PhilipKing@mastodon.social @dansup@mastodon.social @heyazorin@mastodon.social the app should handle errors if a new feature requires and endpoint that is missing. If not, you should group new feature and make a major versión.
     
     I underestand that is exiting to deploy new features as fast as posible but is better don't have errors that new features.
     
     Now users report me that:

   • Embed this notice
     Kyva (kyva@meetiko.org)'s status on Thursday, 18-Jul-2024 15:07:01 JST Kyva

     • Daniel Supernault
     • Lucas A.

     @dansup@mastodon.social @heyazorin@mastodon.social @pixelfed@mastodon.social technically outdated xD
     
     Is a little bit crazy that you add this breaking changes that easy. v0.12.3 is just a patch release (if you follow semantic versioning) from 2 and half months ago...
     
     Keep in mind that people manage Pixelfed instances in they spare time. For me, update versions is not trivial because I have custom changes to the web app to hide the real outdated ui.

   • Embed this notice
     PhilipKing (philipking@mastodon.social)'s status on Thursday, 18-Jul-2024 15:12:29 JST PhilipKing

     • Daniel Supernault
     • Lucas A.
     • Kyva

     @dansup @kyva @pixelfed @heyazorin That’s an excuse, when Lemmy (which is still in beta) introduced similar breaking changes they gave three months notice to allow instances to update (and it still wasn’t possible for some of them to do so)

     And from a user experience point of view, how do you expect people to test a beta if they can’t log in ?

     Developers usually oncentrate on getting the basics right, release the app and leave major changes until the next planned version.