Nato Boram

Full post is visible from lemmy.world, too: https://lemmy.world/post/2064026

Get Pixel Experience or LineageOS. It’s the whole point of having a Pixel phone; you can still upgrade it after it was planned obsolescenced.

ReVanced is so much better. It can even block Reddit ads.

Hey, that’s like an IPFS gateway

NewPipe is better for playing a playlist in the background, ReVanced is better for active watching and browsing

Don’t forget that NewPipe × SponsorBlock is a fork that adds SponsorBlock. Also there’s ReVanced to make YouTube bearable while still having access to your curated feed.

I wouldn’t even watch LTT without SponsorBlock tbh

I have something: https://natoboram.github.io/Leanish/lemmy.world/c/leanish@lemmy.world

There’s no Android build yet since it’s easier to just focus on features first and deployment later, but I do plan on having a SSR build, a PWA build and an Android build.

It works, thanks!

It would surprise me if that was the explanation since this can be easily fixed by Lemmy.world itself by not sending two Accept-Control-Allow-Origin headers, thus breaking web clients.

Right now, I’m forced to route my own calls to my server on the app I’m making because Lemmy.world is misconfigured.

I guess that for instance below 0.18.1, it makes sense, since Lemmy had a bug at that point that didn’t allow web clients to connect.

It would help on other websites and on some in-app ads from mobile devices

I’m on Firefox, too. Can you try on a fresh profile?

Hi! I noticed an issue with the headers sent by Lemmy.world.

Headers sent from and to this website’s official UI look like this:

HTTP/1.1 200 OK
server: nginx/1.18.0 (Ubuntu)
date: Fri, 07 Jul 2023 23:35:17 GMT
content-type: application/json
vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
content-encoding: gzip
access-control-allow-origin: *
access-control-allow-methods: GET, POST, PUT, OPTIONS
access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range
access-control-expose-headers: content-encoding, content-type, vary, Content-Length,Content-Range
X-Firefox-Spdy: h2

Which is fine. However, headers received by custom clients look like this:

HTTP/2 200 OK
server: nginx/1.18.0 (Ubuntu)
date: Fri, 07 Jul 2023 23:33:50 GMT
content-type: application/json
vary: accept-encoding, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
content-encoding: gzip
access-control-allow-origin: https://natoboram.github.io
access-control-expose-headers: content-encoding, access-control-allow-origin, content-type, vary
access-control-allow-origin: *
access-control-allow-methods: GET, POST, PUT, OPTIONS
access-control-allow-headers: DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range
access-control-expose-headers: Content-Length,Content-Range
X-Firefox-Spdy: h2

There’s two access-control-allow-origin! This still breaks web clients.

Oh wow, it actually works!

Try on another browser just to see

People will hate you regardless of what you do

It works so well, that’s very refreshing

I’m making a web app at the moment for personal use. So far, you can scroll posts, sort, filter, upvote, downvote, view one comment page, view a user’s posts, view a community’s posts, subscribe / block users and communities… and that’s about it

Ironically, since it doesn’t have the blur NSFW post feature yet, it’s a much better client for browsing NSFW communities than established clients :D

Absolutely not ready for prime time yet; there’s no deployment, you have to build it from source and it you can’t even comment. https://github.com/NatoBoram/Leanish