Don’t get kids.

Actually going to the signing session with him later today in London. Looking forward to giving the new album a spin

Looks very similar to Fabuland from back in the 80s I must say

Not sure how much that would be in other currencies, but if you’re happy with the price drop, I’d say: go for it! I’ve just played through the main story line and am currently working my way through Nuka world after the whole Fallout bundle was on sale last month. Enjoy!

As far as I’m aware, there is no way to fully know there wasn’t any tampering or swapping of executables that were produced by a workflow. As most things on the internet, I believe there needs to be a degree of trust towards the original author and original owner of the repository that what they published is indeed a built executable from the original source. If there is any doubt about this, the only verifiable way to know for sure, if for a potential user to build from source themselves.

I can think of ways where there is a trusted third party that provides a public key with which to sign the built executable, after which it can be checked by the third party (with its private key) whether it is still the same executable. Specially if a different key pair is used for every signing operation. But there are still flaws there, and would, ultimately, still rely on a degree of trust in the third party.

The Ghost of Tsushima soundtrack takes me back to the game every time

I’m interested as well. I hope there’s a different answer than Amazon Kindle, as I refuse to buy anything from them

Why start a new community if !obsidianmd@lemmy.world already exists?

This is the way

Just yesterday 😅 there’s a bug in the main branch of Lemmy itself that I was trying to pinpoint (introduced after 0.18.0 was tagged). Instead of walking through all recent commits manually, I used bisect. Bisect is not a magic bullet, and you could do the same manually, but it’s a good tool in the toolbox to know sometimes.

It’s an Apollo-only feature, Reddit doesn’t natively do this. I’ve been thinking about this feature for a bit, and it seems a straightforward implementation would be to store “seen” post identifiers with a TTL. Since the data is just bits of text, it should not take a lot of storage on device, and the TTL takes care of cleaning up. Since most posts on Reddit would be bumped away from any type of feed within at least a couple of days, a TTL of a week or shorter would probably work for Apollo. Not sure about Lemmy right now though. I’m not a mobile dev, so would not know exactly how to implement a system like this for Mlem, but if it was a webapp I would use Redis (if server-side) or something like local storage or cookies with TTLs (if bowser-based offline).

I’m not on the experimental build, so will have to wait until it gets a stable release, but I wonder if it’s a similar scheme to the Switch version?