sep

joined 1 year ago
[–] [email protected] 6 points 1 month ago

Ipv4 is not even ipv4 compatible. You use nat to translate one type of ipv4 into another to talk on the internet. Ipv6 is using nat in the same way.
The problem is that ipv4 is not forward compatible ( naturally ). So ipv6 can talk to both, ipv4 only to ipv4.

[–] [email protected] 3 points 1 month ago (3 children)

That must have been a concerted effort. The amount of anti-mozilla posts and comments that totaly permeated everything for a short while, was very suspicious.

[–] [email protected] 5 points 2 months ago (1 children)

As well as the whole firefly series. Watches them all annually.

[–] [email protected] 3 points 2 months ago (1 children)

Bookmarking this. How about a photo library category under photos and grafics

[–] [email protected] 3 points 2 months ago

Thank you. Was going to suggest matrix/elements. But you explained it better ;)
It has really improved the last years. Especially the e2e encryption key sharing, and verfication system vs what was before.

[–] [email protected] 4 points 2 months ago

They are not rapidly moving.. no wonder you miss them

[–] [email protected] 9 points 2 months ago

I install molly-guard on important machines for this reason. So fast to do a reboot on the wrong ssh session

[–] [email protected] 2 points 2 months ago* (last edited 2 months ago) (1 children)

Everybody knew exactly what kilo mega and giga ment. when drive vendors deliberatly lied on there pdf's about their drive sizes. Warnings were issued: this drive will not work in a raid as a replacement for same size!!. And everybody was throwing fumes on mailinglists about the bullshit situation.

But money won, as usual.

Source: threw fumes!

[–] [email protected] 5 points 2 months ago (1 children)

Helldivers2 vs bots on lv10... dead in seconds. pretty screwed.

[–] [email protected] 23 points 2 months ago

People have experience.

[–] [email protected] 1 points 2 months ago

I think true, but most discs i have, has digital audio.

view more: next ›