r00ty

1999. I was part of the ADSL trial in the UK and have been on a form of broadband ever since.

Resistance alone doesn’t cause heat. Drawing current through resistance causes heat at the point (or points) of resistance. Which is why I clarified that it’s not likely so much a problem on small loads.

This is why resisters come in different physical sizes. Because they have differing abilities to dissipate power as heat.

A good example is of dummy loads in radio use. Which needs to dissipate the power output of a radio. That can be anything from milliwatts to a kilowatt. Up to probably 50w they will have a basic heatsink. I’ve seen huge drums filled with oil as 50ohm resisters to handle up to a kilowatt of dissipation.

Yeah, I think in this case there’s a lot more tiny conductors sharing what can add up to pretty high current loads on PD connections. Adding extra connectors adding resistance to low (5-20v) voltage high current connections is adding an extra failure point and increasing resistance on the whole cable run.

Not inherently unsafe, but just not a good idea to promote because you know someone will try to run a 200w charging cable for 30m with like 5 connected cables.

I think a lot of people are mostly on the money here. It’s to do with resistance. Now, I’m not a qualified electrician, but I’m an amateur radio license holder and a lot of what you learn for that is applicable here.

The main problem as many have said is resistance. This comes about from both the length of the conductors but also from every plug/socket connection adds resistance. Also in the case of the non extension socket multipliers, as you add more the weight bearing down would also likely start to make the connections less secure causing more resistance and possibly adding to the problem through arcing.

Now the resistance alone on small loads likely wouldn’t be a huge problem. But if you had a large enough load (specifically at the end of the stacked connectors/extensions), or a fault that caused a larger than expected load the current would cause the resistance to generate heat.

There’s a lot of ifs and maybes involved, but really why do it? There’s really no real world situation to need to have a dangerous amount of extensions like this though.

For larger loads here in the UK there’s some very specific other concerns when dealing with ring mains. But really you’d need to do really weird/unusual things for that to become a problem.

Aha OK. Then yeah I misread it. That makes a lot more sense.

How I read it, they want to use a domain to validate the use of a handle. With the huge variety of tlds the same domain part could be registered many many times.

If I did misunderstand, then sorry. It’s how I read it.

There’s a lot of tlds. Do they explain the policy when two people have the same domain on different tlds? I mean oldest registered makes sense to me. But not without problems.

This is something I do on my new (Samsung) phones for the last 2 phones and this latest one I also turned off fast charging. On previous phones it was capped at 85%, current ones seem to have several options with the highest “saving” being to charge to 80%

If I’m going out for the day and need the full charge I turn it off for the duration and if I need a fast charge I turn that back on.

By and large though most of the time I keep it off. Seems to make the batteries last a bit longer. Too early to tell on the current phone though. Only a year old. I generally keep phones for around 4 years.

I used to do the opposite on the old nicad batteries phones had in the 90s. I’d carry a spare fully charged one, run the main one down to zero, swap them and then charge it to full. This made a huuuuge difference though.

deleted by creator

We can see it ourselves. We use rabbitmq for incoming (and maybe outgoing, it’s been a while since I looked at how it is) federation. So, you can see the queues there. For incoming (from rabbitmq) and outgoing there are also queues (symfony messenger) and these handle failures and can be configured and can be queried.

After the upgrade I just took the default configuration again (because it seems queue names changed). But I used to have various rules setup in rabbitmq for retries and it took a fair few tries before the messages ended up in the proper “failed” queue (which needs manual action to retry). Some items you eventually need to clear (instances that just shutdown, or instances that lost their domain for example). They will never complete.

But it’s not exposed in any way to my knowledge. Well unless people have their rabbitmq web interface open and without login of course.

I think it must be hit/miss. Because I think those edits I made would have gone from my instance to world and then from world to .ee, and it was happening within seconds.

So, presumably random stuff is being dropped or delayed?

That makes sense. So it’s showing me world’s federation with me and not the other way (since I’m not sure such info is available on mbin)

Wait, how do they get that data remotely? I was looking at my instance vs world and I saw there’s like the +1 hour from a week or so ago when I upgraded to latest mbin lol.

I guess they’re looking at common activities and when they appear on each?

Looking at incoming request. .world is working OK for me. They seem to be batching stuff like I’ll get nothing for 30 seconds, then over 3 seconds like 50+ requests.

Of course I don’t know if their queue is backed up and I’m getting delayed stuff. I’d need to stop processing and look into the incoming queue to see what they’re sending.

Bit of an edit. Looking at incoming again I can see under newest items, an entry from world that was 11 minutes old. Oh I have an idea. I’ll see if this edit gets there in a timely manner.

Spoiler alert, it was instant.

Oh ignore me. It’s specifically between those two instances I guess.

That said there could be better ways to show info like this on the fediverse. Except, it’s complicated.

You could be banned on an instance, but also separately banned on an individual community on an instance, or your instance could be defederated from one running a community. Any of which could lock you out in theory.

It’s not as clear cut as closed systems. This is mostly a good thing but for clarity, not so much :p

I did a routine upgrade on my mbin server, where I had an old version with changes I made myself.

Well turns out I upgraded something (probably redis) that broke symfony that broke everything.

So I had a fun afternoon upgrading to the latest mbin version. I mean I needed to anyway but my hand was forced.

Yep sometimes an innocent looking update will change your weekend plans.

Anyways, any reason not to use ssh?

And twitter / x most likely have a similar rule. And musk could have achieved similar by just banning the account.

There’s no reason to give it to Jones. He doesn’t own any of the applicable ip any more. Maybe there’s an argument if he tried that.

Now see, I don’t like it but the simplest thing would be for musk to ban the account right now.

He’s not circumventing anything then. Ownership of the account was transferred, that twitter, a private entity chose to ban it is their business.

It’s not worth arguing about. The website and ip is the juicy thing, being able to make satirical info wars programming and products is where it is at. Maybe, maybe there would be a case if musk allowed Jones to make a new account with the same name or otherwise handed it to him.

No. If valve cancel your steam account, you lose your games and they owe you a big fat zero.

Same goes for all accounts with assets attached.

Sad to say, but in this case it is musk’s platform and his rules.

If he wants to go home and take his ball too. Tough luck.

Doesn’t seem right, but it is legal and already happened on multiple platforms multiple times.

Not a bug! That’s a feature.