other accounts:

  • 0 Posts
  • 56 Comments
Joined 2 years ago
cake
Cake day: February 10th, 2024

help-circle

  • doesn’t really look much different between the two instances. the theme differences are minor. the current default theme on piefed.world is even a bit more compact than the quokk.au default theme.

    there are also user settings for more compact post listings, e.g. the variant with smaller thumbnails:

    and after writing all this i realized you were referring to the bottom navigation. we updated several piefed versions in the last few days, if this is still the case for you i recommend raising this as a bug directly at https://codeberg.org/rimu/pyfedi/issues







  • i see. for PWAs that’s expected, for the native app i would’ve expected a consistent UA for all requests.

    our current blocks/challenges are explicitly targeting things that pretend to be browsers while not actually being browsers. we try to exclude requests that are expected to be accessed by browser based clients that aren’t directly on the main site. appending to browser user agents still matches our browser user agent detection.

    i’m not sure why this was causing issues here though, especially with the login, as that should just be 100% api stuff and therefore use VoyagerApp/1.0 from the native app?


  • MrKaplan@lemmy.worldtoVoyager@lemmy.worldHaven’t been able to log in
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    10 months ago

    Hi,

    this was possibly an unintended side-effect of our increasingly aggressive AI crawler DDoS blocking. When increasing the scope of issuing Cloudflare challenges we missed excluding API endpoints from the rule, that should be fixed now.

    This should only have affected clients with browser user agents though, and I see requests with user agent VoyagerApp/1.0. @aeharding@vger.social do you know if Voyager can send browser-like user agents when installed from App Store?


  • lemmy currently doesn’t have granular federation controls. the only option right now is to defederate from mbin instances, but other instances might still announce your users’ votes to mbin instances. the more hacky way would be to also block federation related http requests from mbin instances to prevent them from retrieving user profiles, which is probably the most effective method that could be used.

    piefeds non-federated votes are a user setting for the default value and users have the option for each vote whether it should be federated. see also https://piefed.social/post/982478