

Appropriately-rated comment.
Appropriately-rated comment.
You’re allowed to delete comments on Lemmy :)
(They’ll still be visible to third-party app users but that’s another topic, it should be fixed eventually)
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
Lots of posts where I disagreed at first, but I managed to find an understanding and, I guess, become a slightly better person.
One thing I fucking loved was when u/TotesMessenger snitched on their posts and it created drama. That was glorious, every time.
low-hanging fruits*
They only documented it when it came for a non-hateful subreddit and it had lots of upvotes and it wasn’t removed by moderators, except for r/teenagers.
Yeah, that culture is coming from the top, nothing much to do about that one sadly
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.
It’s a different software, so no. Also I think Kbin doesn’t have an API
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
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
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.
It works so well, that’s very refreshing
Seems dead