r00ty

Yes, came to say the same. It’s very easy to get a voip number in most countries. But many places that want to use it for ID purposes (finance etc including paypal) will know the voip allocations and block them.

I would very much agree here. I’ve (admittedly mostly server side) been using linux for around 30 years now. But I’m still dual booting on my desktop. There’s just a few things that will still only work in Linux, and also if I break things I can go to windows if I need to do something “right now”

Dual boot gives you the option of, if you have the time trying to make something work in linux. But, if you don’t have the time, just boot to windows and do it.

How I do things, is I have drives that are shared between both OS (I use btrfs since there is a windows driver and, so far (around 3 years) I’ve had no corruption problems. But you can share ntfs too and a boot drive for both. But, it’s not a requirement.

Also yes, it is quite easy to break a linux install. It’s not really because Linux is bad. It’s just because you have so much choice in which drivers to use, which desktop environment (and even the components that make it up) that it’s easy to accidentally select some combination that doesn’t work and you end up with only a console to fix things from.

I like that the OP is choosing Mint. I’ve not used Mint, but from all I’ve seen it looks a real good option for someone starting into Linux from no experience.

/mnt/shared/Development or E:\Development depending on which operating system is running.

Not in home mainly because I use the same directory in windows and Linux.

I recently made a new linux install (to replace my constantly breaking, likely due to my own doing Manjaro install). I went with Cinnamon initially, but in order to try out Wayland, I moved to KDE plasma.

I’m on NVidia, with two different resolution screens. Which causes occasional problems. But overall it’s fine.

I’m probably a bit further to the right than most on the fediverse with this opinion but…

I think, once you have been informed of someone’s pronouns, it’s flat out rude to not use them. I don’t know if it’s a banning issue but that’s for the moderators on your instance to decide or the instance the community is on. Even if you don’t agree with someone’s lifestyle, it’s just polite to address people the way they’d like to be addressed.

But surely there’s a difference between intentional misuse and accidental. I think banning someone for not looking up someone’s pronouns before a public interaction seems like pushing things a bit far here. I certainly am not checking such things. But, then in general when online I will use gender neutral wording because frankly, for online interactions someone’s rarely information that matters for the interaction. I don’t really need to know.

My view is, I think it is almost always clear when someone is being malicious and thus transphobic and when someone makes an honest mistake/did not know better. We, as a whole, really should be differentiating between obviously malicious and non-malicious cases.

My first ever international business trip (in the late 90s) was to Skovde, and that was for software development reasons. So the town has a long history for it.

It’s a nice place too with very nice people.

Technically, no. The last few have been significantly below either measure of inflation. So in real terms, I’ve had a wage cut!

Raises where you work are still based on merit? Damn!

I’ve used IPv6 at home for over 20 years now. Initially via tunnels by hurricane electric and sixxs. But, around 10 years ago, my ISP enabled IPv6 and I’ve had it running alongside IPv4 since then.

As soon as server providers offered IPv6 I’ve operated it (including DNS servers, serving the domains over IPv6).

I run 3 NTP servers (one is stratum 1) in ntppool.org, and all three are also on ipv6.

I don’t know what’s going on elsewhere in the world where they’re apparently making it very hard to gain accesss to ipv6.

But I’ve never played smash. What does that mean? Oh! Oh.

There’s a certbot addon which uses nginx directly to renew the certificate (so you don’t need to stop the web server to renew). If you install the addon you just use the same certbot commands but with --nginx instead and it will perform the actions without interfering with web server operation.

You just then make sure the cron job to renew also includes --nginx and you’re done.

Here’s what I think. Both opinions are correct.

Rust is sufficiently different that you cannot expect C developers to learn rust to the level they have mastered C in order to be working at the kernel level. It’s not going to happen.

I don’t really know too much about rust. Maybe one day I’ll actually mess around with it. But the one time I looked at a rust git repo I couldn’t even find where the code to do a thing was. It’s just different enough to be problematic that way.

So I think probably, the best way IS to go the way linus did. Just go ahead and write a very basic working kernel in rust. If the project is popular it will gain momentum.

Trying to slowly adapt parts of the kernel to rust and then complain when long term C developers don’t want to learn a new language in order to help isn’t going to make many friends on that team.

I mean, while they can block most things, to give people a usable experience they’re going to allow http and https traffic through, and they can’t really proxy https because of the TLS layer.

So for universal chance of success, running openvpn tcp over port 443 is the most likely to get past this level of bad. I guess they could block suspicious traffic in the session before TLS is established (in order to block certain domains). OpenVPN does support traversing a proxy, but it might only work if you specify it. If their network sets a proxy via DHCP, maybe you could see that and work around it.

I did have fun working around an ex gf’s university network many years ago to get a VPN running over it. They were very, very serious about blocking non-standard services. A similar “through” the proxy method was the last resort they didn’t seem to bother trying to stop.

I find anything with that coated plastic over time gets crappy. I still have an old X52 pro I’ve had for probably around 15 years now. In the end I just completely took off the flaking rubber style coating they put over it and it’s now shiny plastic and still going strong.

I also have a G502 that’s 6 years old. It has some worn areas where it’s actively held and on the buttons. I replaced the skates last year and have a spare set. Otherwise, still going strong.

Really not sure why I’d subscribe for something that lasts so long and isn’t THAT expensive to replace.

I’m going to blame the cloud for this. SaaS has got pretty much most software companies into the idea that they can have their cake and eat it with recurring revenue from cloud hosting their services.

This seems to have overflowed into every other market, where they want a piece of that pie.

I’m hoping it’s a fad that goes away. You know how we can make it a fad that goes away? Don’t buy into this shit.

This was normal back in the days of CS 1.5/1.6. People would play at 640x480 on a monitor that could handle 1280x960 because they could drive 640x480 at like 150+hz.

Thanks. That explains a lot of what I didn’t think was right regarding the almost simultaneous failures.

I don’t write kernel code at all for a living. But, I do understand the rationale behind it, and it seems to me this doesn’t fit that expectation. Now, it’s a lot of hypothetical. But if I were writing this software, any processing of these files would happen in userspace. This would mean that any rejection of bad/badly formatted data, or indeed if it managed to crash the processor it would just be an app crash.

The general rule I’ve always heard is that you want to keep the minimum required work in the kernel code. So I think processing/rejection should have been happening in userspace (and perhaps even using code written in a higher level language with better memory protections etc) and then a parsed and validated set of data would be passed to the kernel code for actioning.

But, I admit I’m observing from the outside, and it could be nothing like this. But, on the face of it, it does seem to me like they were processing too much in the kernel code.

That’s interesting. We use crowdstrike, but I’m not in IT so don’t know about the configuration. Is a channel file, somehow similar to AV definitions? That would make sense, and I guess means this was a bug in the crowdstrike code in parsing the file somehow?

I think it’s most likely a little of both. It seems like the fact most systems failed at around the same time suggests that this was the default automatic upgrade /deployment option.

So, for sure the default option should have had upgrades staggered within an organisation. But at the same time organisations should have been ensuring they aren’t upgrading everything at once.

As it is, the way the upgrade was deployed made the software a single point of failure that completely negated redundancies and in many cases hobbled disaster recovery plans.

Yeah, but they’re not. That’s the modern world. But also even if it was a web server there’s usually ways to advertise the IP for the app to connect to. I’ve seen other stuff do that. So getting an IP is easy. Once the app knows the IP and if you really want to allow connections from outside to your IOT devices (I wouldn’t) it could remember the IP and allow that.

You really don’t need to give a fixed IP to everything. I think I’ve given 1 or 2 things fixed IPv6 IPs. Everything else is fine with what it assigns itself.