I was only able to reproduce one of these with some local testing (the not-logged-in banner). What browser are you using? As for the Explore dropdown (and most dropdowns in the web ui), they use htmx to populate, so if there is a network hiccup, then it will just show up empty. Lastly, I believe you on the buttons wrapping weird. I have caught and fixed a lot of those in my time contributing to piefed, so would always appreciate help identifying where it is happening.
A big priority for rimu when making piefed is to keep the request size small to accommodate very poor network connections. From talking with him, he has historically had to deal with extremely tenuous internet access in the past and wants to be able to still function in those environments (a user setting can also enable low bandwidth mode to disable things like images). That is just really hard to do using the javascript frameworks that a lot of modern web interfaces use these days. So, we have compromised and sprinkled in some interactivity where it makes the most sense using tools like htmx or vanilla javascript. However, it can make the site feel a bit like internet 1.0 at times.
With the piefed api maturing, there is now the option to simply use an alternative frontend (photon, blorp, etc.) or a mobile app (voyager, interstellar, etc.) instead. The main area of the site that we have not included in the api is the admin area, so managing things like defederations would still have to be done through the web UI.
Incredible optimization! I don’t think Blorp will ever be able to deliver a web experience as low data as the official UI. However, if you download Blorp (or any of the other apps) then you no longer have to send frontend code over the network. The only data that needs to be downloaded at runtime is API requests. Suddenly the network usage looks a lot more similar to the official UI (though I should test to confirm).
I was only able to reproduce one of these with some local testing (the not-logged-in banner). What browser are you using? As for the Explore dropdown (and most dropdowns in the web ui), they use htmx to populate, so if there is a network hiccup, then it will just show up empty. Lastly, I believe you on the buttons wrapping weird. I have caught and fixed a lot of those in my time contributing to piefed, so would always appreciate help identifying where it is happening.
A big priority for rimu when making piefed is to keep the request size small to accommodate very poor network connections. From talking with him, he has historically had to deal with extremely tenuous internet access in the past and wants to be able to still function in those environments (a user setting can also enable low bandwidth mode to disable things like images). That is just really hard to do using the javascript frameworks that a lot of modern web interfaces use these days. So, we have compromised and sprinkled in some interactivity where it makes the most sense using tools like htmx or vanilla javascript. However, it can make the site feel a bit like internet 1.0 at times.
With the piefed api maturing, there is now the option to simply use an alternative frontend (photon, blorp, etc.) or a mobile app (voyager, interstellar, etc.) instead. The main area of the site that we have not included in the api is the admin area, so managing things like defederations would still have to be done through the web UI.
Thanks for the feedback!
Incredible optimization! I don’t think Blorp will ever be able to deliver a web experience as low data as the official UI. However, if you download Blorp (or any of the other apps) then you no longer have to send frontend code over the network. The only data that needs to be downloaded at runtime is API requests. Suddenly the network usage looks a lot more similar to the official UI (though I should test to confirm).