One of the challenging aspects of building a federated mobile app is parsing post captions and being able to render them properly
See, when you make a post with mentions or hashtags, mastodon converts it to HTML and mobile apps have to deconstruct that HTML to be able to render mentions, hashtags and links properly
We could just render the HTML, but when you would tap on a hashtag or mention, it would open the browser instead of in-app
Mastodon and Pixelfed do provide mentions and hashtags as lists in the federated activity, you can't just trust the HTML itself because not every platform uses the same attributes
We can use the mention/hashtag lists to build the entitymap with indices we can provide to clients so they can properly implement deep linking
@dansup@pixelfed vertical spacing between the buttons & tabs could be greater: I'm certain I'd accidentally press a button when I wanted a tab with my current long nails.
While working on the Pixelfed mobile app refactor, I found the issue causing “broken” or missing comments, it’s not a federation bug, but rather a hardcoded limit of 20 comments (on the MastoAPI)
Working on the fix, and a new pixelfed API for better comment pagination.
As you can see, you're only addressing the tags as #labels following a post, whilst most folks tend to #hashtag their #articles inline as they type out their posts.
Having a facility to integrate those two methods is of great benefit and note that in my example not all #tags are duplicates between the two methods of presenting them.
@lyyn@dansup@grishka I disagree, the 30 days delay prior permanent deletion should be the only option.
It’s does protect users by allowing a recovery when the deletion is performed by someone else than the real owner (account/computer is compromized, password is re-used/shared, …).
However, when the deletion is requested, the user should have nothing else to do, and no further communication is sent, unless a recovery is requested by the owner.