Yes it is a security issue. But almost everything is. You can make it secure enough with the right policies. However it overall increases the attack surface of your application and has a greater chance that you missed something or miss configured the policies. So many firebase apps have been hacked because of miss configured access to the database.
So it puts more work on you to get things right.
In an open letter to the prime minister, Labour MPs said “successive governments” had done “too little to protect young people from… unregulated, addictive social media platforms”.
They are focusing on the wrong thing. The problem is not young people access it, it the unregulated and addictive parts. Those affect everyone not just the young. Regulate the addictive behaviours of these platforms and protect everyone. Don’t just force ages ineffective age verification that harms the privacy of everyone.
I treat warning as todos. Fix them all before I release something. I would only ever disable one if I know for a fact the warning is a false positive.
I would question why you are seeing so many warnings you are not sure about? If you keep on top of them you really shouldn’t have that many. Marking them all as allowed with a Todo comment feels just like you are burying you head in the sand.
I would leave them all there to keep nudging you to investigate and remove them. Hiding them behind a Todo will just mean you will ignore them. And warnings are important, they very likely point to a problem, even if that is just the code could be simpler. It is rare they are true false positives.
One source said officials had discussed including a virtual private network function to make a user’s traffic appear to originate in the U.S. and added that user activity on the site will not be tracked.
Somehow I don’t believe that last part 🤔
Free speech for him, not for you.
I don’t fully believe this is purely an AI agent. Not after the moltbot incident raised how many humans where responsible for the posts on it. It just seems to be an attempt to make LLMs seems more autonomous then they actually are. It may have been written by an LLM, but I bet it was directed by a human trying to stir up drama.
It’s both. If busses are cheap and reliable more people will use them. If more people use them they are cheaper to run. Which creates a positive feedback loop to a point.
You can make busses cheaper for people by other means though - like council/government substitutes or running at a loss for a bit. You need to do something to get more people, you cannot just force people to take the bus before doing anything else.
Disposable/single use vapes have been illegal to sell in the UK since the first of June this year. This is the kind that the article is talking about litter everywhere as people just throw them away when done rather then refilling them. Vapes themselves are still legal to sell. It has only been a couple of months though so likely will still see people using them for a bit but I would hope to see their use start to tail off quite quickly now as you should no longer be able to buy them.
BREAKING NEWS: Girl gets home safely after night out. More at 11.
Yeah I don’t like this either. So many chances for a mistake, be in the wrong dir, file misspelled, something not cloned correctly or anything else not setup as you think it might be and suddenly the package manage does something you don’t expect (like try to install globally rather then in a project or vice versa).
For a lot of things I would rather have something web based than app based. I hate having to download some random app from some random company just to interact with something one time. Why do all restaurants, car parking places etc require apps rather than just having a simple site. Not everything should be native first IMO.
I wouldn’t debian stable is no better than any other mainstream distro. Worst in some regards as it tends to have really old versions of things. If that sounds nice to you then go for it. But it is not the default choice or recommendation for most people.
There is also little reason not to try out different ones to compare if you want to. Nice to see what they are like for yourself if you have the time to.
I am not afraid of some tech journey, but even though arch seems the coolest, with Wayland, kde, hyperland customization, i am not confident enough to use it for work.
The only way you will gain confidence in it is to try it out. But also, most distros use wayland these days and it is more up to the desktop environment you use rather than the distro you use. hyperland is a wayland compositor and is in the repos of most if not all major distros. You should be able to install it on anything really. You can replace the desktop environment or install multiple ones side by side if you want to on just about any distro. The biggest difference between them is which ones they come with by default. But really if you are looking for a highly customized experience then Arch tends to be the way to do as you have less extra fluff you have to remove or work around when getting the system exactly as you want it. The hardest part of Arch is installing it the first time. Really after that it is not any harder to use or maintain. IMO it is easier to maintain as you have a much better understanding of how you set up your system as you are the one that set it up to start with.
I heard it can completely crash your system if your a noob.
You can break any distro if you mess with things. The only big difference is Arch encourages/requires more messing around at the start then other distros. And IMO is easier to fix if you do mess things up - you can always just boot a live USB and reinstall broken packages or reconfigure things without needing a full reinstall again. You can basically follow the install guides again for the bits that are broken to fix just about anything. And that is only if you break something critical in booting. In my early days I broke (requiring a full reinstall) way more ubuntu installs then I have ever broken my Arch ones later on. It is really just about how much you want to tinker with things and how much you know about what you are tinkering with as to if they will break or not rather then what base distro you use.
And you can always try the install process and play around with different distros in a VM to get a feel for them and learn what they are like. So don’t be afraid to try out various different ones and find the one you like the most. Your choice is never set in stone either. Just ensure you have good backups of everything you care about and the worst that will happen is you need to reinstall and restore your backups every once in a while.
but my main needs are not really discussed
…
So in essence i need something stable that is relatively easy to use and has great ue5 and gaming perf.
That is probably the most common set of requirements people ask for. In reality, with a few exceptions, there is really not that much difference between distros given those requirements. UE5 is newer so the biggest change there would be that you might find distros that ship newer versions of stuff might run it slightly better then distros that ship older software. In practice I think it has been out for long enough that you wont see much difference unless you want to play something new on the day of release (but these days those are all buggy messes anyway… not sure your choice of distro will make as big a difference as waiting a few weeks/months for the initial patches to rollout).
Remember, all distros are essentially based off the same software, the biggest difference being what desktop environment they ship with and what versions of software there ship (and how how long they stay on that version). By far the biggest difference you will see if what desktop environment they use and all distros essentially package the same set of desktop environments - each might come with different ones by default but they typically contain all the popular ones in their repos.
i need something stable… great gaming perf
In particular these two points. Do you know what you are asking for here? These are the most bland and wishy washy requirements. Everyone wants something stable and fast, never seen anyone ask for something that crashes all the time and is slow. But worst these tend to be on the opposite ends of the spectrum in terms of requirements, if you optimize for one you tend to trade off the other.
Even stability has multiple meanings. In terms of crash stability you will find all distros to be about the same. No one distro wants to ship buggy crashy software. But at times they do. And it is really just the luck of the draw as to when this might happen to you based on what software you use, how you configure your system and what hardware you have. Some combinations just don’t work for some weird reason and you wont know until you hit it. This is why you hear some people claim one distro is a buggy mess while some other one is rock solid while someone else argues the exact opposite. All main stream distros are just as good as any other in terms of this and you are just unlucky if you ever do run into that type of issue. The biggest problems in this regard tends to be when a new major version of something comes out - but like with gaming it can be beneficial to wait a few months for any issues to be patched before jumping to the latest big distro version.
The other side of stability is API stability - or the lack of things changing over time as new versions of stuff get released. There are two main types of distros in this regard, point release distros which freeze major versions of packages between their major releases so you wont get any new features during the release cycle that version of the distro. Then you have to deal with all the breaking changes from newer versions of software once every so often when a new distro version comes out. Vs rolling release distros that upgrade major versions constantly and so generally follow a lot closer to the latest versions of things than point release distros. Really the big trade off here is not if you encounter breaking changes.
Any distro will need to deal with them at some point, the choice is how often you deal with them. You can wait years on the same version of a point release distro and only need to deal with all the breaking changes once every few years, or once every 6 months. Or you can deal with things as they come out with a rolling release distro. But while it might sound nice to only deal with it every few years it also means you need to deal with all the changes at once. Which can be much more disruptive when you do decide to. Quite often I find the slower upgrading distros are better off with just a full reinstall on the latest version than upgrading from one to the next. Personally I prefer dealing with small things frequently as they tend to be easier to fix and less disruptive over longer periods of time. When I was running kubuntu I used to end up reinstalling it ever 6 months as the upgrades never worked for me (though this was a long time ago), but my oldest arch install lasted probably probably 5-10 years or so.
And at the same time how frequently you get the latest versions of things means you get any performance optimizations and support for newer hardware or newer games as well. But also any bugs or regressions. It is a double edged sword. Which is why stability and performance tend to be a leaver you can tune between rather than two separate things to can achieve. Just like overclocking, the more performance you can get out of a system tends to result in the system becoming less stable overall. Everyone wants the most stable and fastest system, but in reality everyone has a different limit on how much or what types of stability they are willing to give up on to achieve different levels of performance.
But out the box, you will find most distros to be very much within a couple of % of each other and which is fastest will vary depending on which games you want to play and what hardware you have. But they all tend to have quite a bit of head room to optimizes for specific use cases as they all are optimizing for the general use case which is typically just trading off performance in one thing for another. But again, we are talking about tiny difference overall.
Random programming certificates are generally worthless. The course to get them might teach you a lot and be worth while, but the certificate at the end is worthless. If it is free then it does not matter too much either way, might be a good way to test yourself. But I would not rely on it to get you a job at all. For that you need other ways to prove you can do the job - typically with the ability to talk about stuff and having written some real world like application. Which a course might help you do to.
There is in this case, and why Linus did accept the patch in the end. Previous cases less so though which is why Linus is so pissed at this one.
The reason for this new feature is to help fix data loss on users systems - which is a fine line between a bug and a new feature really. There is precedent for this type on thing in RC releases from other filesystems as well. So the issue in this instance is a lot less black and white.
That doesn’t excuse previous behaviour though.
Only 40%? Would have thought it would be much higher. Don’t more projects generally fail then that without being in a bubble?
No. But only because I switched to helix. I have used vim for a lone time before that. Only having vim on a system is fine. Far worse is only having vi. Which is almost like vim but missing a lot of useful things.