Hello, !Hubzilla Development
Out of a private discussion, I have two suggestions
for Hubzilla development community's consideration.1.
Currently Hubzilla doesn't cache remote images. This may have benefits for hubs' performance, but it also means decrease of privacy for users. The images issue is not only my concern, I've seen users of diaspora and Misskey (which both have a similar image approach) share opinions on the same lines. See recent discussion
- first screenshot
from uMatrix plugin shows the state of affairs in Misskey, second screenshot
- Mastodon. The advantage of the second approach for users is that they don't load all the images with their own ip. diaspora added a proxy
, it's not part of the main codebase, so few admins use it. Can this issue be addressed in Hubzilla?2.
Hubzilla user name / handle is a link that leads to remote hubs (assuming user is on another hub than myself). In most other federating networks clicking on a user handle usually opens their profile in the network's interface, preloading basic public profile information (if provided) and a couple of latest posts (or none, if there're none or all were limited visibility). Usually there is a separate link "see full remote profile" or something like that, that leads to remote server. Of course, seeing all profile posts in a federating environment is possible only by visiting that remote profile directly. However, in many cases what I need is just a quick glance at a user's profile (is it a human? a bot? have they got any information to judge whether to follow them or not?)
, and it would be great if I didn't have to visit remote links in such a case. Below are screenshots of my profile viewed from diaspora and other users' profiles shown inside Mastodon interface. Do you think it would be a good idea to cache basic profile information, so that when Hubzillian clicks on a handle link on some post, they will see the profile from their hub's interface?