r00ty @ r00ty @kbin.life

I'm the administrator of kbin.life, a general purpose/tech orientated kbin

---

Read more

Posts

2

Comments

1,265

Joined

2 yr. ago

/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.

Yeah, but that's just because "nobody wants to work"

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.

Yeah, I'm quite sure it's a deliberate activity to dissuade against private email servers. Keep everyone's email "in the club". Once you've got this much working you need a whole suite of tools to deal with the HUGE amount of spam you need to filter. It can be a hell of a lot.

kbin/mbin does have some mastadonesque facilities. So it straddles the line between threadiverse and I dunno what we call the mastadon side.

IRC was "kinda" federated. You needed to convince a server already in the network to accept your server. But in the early days requirements were quite low.

BBS was not really federated (except Fidonet I guess).

Usenet, I guess it kinda was. But only ISPs were really running NNTP servers. Only they and unis really had the resources to too.

You CAN do the full list of things to get accepted there. But you only need to fail a SINGLE test to get sent to junk mail jail.

To not be put to junk you need all of the following (oh and this can and will change one day and you'll go straight to junk)

• SPF configured
• DKIM configured with valid keys applied to DNS
• DNS secured with DNSSEC, with validated keys passing all minimum requirements
• DMARC configured for domain
• Your mail server NOR the entire network on a DNSRBL. For example right now my mail server is hosted on OVH (moving soon) and it will go to junk, and in the hotmail/outlook headers it makes clear this is the only failure (-0.2 points, enough to go straight to junk mail jail)

Not sure if I missed any there. It's been a while since I set all this crap up.

Well it seems it was more to do with sanctions, if the open letter from one of the chopped developers is to be believed. In which case, I think the right thing is to move the names to contributors (they did still contribute), remove them from maintainers (some maintainers are actually paid by the foundation, I mean not a lot, but some are paid).

I still find it all a little odd. But likely there was a bit of a prod from somewhere higher as to how sanctions should be followed.

Most nuclear enabled countries have nuclear subs. I believe here in the UK our entire nuclear deterrent is based on trident missiles fired from submarines.

It's going to be precisely the reason. If you have a dedicated wire, fibre or copper then the entire available bandwidth is available per connection (one caveat with copper is crosstalk but it is minimal and can be mitigated). With fibre the available bandwidth per strand is huge.

It's so fast that even where there's contention, it is rarely a problem that everyone sharing a part of the connection is downloading or uploading at once. So pretty much most of the times you test, you get the full speed.

With mobile data, the entire cell is sharing a small amount (in comparison) of spectrum. Unlike a wire, the entire spectrum cannot be used by a single tower, a pretty small number of channels are carved out for them. Also because the signals are travelling through the air, there is more of a problem of signal loss and interference to contend with, so the channels very rarely reach the maximum possible speed (forward error correction and reducing bits per symbol to reach a suitable signal to noise ratio both will reduce speed for example.

For upload (which isn't usually much of an issue) there's another problem of guard time between timeslots. When downloading, the cell transmitter transmits the whole time and shared the channel between all users (another thing that can slow things down) so there's no problem of needing a guard time. But when it's separate transmitters (phones) sending there's going to be a guard time between different handsets timeslot and the more active transmit stations there are (phones) the more these guard times add up to wasted bandwidth. Luckily most people are downloading far more than uploading, so it's less of an issue.

I think for these reasons caps are used to limit people from ALWAYS consuming data on the cell/mobile networks and instead using wifi wherever they can in order to keep it fast for those that do/need to.

Therefore there is either missing information (external pressure to take this action) or this is simply an action based on personal judgement.

Looking at the other post about NVidia drivers, I am starting to wonder if western governments (or perhaps just the US) are going after large orgs and suggesting how current sanctions should be interpreted. In which case, not sure I can then blame the Linux foundation, since you know, you don't need government heavy breathing down your neck.

Yeah, along with this I am suspecting there's been a "suggested interpretation" from western governments to large orgs.

And I'll say the same here as I did above. If it was for security, their code is tainted too. It's an arbitrary reaction that is not complete as a solution to anything.

If that were true, surely they'd not trust ANY of their existing work, or at least any done since the Special War Operation. Wouldn't that make sense?

They've left the code, and removed the people arbitrarily. Seems a bit off to me.

You know. I don't like what the Russian leadership and military are doing. I feel like ultimately we're in the cold war era. But you know, at the height of the cold war, radio operators around the world still worked Russian stations.

Yes, there was a very clear policy, neither side talked about ANYTHING beyond their signal report and working conditions (information about radio, power output and aerial basically). At the height of the actual cold war, the individuals were not cancelled like this.

Sanction the leadership, sanction the money, and sanction the military. But the normal people that are subject to the propaganda? I don't understand the benefit in doing this. I also don't see how the sanctions effect an open source project..

Seems a bit weird. Maybe there's information we're not privy to, but on the face of it, just based on what we're seeing. Seems like a very very odd move.

Definitely. And it's actually "We installed a camera in your bedroom, but it's hidden, you cannot remove it. It's enabled but don't worry it's not recording".

I just ideally would like Microsoft to say something. Because at the moment it's super weird to enable it on PCs that it's not meant to run on.

There's been a lot of youtube videos made on the tech side of it. But, like I say they all make a fair point. It's installed, enabled and hidden. But none of them have shown any evidence of it actually collecting data yet.

This arrived in the 24H2 windows update I think it was about a week ago.

To be clear, I installed a new Linux system totally separate to this and just coincidental, and there's still some things I need to use Windows for, so it's not going anywhere soon. But for sure this whole thing is one more reason to be suspicious of Microsoft.

As I said, I am not sure there's any evidence showing it's actually doing anything yet. None I've seen at least.

But, I think there's some very suspicious points that stand out to me.

• Installed by default
• Enabled by default
• Hidden from the user unless they specify the feature by name from command line (listing from command line doesn't include it either). And I wonder if being searchable by name was an accident that will be patched out next time.

If this wasn't going to be anything to do with the recall functionality that has been previously described, then I feel fairly sure they would have posted an announcement about it by now. Silence in general is a bad thing for this kind of thing in my experience.

But, since it's not doing anything now I'm more in a "wait and see" stance personally.

I've found it very interesting. So far as I can tell it's installed and enabled (even on non co-pilot PCs). However I have yet to see or hear of anyone that has found evidence that it is actually running and doing its job (capturing screenshots and creating the database for the AI model).

To me, the fact it's installed and enabled and they've not stood up by now and said "Ooops our bad, it was only meant to be on copilot PCs and we should have added it to the features menu so you can turn it off" just suggests that, the stuff is there and at some point they will flip a switch on ALL PCs to enable it.

It's quite lucky that a week or so ago when I got some new SSDs, I put aside 2TB for a linux boot to replace my old broken previous linux dual boot. Not booted into windows in over a week.

This is exactly what I expected AI to do. Basically if you're a junior developer your work is likely to be checked by a senior.

Instead they will just have seniors use AI and then check that work instead.

It's very shortsighted because you only become a senior developer after being a junior and it will turn off new people to the industry.

But, that doesn't matter to pretty much any large business. They never have a long term strategy (and do not let them have you believe otherwise). They have month, quarter and year only and the importance is in that order except at quarter and year end.

They will destroy their own industry for short term gains and then blame the rest of us when things turn sour.