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.

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.

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

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!

Kbin also turns all your upvotes into reblogs, so you'll be spamming Mastodon users whenever you like posts

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