gant

Not all of the maintainers came over to LOS. They only support devices with volunteer maintainers.

https://wiki.lineageos.org/faq.html#my-device-is-not-officia...

Working as intended.

OP literally just deleted a bunch of files from the repo and then went out of his way to break compatibility with normal JWT HS256 tokens by changing the typ and removing the alg argument. If you wanted to pull out other algos from jwt-go, deleting their implementations would've been entirely sufficient. There is a map that holds a alg-string to implementation that would've ended up with only HS256.

Instead OP made sure these tokens can't be used outside their fork, and thus only in Go.

ISHYGDDT.

People still use Java Web Toolkit?

Okay, dumb jokes aside, they're clearly talking about alternative ways to authenticate, so I wouldn't know how you could conclude this was about anything but JSON Web Tokens.

Oh hey, it's another "JWT libraries used to be terrible" article.

Idiots shouldn't write authentication code. Especially when credentials are involved.

Funny jwt-go was used as an example; it was never vulnerable to the alg-none attack: https://github.com/dgrijalva/jwt-go/commit/2b0327edf60cd8e04...

Most likely not, as you'd be replacing the affected function (wp_mail) with the plugin.

Of course electron is fast, it builds on years of work making v8 fast.

My main issue is battery life. I just need to open one electron app (Discord, Slack, Spotify even though that's CEF, but close enough) to have powertop drop from 10 hours expected battery life to 3-4.

Stop spewing bullshit.

Here's an old revision from 2005 by a Valve employee confirming Steam used VGUI back then.

https://developer.valvesoftware.com/w/index.php?title=VGUI_D...

No, VGUI is not HTML.

Here's a fun one. Start Steam with `-dev` and hit F7. Widget factory VGUI edition!

Oh also, https://developer.valvesoftware.com/wiki/VGUI_Documentation

And thus the era of METAL[1] begins...

[1]: https://www.destroyallsoftware.com/talks/the-birth-and-death...

Nope

https://github.com/getgrav/grav/issues/516

I had my spotify cache on a btrfs SSD with CoW enabled until a few minutes ago.

Fuck me.

I just subscribed. Very nice and simple service, love it. The only bad thing I can say is that the "popular" tab seems to be HN delayed by half a week or so.

Even with a free software tool like mitmproxy modifying requests is trivial. You don't even need Burp.

Everybody that pins it or retrieved the file from someone else (second one to maximum cache size that is configurable). Files and folders are referred to by hash.

Usually you still need to run a server to seed the files, but if a file becomes popular it will be served from anybody who also retrieved it and likely persist in the network even if your server goes down.

Think of it as BitTorrent for the web. It has Gateways that allow current browsers to access the network and pointers to update content with a new version (that's /ipns/ not /ipfs/ - the old version persists as long as someone hosts it).

What's also interesting is that due to the nature of the hashing algorithm (it's a merkle tree), you can "ipfs add" a directory, preserving the file structure inside, so websites on IPFS can use relative paths.

The name "Request for Comments" is historical, but still very confusing. IDs are the literal requests for comments now, and RFCs the standards.

I always thought it made sense to address local VMs with .localhost domains in my hostsfile. Apparently not?

PHP: WordPress, according to Automattic:

https://api.wordpress.org/secret-key/1.1/salt

I'm personally still trying to figure out where the hordes of new users that just install Apache are. In these times, if you can install Apache 2 on a computer permanently connected to the internet you can probably also install Caddy or Certbot.

Check the username.

The point seemed to be that killing existing Win32 APIs would hurt Microsoft more than it helps the UWP, but for gaming the only thing that needs to happen is a new graphics or peripheral API that's UWP only and is substantial enough for developers to drop Win32 support.

"Open Source" developer does not get the point of free software.

News at 11.

P.S.: AGPL isn't the GPL.

DX13. Now what?

And aren't UWP apps a walled garden (apps need to be signed unless you enable developer mode, which has all kinds of side effects, requires a Microsoft account and can be revoked?)?

The only thing I recall when I see IFLS:

https://www.youtube.com/watch?v=PtyYlAH0f_M

It's a very long term thing. It'll probably happen because new APIs will be on UWP and not on Win32. I think VR might be the "next thing" that'll only get in-OS support in UWP.

Seems that only applies to users that don't have a paid plan.

Now they are paying with their data. What did they expect?

>should be used together

That's a wonderful idea /s