aeharding

joined 1 year ago
MODERATOR OF
[–] aeharding@vger.social 3 points 1 month ago (1 children)

That’s actually incorrect, it is a solved problem in voyager. Clicking the link in the post from any Lemmy instance, or up to date piefed instance like piefed.blahaj.zone, opens in app.

The only reason it doesn’t work from piefed.ca is piefed.ca is running an outdated version of Piefed that doesn’t support the federated instances endpoint in api/alpha.

Proof:

https://piefed.ca/api/alpha/federated_instances

https://piefed.social/api/alpha/federated_instances

[–] aeharding@vger.social 7 points 1 month ago

Thanks for checking!

I was actually testing an invalid login, where it says "connection error" instead of "invalid login credentials" because the backend error isn't sent due to a CORS issue.

After attempting login with piefed.social vs feddit.online, here's the screenshots. See the "CORS missing origin" error under trasnferred column for feddit.online. Also the lack of access-control-allow-* headers compared to piefed.social.

[–] aeharding@vger.social 2 points 1 month ago

Awesome thanks for confirming!

[–] aeharding@vger.social 7 points 1 month ago (6 children)

That’s what happens when you try to signup, not login. There is a login button below pick a server button.

Also, try the web at https://vger.app/, probably easier to debug!

[–] aeharding@vger.social 7 points 1 month ago (9 children)

Do you know the admins? It looks like CORS is broken on signin (POST req), which causes the PWA to break.

Works for all the other instances so maybe they are doing something custom

[–] aeharding@vger.social 8 points 1 month ago (1 children)

The image link is broken, doesn’t work in the browser either

[–] aeharding@vger.social 12 points 1 month ago (1 children)

Hey, thanks for the Voyager rec! Note, Piefed is still experimental with Voyager, there are known issues, so as others said it might be a bit early to recommend to brand new users.

Also, any reason you prefer https://vger.app/settings/install versus https://getvoyager.app/? The latter has a bit nicer onboarding!

[–] aeharding@vger.social 6 points 1 month ago (3 children)

Thanks, I can reproduce it! It happens when the remember feature is enabled and you're opening a post for the first time from a community where you haven't opened any other posts from (since app startup)

I'll fix in the next release

[–] aeharding@vger.social 2 points 1 month ago

I could see there being a setting for that. It's intentional by default for image posts to hide the body until tapping into the post, for example viewing photography communities you probably want to scroll through the images, and not have the feed cluttered with credits and descriptions and whatnot.

[–] aeharding@vger.social 3 points 1 month ago (1 children)

You can also tap and hold the share icon for the options.

[–] aeharding@vger.social 5 points 1 month ago (5 children)

I tried but I can't reproduce. Maybe there is some setting combination that is causing issues? I tested "remember community sort" comment toggle, but worked for both.

[–] aeharding@vger.social 5 points 1 month ago (1 children)

So odd! I've never experienced that before. Did you try restarting the phone? Also do you have offload unused apps enabled?

1
PPG stack (infosec.pub)
submitted 11 months ago* (last edited 11 months ago) by aeharding@vger.social to c/paramotor@lemmy.world
 

Anyone else noticing? It seems to be affecting other instances as well, since instances hot link to eachother.

The rate limiting seems to get much worse in the evenings.

lemmy.world:

mander.xyz:

{
  "code": "object-request-error",
  "msg": "Invalid status 429 Too Many Requests for Some(\\"01/90/24/ad/1d/8d/7e/8a/82/ee/7104ff150707.png\\") - {\n \\"message\\":\\"Too many requests\\"\n}"
}
view more: ‹ prev next ›