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.

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

I’m really liking Pop OS! I’d still be using Ubuntu if it wasn’t for Pop tbh. I’ve also had some fun with Elementary OS, but their hostile stance on tray icons is killing my workflow.

Ideological design bullshit shouldn’t get in the way of making a good product tbh.

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

The “local” sort is full of cats and it’s amazing

Can confirm; fun and games are over

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.

uBlock Origin makes it way better, but still, you shouldn’t have to use that in the first place

Vain and counter-productive

We need content

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

which suggests a lookup table

No, it only suggests an additional field in the Post table

since there’s no assurance that any instance is aware of any other instance

It already works like that, but slightly worse because post IDs aren’t the same across instances. If you search a newly-created community from another instance here, you just won’t find it until it’s synced, despite its URI being unique.

Thinking about it, it would be possible to have an URI for posts like post:${id}@instance.com, similar to how user URIs and community URIs are made. This way, you could open /post/1772651 on lemmy.world or post:1772651@lemmy.world on, idk, lemmy.blahaj.zone or something.

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.