Conversation
Notices
-
@dcent About the cache: right now, the cache is configured like this:
text/css 30d;
application/javascript 30d;
~image/ 30d;
~video/ 30d;
~audio/ 30d;
Everything else is not cached. I understand that, in order to show that you've liked a notice, that particular thing can't be cached, else it would not show.
About images: you are right, it's a poor UX. I'm afraid I don't know devs plans about it. I know a new interface is in the works, but that's about it.
!gnusocial
-
Re GNUSocial (@administrator @lxo):
Can pages have a longer cache time? What I've noticed is after I 'like' a person's post for example, and a new page is loaded to tell me the 'Like' was successful, I hit 'Back' in the browser but the page from earlier is not cached so the browser is forced to fetch a new page for the server; 100% of the time (so far) that page has been identical, no need to request a fresh page. I think this needs to be fixed to improve experience for both end user, that must wait for the fresh page and the server that must do 3x more work (on average) for zero benefit; a 5-minute cache time would fix this.
Also, images in posts should be enlarged in a new tab when they are clicked, not when the little link above the image is clicked. Currently clicking an image does nothing, and it's poor UX, I've put this past a couple people now and they seem to struggle with the UI. In all fairness, the little link above the images is only clutter, it is not even useful as a caption because it is often truncated.
Are these issues listed for GNUSocial v3? If not, I'll be interested in someone being so helpful as to copy-paste into it.
-
Oof, mastodon now forcing people to switch on javascript just to view a person's fediverse profile? Will it be optional so instances can choose whether they force js?
🤔