Open Source Software Community - it's about ethics in Code of Conducts

DavidS877 said:
I assume you're saying that because only satan could have come up with Token Ring.
(Or IBM, same thing really)
Click to expand...
There's actually an RFC for it. There's also a joke RFC for TCP/IP over Carrier Pigeon (which may unironically be a better idea).
 
Ed Special said:
I mean, you joke about it, but tape is far from dead in IT, especially with LTO being an open standard and being capable of storing, from what I'm reading here, about 30TB on a device around the size of a 3.5" HDD.
Click to expand...
Yea, tape still reigns supreme for enterprise use and backup.
If money is no object the highest density these days is probably MicroSD cards.
Apparently Sandisk now has a 4TB MicroSD,
Assuming a 50% packing for the size one LTO tape looks like it would fit 600 MicroSD cards. At 4TB each that's over 2PB.

Getting the data onto 600 MicroSD cards so you can put them in a station wagon is left as an exercise for the reader.
 
Last edited:
DavidS877 said:
Getting the data onto 600 MicroSD cards so you can put them in a station wagon is left as an exercise for the reader.
Click to expand...
3d printer parts for a tape library style machine to organize/autoload the cards. But there's not room for a barcode on the edges, not sure how to label them while keeping them nicely packed.
ts4500open.webp
 
DavidS877 said:
Never underestimate the bandwidth of a station wagon filled with tapes.

Yes, I'm old. My lawn, something something.
Click to expand...
Someone's done the calcs about the bandwidth of a van or truck loaded with SATA or SAS drives. At a certain point it becomes far more practical than simply setting up a MPLS or the like and saturating it for days or weeks on end to do a remote sync.

If you're just going for raw throughput and want to discard the practicality of transfer limitations, microSDs would probably be your best bet.
Just with some napkin math and checking the specs via Wikipedia:
microSD: 165 mm^3 volume
3.5" disk: 387438 mm^3 volume
That means in place of one 3.5" you could have around 2348 microSD cards if you stacked them properly. Estimate a few less for variations in thickness and whatnot, call it 2300.
Largest microSD commonly available is about 2TB, so that means you could do over 4000TB in just pure, raw capacity, in the space of one 3.5".
Of course, throughput and the physical labor and time to swap them in and out of readers would be absolute ass. Total ass-pull figure, but I'd bet that would give worse throughput than the regular vehicle full of 3.5"s.
Ed Special said:
I mean, you joke about it, but tape is far from dead in IT, especially with LTO being an open standard and being capable of storing, from what I'm reading here, about 30TB on a device around the size of a 3.5" HDD.
Click to expand...
Tape is still super common for backups. Running backups to tape libraries and shipping them off to Iron Mountain or the like is still quite common amongst bigger companies.
 
Angie Wormwood said:
Someone's done the calcs about the bandwidth of a van or truck loaded with SATA or SAS drives. At a certain point it becomes far more practical than simply setting up a MPLS or the like and saturating it for days or weeks on end to do a remote sync.
Click to expand...
There's a reason for AWS Snowball. Although apparently they're phasing it out. Apparently 210TB.
Azure has Data Box for up to 525TB for the small ones and 800TB for "Databox heavy"

AWS used to have a tractor trailer solution too. 100PB in a container.

Looks like AWS now has locations where you can drive your station wagon and plug into their network at 100Gbit. *Starting at $300 per port hour, hope you have a device that can saturate that port.
 
was reading about the tokio-tar thing https://edera.dev/stories/tarmageddon and something caught my eye:

In addition, the Edera fork krata-tokio-tar will be archived to coalesce all efforts with the astral fork and reduce the ecosystem confusion.
Click to expand...
huh, let's check it out.
1 star. ONE.
16 commits, all other people. he has two commits, both version bumps.
lets look at a PR https://github.com/edera-dev/tokio-tar/pull/1
left to sit for 4 months, then merged into the wrong branch.
Identify and reach out to the maintainers of the unmaintained upstream repositories (tokio-tar and async-tar). Neither project had a SECURITY.md or public contact method, so it required some social engineering and community sleuthing to locate the right maintainers.
Click to expand...
i wonder if the retarded fork had a security.md, surely he would have mentioned that https://github.com/edera-dev/tokio-tar/security
Individually contact the maintainers of the two most active forks (astral-tokio-tar and krata-tokio-tar) and coordinate simultaneous patching under a strict 60-day embargo.
Click to expand...
again, one star!
This experience reinforces the importance of defense-in-depth. We are happy to report that due to proactive design in Edera, our own products were not vulnerable to this bug despite embedding the vulnerable krata-tokio-tar. By implementing strong security boundaries and ensuring that vulnerable operations were not used in critical pathways, Edera mitigated the issue before the patch was even released.
Click to expand...
we were not affected, however we immediately archived our repository instead of patching it. lol and indeed lmao.
1.jpeg
the mental gymnastics these retarded fags jump through to try make themselves feel important about a fork nobody even knew existed is staggering.
tl;dr to avoid confusion, we archived our retarded tranny fork that had 1 star. you're welcome open source.

edit; nothing ever changes. https://edera.dev/why-edera
well look who it is! aiadne, another fat and retarded tranny
2.jpeg
 
Last edited:
DavidS877 said:
Looks like AWS now has locations where you can drive your station wagon and plug into their network at 100Gbit. *Starting at $300 per port hour, hope you have a device that can saturate that port.
Click to expand...
That is just ~10GByte/sec which is not really that fast at all. Well, it would be fast for consumer grade hardware/storage to deliver that kind of throughput
but for enterprise grade gear, sequentially streaming at 10GByte/sec off storage is quite slow.

We are talking sequential streaming of large datasets. The easiest type of i/o to make go fast. For the people paying for that service, 100GBit/sec is considered pretty slow and they probably complain that the port speed is a bottleneck.
 
Last edited:
NortelNutworks said:
There was a big thing at DefCon about it and Meshtastic this year. Also people got to learn how fucking retarded Meshtastic's routing and encryption both are. Some of them went to a quasi-commercial thing called MeshCore, mostly in Britbongistan, others are trying Reticulum since both can use the same hardware, but everything is mutually incompatible.
Click to expand...
I looked into this for search and rescue use and the routing was the biggest issue with it which didn't seem like it was going to ever change. I know cybersec people who all bought one of the Lilygo TEchos or TTGOs and they just message one another with it during meetups. I guess it's a novelty if you live in a city and have fiber internet.

Cherenkovblue said:
Unironically carrier pigeons with flash drives would make for an excellent warez distribution system.
Click to expand...
It would actually be worse unless you had a pigeon trained for each person you were sending to and maintained them which is a lot of work since they get water at one loft and food/a mate at another. They also are sensitive to carrying loads.
 
You must log in or register to reply here.
Back
Top Bottom