String -> immutable string
StringBuilder -> mutable string, optimized methods for string modification3,833 karma · joined April 2, 2013
String -> immutable string
StringBuilder -> mutable string, optimized methods for string modification > Free Pascal strings are as close as you get to magic, compared to C/C++.
Not your point of reference, but Java and C# treat strings as immutable objects too. > just using PCI passthrough
On a laptop, I never got a working setup where I could attach/detach a modern nvidia card from host linux. So something that can do without is better.
But intel SRIOV is a thing as well, which should be the secure alternative.Caveat: I am no expert on Android.
The most important point for every political faction however is to realize that the problems aren't solved when the current president steps down. The real power that pushes the agenda rest in the hands of a loosely connected network of 'think tanks', religious organizations, tech billionaires and media moguls. They are hidden from the public discourse, simply because they are able to manage it, and as such are a formidable opponent.
> We plan to heavily overhaul the VPN implementation to make most forms of leaks nearly impossible rather than continuing to use the current system prone to it.
Thanks, great to hear. Given the slew of bugs you uncovered it seems the Android implementation has some rough edges. Would `pasta` be helpful to you? It allows you to unshare netns and then pass a user-space network adapter inside. https://passt.top/passt/about/ Podman leverages this one as well in more recent versions.Google just closed the ticket, without communicating their plan to deal with it. I just stated that we cannot rule out a possibility of foul play, thereby keeping other options open. Keeping that thing in mind which is better known as "the reality" I would be a little bit more wary about Google's stance towards privacy than I would be about GOS though. The difference in how these parties are handling this issue is already a tell.
I have a hunch this leak is bound to wifi hardware only, for details: https://supuk.ch/papers/android-natt-keepalive-vpn-bypass
"Read the relevant design documents under docs/ before changing architecture."
makes me think that developing 'graphify the tool' and using 'graphify as a tool' are mixed up in the same document? How does an LLM keep track of both this gigantic skill and the user development problem at the same time? > A proper fix would require changes in the Android system. The researcher who discovered the leak has reported the issue to the Android Vulnerability Reward Program, but according to the researcher the issue was closed without action. This issue is not public, but based on this information we deem it unlikely that Google will do anything about it. GrapheneOS is aware of the issue and are working on a fix.
If the account given by the researcher is correct, we cannot rule out that Google deliberately introduced or wanted to keep the leak in place. > i demonstrated replacing _all_of them at once, not replacing them each by hand.
Not really, that is search and replace. IDE's do typesafe refactoring. If you change the Find method in class A, you should only change occurences of x.foo(), where x has type A. You shouldn't accidentally change all B.find()'s.That is my advice for everyone completing their first Python tutorial: learn a typed language next if you aspire to do serious work. It also saves you writing many manual tests that you had to make otherwise, as the compiler makes that superfluous. Plus your IDE becomes a superpower.
> complaining about LLM-assisted writing.
I urge you to read the article. "assisted" is doing a lot of load-bearing work here.
The problem is not just the writing style, but rather that it doesn't make sense at all.Take the example for PGQ. "Two ordinary tables, one graph on top of them:" The example makes zero sense, because the fucking tables aren't even there. You can't be lazier than writing a prompt: "please make a blog post about the new PostgreSQL release, and give code examples for each new feature", then ctrl-c, ctrl-v the output.
You can write articles with the most horrible style if you want, but this level of disdain for readers is beyond belief.
The headline feature (property graphs) has a better example here in the official docs: https://www.postgresql.org/docs/19/ddl-property-graphs.html
- Signal. high priority channel, checked daily
- $PrivacyHazardApp. low prio, checked with steadily increasing intervals.
Make sure you communicate those intervals in advance, have them in the footer of every message you sent on $PrivacyHazardApp. Average Joe needs lots of patience and lots of education.
I understood from other comments that RCS is the default communication channel in N.America an I can sort of see why you want to give people a somewhat less worse option here than Google's Messenger. But RCS should not be the default imho, because lazy people gonna be lazy. So I hereby endorse you to gently push newcomers towards a safe and privacy friendly default by pre-installing Signal or whatever meets the bar and give it a prominent place.
I guess it will make your life much easier if you wouldn't have to restrict yourself that much.
> RCS isn't an open platform in practice. It isn't even as open as SMS/MMS. It heavily depends on proprietary Google and carrier infrastructure in practice. We can start by replicating Google's approach and then we can work on only using carrier services for carriers where it's actually supported.
What is the point of RCS though? It seems to be strictly inferior to Signal. It seems a Google product meant to serve Google. I wouldn't hate it if GrapheneOS would totally ignore RCS. I fail to see any value in it, but maybe I am lacking information(?) > Google did something in the mid-2000s that nobody thought was possible: they created a browser and got mass adoption without having a platform. People willingly downloaded it
I have to say that things weren't so bright. You were correct that Google had no platform, but Google never had any qualms about doing illegal things. To start with, the average person had no idea what a browser is, they had 'the internet' installed on their computer. Someday 'the internet' had changed on their computer.How? Well, remember that Windows had (or: has) no equivalent of Linux software repositories. People browsed the internet and downloaded software (including malware) from big download sites. Google sponsored those sites and had google chrome injected in every installer. Think about that when Google talks about 'sideloading Android apps'. People just had no idea, but all of a sudden their internet had changed.
Secondly, Google hijacked other browsers by urging people on the Google homepage to install Google Toolbar (if I remember the name correctly) This provided a different way to spy on user's browsing activity, plus it provided a springboard toward a full chrome install.
Thirdly, Google pushed users aggressively to download Chrome across all of their products. I remember Google telling me on every page that my browser was not Chrome.
Chrome was never an offer from a benevolent party, on the contrary. I have been talking against many a deaf ear that it isn't that smart to install an ad viewer from an ad company, even if the first page load feels more flashy in Chrome. I am glad that people finally are starting to wise up, better late than never. Especially the stupid excuses I heard from tech people that insisted Chrome is the only way has learnt me that tech people aren't as smart as we think they are. Don't take that personally.
We now have to free the internet for the average Joe. That won't be easy if we can't evade consequences from crime as Google can.