I have been looking for a new contract for a while now, because my dsl is shit (thanks to my landlord). But all new cable contracts I can find are NATed (ecxept buisness contracts).
Fair, it is a lot harder, but possible (you could vpn your traffick through a vps).
Actually one of the reasons I have not changed my terribly slow contract yet.
Not necessairly. In Germany CGNAT is quite common. So if one of OPs devices routes via IPv4, the traffic will be routed to the carriers public facing router. I would not consider that local as it physically leaves the cables you control.
Does your provider give you yoir own (not necessairly fixed, jus no one else having it simultaniously) IPv4-Address?
Some keywords to look out for wrt that are NAT, or DS(dual stack)-lite.
I think I was a bit unclear on that, I meant uncompressed rips as in I ripped the relevant media to unkompressed mkvs, I didn't save the entire disk dump.
I also have mostly such rips, but also a bit of media from other sourches ™ which is already compressed. So I suspect my results would be even worse.
Really?
My banks use the best 2fa I've seen so far. You have a card-reader which generates a code based on some input values related to the transaction and the physical chip on my bank-card.
(Although they have been pushing PuhsTan (app on phone) a lot recently :/)
why couldn’t you compute p/q < r/s by checking ps < rq?
That's what I meant by scaling the fractions. Tbh I kind of forgot that was an option and when I remembered I had allready written the part about comparing floats so I just left it in. But yeah, encoding lengh might be a killer there.
You could also avoid reducing fractions the same way. Like I don't neecessairly need my fractions to be reduced, if I am just doing a few equality comparisons per fraction. Of course I would have to reduce them at some point to avoid exceding the encoding lentgh in the enumerator and denominator when there is a representation with a short enough encoding available.
I think the bigger problem might be the missing usecases. As another user mentioned, this would still only encode rationals perfectly (assuming no limit on encoding lengh). But I cannot see many usecases where having rationals encoded percisely, but irrationals still with an error is that usefull. Especially considering the cost.
maybe we could solve this by prohibiting the end user from adding or multiplying numbers
I' assume its because implemenring comparisons can't be done efficiently.
You'd either have to reduce a fraction every time you perform an operation. That would essentially require computing at least one prime decomposition (and the try to divide rhe other number by each prime factor) but thats just fucking expensive.
And even that would just give you a quick equality check. For comparing numbers wrt </> you'd then have to actually compute the floating point number with enough percesion or scale the fractions which could easily lead to owerflows (comparing intmax/1 and 1/intmax would amount to comparing intmax2/intmax to 1/intmax. The emcodinglengh required to store intmax2 would be twice that of a normal int... Plus you'd have to perform that huge multiplication).
But what do you consider enough? For two numbers which are essentially the same except a small epsilon you'd need infinite percision to determine their order. So would that standard then say they are equal even though they aren't exectly? If so what would be the minimal percision (that makes sense for every concievable case? If not, would you accept the comparison function having an essentially unbounded running time (wrt to a fixed encoding lengh)? Or would you allow a number to be neither smaller, nor bigger, nor equal to another number?
I googled around a bit and it seems the main concern is being seperate sowftware-wise, not mainly location wise (although thats a nice side effect). So mainly avoiding fun stuff like https://m.slashdot.org/story/112253.
I am just repeating a commonly used phrase with that tbh.
I would Imagine it comes from the fact that a backup also safeguards agains other failures by creating more distance between the Copies. If you are hit by a ransomware attack Raid wont be much good. If your PSU sufers a failure, it might cause an overcurrent/voltage in both hdds.
If you accidentally delete something it will be deleted on both drives, etc.
Whrere are you from?
Because in Germany it is really common.
I have been looking for a new contract for a while now, because my dsl is shit (thanks to my landlord). But all new cable contracts I can find are NATed (ecxept buisness contracts).