Boof
Yes, it’s a full 24 hours, but a library doesn’t use 24:00:00 to represent the last hour, it’s 23:59:59. Once it hits 24:00, it rolls over to 00:00:00.
Hence my initial error of answering 23.
It’s not valid, but I don’t edit out erronous answers because I believe all data should be preserved, no matter how dumb it makes one look.
Pseudocode and/or a variant of lua.
Most date libraries count to 23h 59m 59s then roll over to 00h 00m 00s. So the answer is 23 hours, not 24.
Edit: I’m big dum dum. It’s asking string length of “Monday”, thus 6.
I wash mine when it starts growing mold. So anywhere from every 3 years to every 6 years.
See, capitalism is good!
When it’s imploding on itself, that is.
Adding an asterisk on the *this particular thing happened quick.
I assume it would, but I don’t know, OP got the statistics.
E: OP had a link, it’s pretty fast drop.
Doubt it, that’s usually just a single command on the top level domain. Everything gets kicked out at once.
Edit: Also, suppo.fi also seemed to be down for a bit, and it’s probably in DE hetzner datacenter.
I was thinking it’s only spam servers, but it might actually just be downtime for hetzner or something.
Instances do not get banned on lemmy. You can run any kind of an instance.
That said, part of this could be providers pruning “fake customers”, aka spammers, scammers, etc, who “paid” for their servers with stolen CC and SSN.
Edit: Someone up to making an uptime map for Lemmy, placing servers on a map based on where they report originating at? This could help seeing if a specific datacenter has downtime.
The good ol fashioned,
<center><div>hecc</div></center>
div {display: inline-box; text-align: initial}
Youtube, as in the entire site, is an advertising platform.
Everything the user does is sold to the highest bidder.
Video ads make pennies compared to everything else.
You can actually just stream media files sequentially via torrents.
It only needs couple* seedboxes by Google to seed the torrents.
Hashing on client side is both more private, and secure. All the user ever submits is a combined hash (auth/pubkey) of their username + password.
If the server has that hash? Check the DB if it requires 2FA, and if the user sent a challenge response. If not, fail the login.
Registering is pretty much the same. User submits hash, server checks DB against it, fail if exists.
Edit: If data is also encrypted properly in the DB, it doesn’t even matter if the entire DB is completely public, leaked, or secured on their own servers.
Argon2 is the best (secure) crypto currently.
That said, adoption is slow, Bitwarden only recently implemented it for example.
That said, due to Argon2 being security-oriented, the recommended settings for it are pretty heavy.
Well to be fair, if they’re hashing serverside, they were doomed to begin with.
But yeah, there’s a lot of ways to DDoS, and so many tools that just make it a 1 button click.
Your password could also just be a long, unique sentence, without any excessive special characters. Maybe even a poem.
Like "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum eu leo eu nibh efficitur viverra. Integer lacinia tortor est, quis aliquet tortor varius sed. Sed dapibus vel turpis at suscipit. Nulla consequat orci in nibh dapibus sodales. Phasellus at arcu ac dolor suscipit pretium. Curabitur sit amet justo sit amet ipsum scelerisque accumsan ac ac nulla. Nullam accumsan lorem sagittis iaculis varius. Nullam convallis nisi ante, id congue diam tincidunt vel. Aliquam sed iaculis mauris. Nam leo nisi, consequat sed sodales non, tempor vel ante. Nunc eleifend vulputate turpis bibendum bibendum. Morbi nec massa in mi sagittis lacinia id ut metus. Maecenas gravida mi vitae lorem laoreet sagittis. "
That’s alot of common characters and words; yet, it’ll take centuries to crack.
That’s a misunderstanding of DDoS. 0 byte packets are actually worse than large packets.
Which is why most DDoS (at least was) is extremely slow 0 byte requests until the server throttles/crashes under the number of requests.
E: Consider this. Are you more likely to throttle a bandwidth of terabytes/petabytes with couple million 1gb requests; or break it entirely by sending >4294967295 0 byte requests that effectively never stop being requested from the server?
Old Steam calling.
Website and Client used different password rules, what worked for the other didn’t in the other.
I have two states.
0 equals “I have no idea what I’m doing”. 1 equals “I have no idea why this works”.
Binary ops withstanding.
It’s more so lucky that there was someone diligently doing that. It could’ve easily gone unnoticed had there not been someone like him.