It sounds to me like the university is using the threat of expulsion to steal or coerce you into giving over your site. I think you just got the best IRL education ever.
This is one of those games that would be great to have the source code for. I’ve seen dozens of people try to do rewrites or reverse engineer the code, but this one got further than most. The author of the original Allycat died a couple decades ago, so that little DOS binary is all we’ll ever have.
That is too bad, Teleport is how I learned a lot of the crypto APIs in Golang. It also provided me with a glimpse into part of openssh which was never very well thought out - signed keys.
Since I was working in an environment where development teams tended to obtain root credentials from CI-CD pipelines and use them to change all the permissions on production servers or fill the storage with database dumps, I ditched teleport, ssh, and logins altogether! We followed the serverless model and there are no logins to any compute resource. The only way to bring data in is via unprivileged ci/cd pipelines or the application's API, the only way to get data out is via stderr or writing to a resource like S3. Nothing runs with privileges, there is no ssh, there are no admin-only access methods. Overnight that eliminated almost everything mysterious or unreproducible. No more permissions issues.
When I did low latency everyone was offloading TCP to dedicated hardware.
They would shut down every single process on the server and bind the trading trading app to the CPUs during trading hours to ensure nothing interrupted.
Electrons travel slower than light so they would rent server space at the exchange so they had direct access to the exchange network and didn't have to transverse miles of cables to send their orders.
They would multicast their traffic and there were separate systems to receive the multicast, log packets, and write orders to to databases. There were redundant trading servers that would monitor the multicast traffic so that if they had to take over they would know all of the open positions and orders.
They did all of their testing against simulators - never against live data or even the exchange test systems. They had a petabyte of exchange data they could play back to verify their code worked and to see if tweaks to the algorithm yielding better or worse trading decisions over time.
A solid understanding of the underlying hardware was required, you would make sure network interfaces were arranged in a way they wouldn't cause contention on the PCI bus. You usually had separate interfaces for market data and orders.
All changes were done after exchange hours once trades had been submitted to the back office. The IT department was responsible for reimbursing traders for any losses caused by IT activity - there were shady traders who would look for IT problems and bank them up so they could blame a bad trade on them at some future time.
You don't need to shut down processes on the server. All you have to do is isolate CPU cores and move your workloads onto those cores. That's been a common practice in low latency networking for decades.
I'm not in HFT, but I wouldn't expect that to be enough.
Not only do you want to isolate cores, you want to isolate any shared cache between cores. You do not want your critical data ejected from the cache because a different core sharing the cache has decided it needs that cache. Which of course starts with knowing exactly what CPU you are using since different ones have different cache layouts.
You also don't want those other cores using up precious main memory or IO bandwidth at the moment you need it.
Just to add to your good points: since there's always a faster cache for your working set to not fit in, you can use memory streaming instructions to reduce cache pollution. Depending on the algorithm, increasing cache hit rates can give ridiculous speed-ups.
Some years ago I wrote a gist about HFT/HPC systems patterns (versus OPs C++ patterns) applied to dockerized Redis. Might be dated, but touches on core isolation/pinning, numa/cgroups, kernel bypass, with some links to go deeper. Nowadays I do it with Kubernetes and Nomad facilities, but same basic ideas:
I'm hoping that one day ChatGTP will be advanced enough to ignore advertisements for me. Oh what will the world do if they have to go see a doctor to get an effective toenail fungus cure rather than try the four hundred clickbait remedies that don't.
The problem with hashicorp IMO is that all of their pricing is apparently targeted at hedge funds and oil sheiks. I would like to buy support from them but I don’t have $30k/month to do that. I would like to move to a paid tier but that’s another $7k plus change a month. At that pricing level it makes more sense to build rather then buy. Compare that with AWS’s cloudformation. AWS support has a hefty price tag also but it includes every service including cloudformation.
Having your database exposed on the public internet so a third party service like this can read it directly is a very bad idea IMO. I get what your going for but the end here is some mom and pop getting their database compromised.
Deutsche Bank was one of the first places I worked at, closer to its heyday, I absolutely loved it. But it has been in decline for years, and has a lot of management issues, and fiefdoms.
One of my favorite stories to retell is my wife had a job there also and she had a medical issue from a car wreck. Her boss said the bank couldn’t function if she was doing physical therapy two hours a week, basically fired her, all the paperwork was drawn up, sent to a manager in London to sign. The manager in London was “too important” to sign things so he just leaves it for someone else to rubber stamp in his name the next day. Meanwhile my wife goes across the street (literally), gets a doctor to sign her disability paperwork, walks it into HR - and instead of doing physical therapy two hours a week she was on paid medical leave for almost a year. Her termination paperwork did get signed eventually but because she was on a protected leave they had to throw it out.
Is getting disability for a year so easy? Afaik in Austria your GP is not enough for that. It needs to get approved by supervisors of the national insurance to get it approved to prevent cheaters with "friendly" getting fake disability claims.
Yeah, in AT you'll get referred to an Amtsarzt from the ÖGK before anything - Also pretty sure the employer is off the hook and you get the money straight from either the ÖGK (federal health insurance) or the AMS (unemployment office) for any sick / disability leave longer than 6 weeks.
I think you have that backwards - Elon never wanted Twitter, he just wanted to see his name in some headlines and make people run around pulling their hair for a bit. However he messed up and put himself in a position where he had to buy Twitter for far more then it was worth and he was held to it. All the top people he fired day one were more then happy to parachute away - was the best thing for them. There is no way he will ever make back that 44 billion on Twitter, he’ll be lucky if he can pay the interest payments on it with what Twitter generates. More then likely all the people who went into Twitter with him will get deals on his other ventures and get their money back that way.
I’m not following all that. Someone made an offer, the board legally had to sell as it was in the interest of the owners (the shareholders). What else matters? If it’s deemed to be in the interest of shareholders for Reddit to sell off every sub to a corporate, they’ll do that too.
You’re both kinda right — yes GP’s evaluation was (probably) why the Elon transaction happened, and also it would not have had to happen if the owners were a handful of private individuals who didn’t mind passing up a majorly overvalued offer like that.
Of course, anyone at all who cares about money would have been a fool not to force him to buy it once he screwed up by bluffing in a way that made him contractually obligated to execute the transaction! So in practice, since even super-rich people love getting more money and non-rich people really want to become rich, good luck in practice spinning a hypothetical where Twitter owners would have said no, especially considering what a dog the company was already in terms of making money.
Yea. Owners can say no if and only they really are the owners. Being privately owned does not ensure good stewardship but it allows it. Case and point will be Reddit once it goes public. Every single person in tech should take a corporate law class and it should be required in undergrad.
reply