Hey, where's Perry?
ubergeek77
joined 2 years ago
0.12kg over four years??
How is that not within the margin of error?
More like guesswork/assumptions than reality
Sorry to be blunt, but you're not a developer and it shows. Android's build system was purpose made to be reproducible. Electron was not.
There is so much going on in an Electron build, most of which is out of Signal's control unless they maintain an entire fork of the Electron build stack. That is an enormous engineering effort for basically zero benefit.
It probably is functionally reproducible, apart from checksums differing due to build dates baked into the artifacts somewhere. It's not as easy as you think.
If you think it's as easy as "building it in a Docker container," then by all means, try.
Keep in mind that Lawnchair is buggy and consistently 2 years behind the latest version of Android. I'm using their 12.1 beta, and it still crashes with null pointer exceptions about twice a week. And, on Android 13 and 14, integration you would expect between the recents screen and Lawnchair does not work. These are the gestures you're talking about.
And here we are on the launch of Android 14, with no development of Lawnchair for Android 13 in sight.
I should also point out, these gestures you're mentioning only work on the stock Pixel launcher, the AOSP launcher, and Lawnchair. This is because starting with Android 9, Google baked the recents switcher directly into the launcher app. And, it has to be a system-level app with a special system config that allows the launcher to perform this function.
This is why root is needed for the Quickswitch module. Lawnchair has the code to do this (at least on Android 12), but you have to overwrite a system config to allow Lawnchair's package name to be capable of serving the recents screen.
The person you replied to is being downvoted, and yes, expecting support from Google is a meme, and Google deserves 100% of the negativity they're receiving in this regard.
But, in their defense, they have always kept their word on keeping Pixels updated, and in some cases, have added on an additional year of support when not originally planned, including an extra full Android update for older devices.
So while they eventually kill every new software product they make, they've always kept their word on Pixel updates. I think the Pixel team has a lot more resources than the rest of Google, so I'm inclined to believe them for now, but I'll be one of the first people grabbing a pitchfork if they don't keep their word.
Neither of those are issues:
- Both Investigations games had HD mobile ports that already had redrawn/upscaled visuals. They look really good.
- They would need to translate AAI2, but localizing a previously fan translated game is not unprecedented, they did it with GAA.
It's not an assumption. The vanilla Signal app has code in it that disables itself after a certain period without updates. Unless they removed that from this app, then this will do the same thing.
In this case, it sure does sound like abuse. Considering the careful wording, combined with the seemingly kneejerk reaction of requiring authentication, there was likely illegal activity going on:
Earlier this year we saw an increase in the number of reports we received about some people using our service in ways that we cannot tolerate. To be more clear, this was not about some people merely saying things that others disliked.
Over the past several months we tried multiple strategies in order to end the violations of our terms of service. However in the end, we determined that requiring authentication was a necessary step to continue operating meet.jit.si.
It was a free, anonymous service that let people stream video and send messages. Consider for a moment if that "video" was actually non-video data encoded to be streamed through Jitsi and sent to another location. Or, consider if the video was video, but was so egregious and illegal, that Jitsi had to take action. It doesn't take a lot of thinking to consider the kinds of activities could have been going on.
Why is everyone up in arms about this? The abuse of their free service was rampant. This isn't a core project change, this is just a measure to keep a version of the project up for free without completely taking it down. They don't even have a way to monetize this. An alternative was to simply shut it down and only allow you to self host it.
I self host my Jitsi instance, but as a privacy nut, I don't see a problem with this. Absolute privacy cannot always coexist with free anonymous services. Don't blame Jitsi, blame the people who ruined it for everyone else.
I spent a lot upgrading my PC, but I ended up being so busy with other things that I really didn't have time to play it. The promise of better looking games and better VR performance excited me, but after it was all said and done, I hardly turn the thing on. For a whole month I just wanted to play on my Steam Deck, and even just these past two weeks, I haven't had time to do any gaming at all.
Maybe your situation is different, maybe not. But think about what your day to day life will be like after you buy it, rather than focusing on game fidelity.
You said you're saving up for a house. Moving is time consuming and stressful, it will likely be a month, 2 months of making arrangements. Will you have time to game?
Unfortunately, there is not a lot of information to go off of here. I was able to upgrade to 0.18.4 with no hitches, and I haven't seen similar reports of this.
Are you using any custom configs? Do the logs for just the Lemmy service show you anything of note?
docker compose -p lemmy-easy-deploy logs lemmy
In the past, Lemmy itself has had some strange edge cases causing crashes, such as an improper audit log value causing the entire audit log to fail. It's possible this is a similar case, in which case you may need to file a bug on Lemmy's tracker.
You are welcome to file an issue with some more information and logs, but if this is an issue caused by a bug in Lemmy, unfortunately I won't be able to fix it.
If you're still having issues, feel free to give me some more info on my tracker and I can take a look:
I really hope this will let my AR glasses work. I was bummed they didn't work with my Pixel 6 Pro, and half the reason I went for an 8 Pro were the initial display out support news from July.
When this workaround was reported to not work, I was pretty bummed, but this seems like a good sign. I'll be building my own ROM anyway, so I can easily set this property enabled by default with no need for root.