Nato Boram

Yeah, better use the linter too, that way it’s limited to 80 characters

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.

Being connected online is advertising intrusion vectors to would-be nefarious actors

What Dart looks like when written by ActionScript programmers

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

A government-sponsored instance could be interesting, but I’m not sure what value it would bring. Also it would probably turn instantly into worse than Facebook with toxicity.

I didn’t think we would have ads so soon on Lemmy, lol

Putting Tumblr on ActivityPub could be interesting and potentially save it, but there’s so much deleted content from when it was in its prime that I’m not sure if it’s even worth it. The platform is so dead.

That said, giving taxpayer money to private social media businesses is the worst idea ever. In the first place, public money should mean public code.

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/[email protected]

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.

This is what I’m working on

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

And this, ladies and gentlemen, is why having “leopards ate my face” in the title is banned in the subreddit :)

It’s honestly something I have always wanted from Reddit. You know that moment when you open a post, do stuff, go back and then suddenly you lost your scroll position and you have to go back to where you were and it takes so much time that you just close the app? Yeah, fuck that.

I’m thinking about infinite scrolling in a way that edits the page number automatically so that you can go back even if you reload the page, but it’s definitely not a priority at the moment. I’d rather add basic features like commenting and posting first. And maybe basic mod tools, since it’s always something that third-party apps lack for some reason.

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.