Ahh, yeah, I think I didn’t quite follow OP’s request. The part they don’t remember is the time between where they traveled to in the past and their “present”, and the story is about them intuiting what happened in there.
From the title it sounded like the protagonist was suffering amnesia-like symptoms about how the world used to be along with everyone else.
I promise you in a year you’ll be asking the same question about the same group of people.
So the premise is: they travel back in time, change their future, travel back to the present, forget everything they did while time traveling, and now have to just experience their new future without knowing anything changed? Do I have a that right?
I mean, how do you know this isn’t the backstory for every character in every story ever? How do you know you didn’t JUST do this yourself?
Wonder if steam workshop scans for this kind of thing, or if it would have otherwise been found quicker.
What client are you using? Those all sound like complaints about the client, not mastodon.
I’m all for it. All publicity is good publicity in this space. Open criticism is the first step to better open software.
Lol that’s actually hilarious. So but, why not comment on your posts too? Each post is just sitting there with an empty comments section.
I recently put a dozen hours into Witcher 3 while using my steam deck on a couple long flights. I’m pretty sure it synced correctly when I finally got home and connected to wifi. Maybe it didn’t work at one time, but I’d be surprised if it still doesn’t.
I don’t see any of The Avalanches on there. All their stuff is good, but if you haven’t listened to them, probably start with the original Since I Left You album.
For reference, I discovered J Dilla - Donuts when trying to find more stuff like The Avalanches.
Yeah, that QI clip came to mind when you mentioned it, but to your point the shape that we consider “fish-like” shows up a lot in water. Even whales and dolphins figured out a similar shape, despite them not being fish (though they might still be etymologically related if you go back far enough?)
Ok, I can buy that the shape of a crab is probably optimized for a certain lifestyle.
I’m not an expert, but my understanding is that the science indicates all mammals have a common ancestor. Not certain about fish, but I think that’s a similar case?
To me, the surprising part about carcinisation is that, the form of a crab seems oddly specific, but non-obvious. I mean, I look at the form of a fish and think, “yeah, it makes sense why that shape would be favored in water,” but I look at a crab and think “guess that’s just what worked out for your ancestors. Tough luck, buddy.” But apparently it’s not just bad luck, it’s a common strategy.
Btw it looks like you accidentally quoted the same sentence twice.
Or just the form of a crab in general! Carcinisation is so weird, but apparently evolution sometimes goes “Let’s just do crab again, that shit was 👌”.
My post was talking about where I thought anti-cheat would need to end up in order to be effective without being invasive, not about the state of anti-cheat now. I gave VAC as an example of a cross-game platform for cheat detection, and thus where valve would most likely stick something like this.
Anti-cheat is an arms race. We just find ourselves at a point where the arms race has progressed to the point where the best known strategy for securing a play session means ostracising custom hw/kernel configurations.
But I have to think it’s only a matter of time before even that’s not enough, (since there already exist ways around kernel level anticheat, including AI-based techniques that are entirely undetectable).
My guess is the logical conclusion involves a universal reputation based system, where you have an account with some 3rd party system (maybe VAC) that persists across all games you play. It will watch your gameplay, and maintain a (probably hidden) “risk of cheating” score. Then matchmaking for each game will use this score to always pair you against other accounts with a similar score.
Actually, it might not be a “risk of cheating” score so much as a “fun to play with” score. From a gameplay perspective, it’s just as fun to play against a highly skilled non-cheating human, as it is a bot that plays identically. But it’s less fun to play against a bot that uses info or exploits that even the best non-cheating players don’t have access to (ex. wallhacks). So really, the system could basically maintain some playstyle-profile for each player, and matchmaking wouldn’t be skill-based, but rather it would attempt to maximize the “fun” of the match-up. If a player is constantly killing people unrealistically fast, or people who play with them tend to drop early, this would degrade their “fun” score and they would tend to be matched only with other unfun players.
I think this would be the only practical way to fight cheating without even more invasive methods that will involve just deanonymizing players (which I think some studio will inevitably try in the near future).
I disagree that it’s the same for multiple reasons: first off the project and telemetry were never profit-driven. Their goal was always to use modern methods of software development to make the software better.
The fact is, these days all for-profit projects gather a ton of info without asking, and then use that data to inform their development and debugging (and sell, but that’s irrelevant to my point). To deny open source software the ability to even add the option of reporting telemetry is to ask them to make a better product than for-profit competition, with fewer tools at their disposal, and at a fraction of the pay (often on a voluntary basis). That’s just unreasonable.
Which is why the pushback wasn’t that they were using telemetry, it was that they were going to use Google Analytics and Yandex, which are “cheap” options, but are obviously for-profit and can’t be trusted as middlemen. They heard the concern over that and decided to steer away to a non-profit solution.
But as a software dev and a Linux user, I often wish I could easily create bug reports using open source, appropriately anonymized telemetry reporting tools. I want to make making a better system for me to use as easy as possible for the saints that are volunteering their time.
As for the issues in tenacity, it was likely specific to what I was doing. I was rapidly opening and closing a lot of small audio clips, and saving them to network mounted dirs under different names. I remember I had issues with simple stuff like keyboard shortcuts to open files, and I had to manually use the mouse to select a redundant option every single time (don’t recall what it was), and I think it would just crash trying to save to the network mounted dir, so I had to always save locally and copy over manually. So I just switched back and continued my work.
Afaik, back when it all went down, they heard the public reaction about the telemetry thing and completely reversed course. On top of that, many distros would be sure to never distribute a build with telemetry enabled anyway. So there has never been any cause for concern. Would love to be proven wrong, though.
Also, Audacity is handy, but it’s not perfect, and I’ll gladly use a better alternative. But the last time I tried Tenacity, it had a bunch of little differences that made the tool just a bit harder to use. So I still default to audacity.
Which is a good reminder to everyone to support your local Lemmy instances.
Let’s Encrypt is good practice, but IMO if you’re just serving the same static webpage to all users, it doesn’t really matter.
Given that it’s a tiny raspi, I’d recommend reducing the overhead that WordPress brings and just statically serve a directory with your site. Whether that means using wp static site options, or moving away from wp entirely is up to you.
The worst case scenario would be someone finding a vulnerability in the services that are publicly exposed (Apache), getting persistence on the device, and using that to pivot to other devices on your network. If possible, you may consider putting it in a routing DMZ. Make sure that the pi can only see the internet and whatever device you plan to maintain it with. That way even if someone somehow owns it completely, they won’t be able to find any other devices to hack.