Developer of PieFed, a sibling of Lemmy & Mbin.

  • 90 Posts
  • 608 Comments
Joined 1 year ago
cake
Cake day: January 4th, 2024

help-circle















  • Yeah. But in this case the Topics menu can be quite heavy as it lists every community that the current user is subscribed to. Instead of generating that menu (and sending it to the client) on every page load, when it probably won’t even be used, PieFed makes an ajax call (only possible with JS) to retrieve the topics menu when it’s clicked. Same for ‘Feeds’.

    This cut the amount of HTML being sent to the browser by around 50% (depends on how many communities you subscribe to but PieFed makes it extremely easy to subscribe to dozens of communities with a single click so many people have hundreds) and eased load on the server too. Some of the more under-powered instances run noticeably faster now.









  • Rimu@piefed.socialOPMtoPieFed Meta@piefed.socialPasskeys in PieFed
    link
    fedilink
    English
    arrow-up
    3
    ·
    17 days ago

    It’s an alternative and will remain one for a long time. Browser & OS support needs to mature before we could even think about making it a hard requirement.

    At present I expect only instance admins would be interested in passkeys.

    Over time if adoption and viability increases we might want to make passkeys more prominent, include the creation of the passkey as a step in the onboarding process, make email-based 2FA compulsory for every login when people use the old username+password method and various UI nudges to get people moving in the ‘right’ direction. But all that feels like a long way off at the moment.