I had a secondary Gmail account with a really nice short nickname (from the early invite/alpha days), forwarded to another of my mailboxes. It had a weak password, leaked as part of one of the many database leaks.

Eventually I noticed some dude in Brazil started using my Gmail, and he changed the password — but I still got a copy of everything he did through the forwarding rule. I caught him bragging to a friend on how he cracked hashes and stole and sold email accounts and user details in bulk.

He used my account as his main email account. Over the years I saw more and more personal details getting through. Eventually I received a mail with a plaintext password... which he also used for a PayPal account, coupled to a Mastercard.

I used a local website to send him a giant expensive bouquet of flowers with a box of chocolates, using his own PayPal and the default shipping address.

I included a card:

"Congratulations on acquiring my Gmail account, even if I'm 7 years late. Thanks for letting me be such an integral part of your life, for letting me know who you are, what you buy, how much you earn, who your family and friends are and where you live. I've surprised your mother with a cruise ticket as you mentioned on Facebook how sorry you were that you forgot her birthday and couldn't buy her a nice present. She seems like a lovely woman. I've also made a $1000 donation in your name to the EFF, to celebrate our distant friendship"

--- HTTP/3 is coming! And it won't use TCP! ---

A recent announcement reveals that HTTP - the protocol used by browsers to communicate with web servers - will get a major change in version 3!

Before, the HTTP protocols (version 1.0, 1.1 and 2.2) were all layered on top of TCP (Transmission Control Protocol).
TCP provides reliable, ordered, and error-checked delivery of data over an IP network.
It can handle hardware failures, timeouts, etc. and makes sure the data is received in the order it was transmitted in.
Also you can easily detect if any corruption during transmission has occurred.
All these features are necessary for a protocol such as HTTP, but TCP wasn't originally designed for HTTP!
It's a "one-size-fits-all" solution, suitable for *any* application that needs this kind of reliability.
TCP does a lot of round trips between the client and the server to make sure everybody receives their data. Especially if you're using SSL. This results in a high network latency.
So if we had a protocol which is basically designed for HTTP, it could help a lot at fixing all these problems.
This is the idea behind "QUIC", an experimental network protocol, originally created by Google, using UDP.

Now we all know how unreliable UDP is: You don't know if the data you sent was received nor does the receiver know if there is anything missing. Also, data is unordered, so if anything takes longer to send, it will most likely mix up with the other pieces of data. The only good part of UDP is its simplicity.
So why use this crappy thing for such an important protocol as HTTP?
Well, QUIC fixes all these problems UDP has, and provides the reliability of TCP but without introducing lots of round trips and a high latency! (How cool is that?)

The Internet Engineering Task Force (IETF) has been working (or is still working) on a standardized version of QUIC, although it's very different from Google's original proposal.
The IETF also wants to create a version of HTTP that uses QUIC, previously referred to as HTTP-over-QUIC. HTTP-over-QUIC isn't, however, HTTP/2 over QUIC.
It's a new, updated version of HTTP built for QUIC.

Now, the chairman of both the HTTP working group and the QUIC working group for IETF, Mark Nottingham, wanted to rename HTTP-over-QUIC to HTTP/3, and it seems like his proposal got accepted!
So version 3 of HTTP will have QUIC as an essential, integral feature, and we can expect that it no longer uses TCP as its network protocol.

We will see how it turns out in the end, but I'm sure we will have to wait a couple more years for HTTP/3, when it has been thoroughly tested and integrated.

Thank you for reading!

To become an engineer (CS/IT) in India, you have to study:
1. 3 papers in Physics (2 mechanics, 1 optics)
2. 1 paper in Chemistry
3. 2 papers in English (1 grammar, 1 professional communication). Sometimes 3 papers will be there.
4. 6 papers in Mathematics (sequences, series, linear algebra, complex numbers and related stuff, vectors and 3D geometry, differential calculus, integral calculus, maxima/minima, differential equations, descrete mathematics)
5. 1 paper in Economics
6. 1 paper in Business Management
7. 1 paper in Engineering Drawing (drawing random nuts and bolts, locus of point etc)
8. 1 paper in Electronics
9. 1 paper in Mechanical Workshop (sheet metal, wooden work, moulding, metal casting, fitting, lathe machine, milling machine, various drills)
And when you jump in real life scenario, you encounter source/revision/version control, profilers, build server, automated build toolchains, scripts, refactoring, debugging, optimizations etc. As a matter of fact none of these are touched in the course.
Sure, they teach you a large set of algorithms, but they don't tell you when to prefer insertion sort over quick sort, quick sort over merge sort etc. They teach you Las Vegas and Monte Carlo algorithms, but they don't tell you that the randomizer in question should pass Die Hard test (and then you wonder why algorithm is not working as expected). They teach compiler theory, but you cannot write a simple parser after passing the course. They taught you multicore architecture and multicore programming, but you don't know how to detect and fix a race condition. You passed entire engineering course with flying colors, and yet you don't know ABC of debugging (I wish you encounter some notorious heisenbug really soon). They taught 2-3 programming languages, and yet you cannot explain simple variable declaration.
And then, they say that you should have knowledge of multiple fields. Oh well! you don't have any damn idea about your major, and now you are talking about knowledge in multiple fields?
What is the point of such education?
PS: I am tired of interviewing shitty candidates with flying colours in their marksheets. Go kids, learn some real stuff first, and then talk some random bullshit.

import LongRantKit
import NonRantKit
import TldrKit

I don't like stickers on my laptop because it clutters it up. But today I realized the importance of them.

A few months ago I was sitting at a coffee shop working on a paper and I noticed a guy with this cool sticker on a MacBook Pro: it had the integral symbol to the left of the Apple logo, and to the right of it a lowercase d and another Apple logo. It took me a few hours to realize what it meant, but I finally did and at that point I also guessed that not many people know what it is.

So I, as antisocial as I am, I finish up my work and before I leave I walk up to him and say hi. At this point I'm a senior in high school and I learn he's a junior in the same college I plan to attend. We talked a little before I had to leave and got to know each other somewhat.

After I leave I find him on Instagram and Facebook and friend him and such.

Recently I posted a picture saying I had recently joined the Apple Developer Team, and also recently reposted a memory on Facebook from 5 years ago that was a screen capture of an iPhone 4 simulator running iOS 5 showing off one of my first apps.

Then yesterday I get a message from the guy I met at the coffee shop asking for some help with an iOS project he's working on. We decide to meet today and I spend the entire morning showing him the basics of Swift, Xcode, Interface Builder, etc. I feel like I really helped him jumpstart his app and helped him understand the basics of different concepts.

If he didn't have that integral sticker on his laptop I would have never had this opportunity to finally share some iOS development experience.

For this I would like to thank my high school calculus teacher, with whom I spent many classes at Starbucks because I was an only student. I'd like to thank laptop stickers, and finally I would like to thank the coffee shop.

TL;DR: Said hi to a guy with an integral sticker on his laptop, a few months later he approaches me for help understanding iOS development.

TL;DR I'm fucking sick and tired of Devs cutting corners on security! Things can't be simply hidden a bit; security needs to be integral to your entire process and solution. Please learn from my story and be one of the good guys!

As I mentioned before my company used plain text passwords in a legacy app (was not allowed to fix it) and that we finally moved away from it. A big win! However not the end of our issues.

Those Idiot still use hardcoded passwords in code. A practice that almost resulted in a leak of the DB admin password when we had to publish a repo for deployment purposes. Luckily I didn't search and there is something like BFG repo cleaner.

I have tried to remedy this by providing a nice library to handle all kinds of config (easy config injection) and a default json file that is always ignored by git. Although this helped a lot they still remain idiots.
The first project in another language and boom hardcoded password. Dev said I'll just remove before going live. First of all I don't believe him. Second of all I asked from history? "No a commit will be good enough..."

Last week we had to fix a leak of copyrighted contend.
How did this happen you ask? Well the secure upload field was not used because they thought that the normal one was good enough. "It's fine as long the URL to the file is not published. Besides now we can also use it to upload files that need to be published here"
This is so fucking stupid on so many levels. NEVER MIX SECURE AND INSECURE CONTENT it is confusing and hard to maintain. Hiding behind a URL that thousands of people have access to is also not going to work. We have the proof now...
Will they learn? Maybe for a short while but I remain sceptic. I hope a few DevrRanters do!

'"Chess" can't be modified or deleted because it's required by macOS.' This is a screenshot I took last year when trying to clean up unused apps on a mac. makes me want to try to forcefully remove the chess app, only to see which integral part of the system it will break.

Devs can hardly stand testers but both of them are an integral part of the development process...

1. Learn Kotlin
2. Actually sit down and push through machine learning.
3. Finish integral calculus and start multivariable calc.
4. Work on 1 project until completion.
5. Socialize a bit more.
6. Obliterate bugs.

Too much math ? Seriously ? Had you made the effort to atleast 'look' at them, you would see how simple they are. And just because I use the word 'equation' does not automatically make it a Volterra Integral Equation.

Could've discussed the subject at hand. But no, let's bring on the judgement. Who wants to ever discuss the subject ?

Since memes have become an integral part of our community, I propose a way to handle them without affecting the actual Ranters.

Everyone adding a meme or a gag picture can do so under a particular tag, and the Algo can handle your meme needs by exposing you to that particular tag based on your activity with such posts.

Or you could just make the users search for memes if they wanted to see them.

This could also be done vice versa by ranters using a RANT tag, I would keep my RANT filter on so anything without that tag won't show up

To make it better you can provide a sort of suggested tags option :

|gag|¦¦¦|meme|¦¦¦Ranf|¦¦ scroll to the right for more... Kinda thing

@dfox @trogus please tell us what you think about this

In a meeting yesterday working through our WebAPI coding standards, starting from File -> New project..etc..etc.. and ironing out some of the left-or-right decisions so we can have a consistent coding style, working in a meeting room with an overhead projector and sharing keyboard around with one another.

Then we hit the routing 'rules' in the WebApiConfig, "api/{controller}/{id}"…

DevMgr: "Do we need the 'api' prefix? It seems redundant."
Ralph: "Yes it's needed. Prefixing the controllers with 'api' is industry best practice. Otherwise, how is anyone to know it's a web api"
Prancer: "Yea, it's part of the REST standard."
Me: "I don't think so. That is only part of the Asp.Net routing rule. We can put anything we want or take anything out."
DevMgr: "Yea, it looks silly. All the new services are going to be business process specific."
Ralph: "That's how everyone does it. It's kind of the point of why REST services are called WebApi"
Prancer: "What's the point of doing any of this work if we're not going to follow industry standards."
Me: "I understand if the service is part of larger web site, but we're developing standalone services. Prefixing routes with 'api' is redundant. I mean who are these 'everyone' you're talking about?"
<ralph rolls his eyes>
Ralph: "Lets see …uhhh… Netflix?. They're kinda a big deal."
Me: "Like I said, it's an integral part of their site and the services they provide. That's fine. I'm talking about the 12 other 3rd party services we integrate with. None of them have 'api' on any of their routes."
Prancer: "We're talking about serious web services."
Me: "Last time I checked, UPS is a big and serious service."
Ralph: "Their services are a fracking joke" – he didn't say fracking.
Me: "Our payroll system, our billing system, billion dollar companies, didn't have '/api' prefix anywhere. Heck, even that free faxing service we used for a while was a dead-simple routing path."
<I take the keyboard away from Ralph, remove the 'api' from the route.>
Me: "There. Done. Now, lets talk about error handling.."

Rest of the meeting Ralph and Prancer don't say much of anything, arms crossed…I swear Ralph looked like he was going to cry.
This morning I catch my boss…
Me: "What did you think of the meeting? I thought Ralph was going to take a swing at me when I took the keyboard away from him."
DevMgr: "Oh yes…I almost laughed out loud….blows my freaking mind how worked up people get about crap that doesn't matter. Api..or not…who the frack cares. Just make it consistent"
Me: "Exactly…I didn't care either way, but I enjoyed calling out that nonsense."
DevMgr: "Yes..waaay too much."

If I didn't call them on their BS and the 'standard' allowed to continue, I can bet my paycheck when the subject comes up in a few months (another mgr asks 'isn't this api prefix redundant?') Ralph and Prancer will be the first to say "Yea, its stupid. We fought really hard to remove it from the standard...its not our fault...its <insert scapegoat> fault."

I fucking hate the process of setting up IDEs and compilers! All the build files, cmake files, tasks, all that shit.

I undrerstand it's integral part of coding, but fuck, why does it always take so long to set up a stupid project. Just let me start coding ffs.

Sometimes I get so frustrated that I rather write a bash script or run the compiler commands in the shell instead of going through the hassle of setting all this up.

float integral = 0;
float dx=float.minValue;
for (float x = a; x<=b; x+=dx) {
integral+=f(x)*dx;
}

A classmate just literally wrote this and he believed it was the proper way to do it.
I asked him to integrate f(x)=1 on 0<x<1.

Please stop using cache as an integral part of the system.

Just... don't...

Revision to the Peter/Dilbert Principle, the ProjektAquarius principle: a company will systematically shift the least competent employee on to the assignments the competent employees can't be bothered to do until they become an integral part of the team and drag you down with them. (E.g. eventually they completely fuck up your delivery process, although it's probably still cheaper and quicker than having them do anything else.)

ProjektAquarius principle: A Case Study

We have an engineer who is getting paid quite a bit more than me. Over time his responsibilities have gradually been reduced to documentation and running our almost entirely automated build. Well today the build failed. He pulls me over to tell me, and says he's confused because there is a file there he has never seen before in there and a file he always has seen that isn't there (basically a file got renamed. It was not non-obvious). Answer: change the file name.

Then he comes over and tells us that it's failing again because the script is not finding a file. So a coworker of mine and I go over. He explains the whole build process to us when we ask if there is any point in the script that would help us identify where the script is looking for the file and failing (there wasn't but that's besides the point).

Turns out, he had decided to put the assembly list in order. Normally no problem, but the list is in source destination pairs. So the fucking file was being put in a different directory than the one the script was looking for it in and failing. And that's the story about how my company just paid 3 engineers a quarter of a man hour each for something that would have been resolved in 30 seconds via file search/copying and pasting a file path. Related note: our process for building an install is now about 4 hours long with no change on process besides the BCAK.

Symfony totally misses the point that a cache is supposed to sit on top of your code and accelerate it, not be an integral part of the software, so you cannot turn it the fuck off!!!

I'm fucking Paralyzed and I need some advice.

I want to be an entrepreneur.

Not just an entrepreneur but a DAMN good one.

I self-studied business, economics, physics, self-taught multivariable calculus, teaching myself chemistry too.

But I haven't even started my career and I just graduated from University.

Right now I'm starting simple and just doing a few web development things.

But, I want to go deeper into a subject that hasn't really had its problem solved yet.

A.I. can sell you neat things, but it can't kill misinformation (yet).

Graphics are an integral part to gaming, but GPUs are the second greatest threat to our environment behind commercial jets.

Do I HAVE to choose between A.I. and graphics?!

Well let's see here, I imagine that there would be different models of AI's by different companies ... Easy ... I would become an AI reviewer on youtube, and since AI's are such an integral part of daily activities, i imagine i will have a pretty good subscriber base, enough to sustain my needs !!!

data Word: A Word is an unsigned integral type, with the same size as Int.

And here I was thinking a word is a string! And that's not all, there is also Word8, Word16 and whatever else.

Another Mojave Post...

Apple added 4 new apps, all of which cannot be removed (oh boy am I off to a great start). I saw the new home app and thought "if your stuck here I might as well attempt to put you to some use" so I opened it to try and maybe add my smart plug or something, but it told me I need an iOS device to add accessories...

Why the fuck is there any functionality that is locked behind iOS especially something as integral to the core functionality of the app like adding a fucking device to an app that manages them.

On a side note apparently news is bugged for me and I cannot find it it the launchpad so that's slightly less bloat.

Once upon a time in the bustling city of Techville, there lived a talented web developer named Alex. Known for their exceptional coding skills and innovative designs, Alex had a reputation as a brilliant but often solitary worker. Despite their immense talent, they often struggled with social interactions and found it challenging to connect with their colleagues.

One sunny morning, as Alex arrived at the sleek offices of WebWizards Inc., they noticed a new face amidst the sea of familiar coworkers. Her name was Lily, a warm and friendly individual with an infectious smile. Alex couldn't help but be drawn to her positive energy and kind nature.

Over time, as they worked on various projects together, Alex and Lily formed an unexpected bond. Lily's patience and willingness to collaborate made their partnership seamless. She recognized Alex's expertise and valued their creative input, which helped foster a deep sense of mutual respect.

As their professional relationship grew, Alex began to see beyond the surface of the company they worked for. They realized that WebWizards Inc. was more than just a business; it was a family of talented individuals who genuinely cared about one another. The company fostered an inclusive and supportive environment, encouraging personal growth and celebrating achievements.

One day, overwhelmed by gratitude for both Lily and the company they worked for, Alex decided to express their feelings. They sat down and poured their heart out, typing a heartfelt message of appreciation and admiration. Alex couldn't contain their excitement as they hit the "Send" button, eagerly awaiting a response.

To their delight, Lily responded promptly with overwhelming joy and gratitude. She confessed that she had also felt a strong connection with Alex and considered them an invaluable asset to the team. Furthermore, she shared that the supportive culture and caring nature of WebWizards Inc. had made her job more fulfilling and enjoyable.

The two coworkers became closer friends, their collaboration flourishing both in and out of the office. Alex's once-rare smiles became more frequent, and their confidence grew. They no longer felt like an outsider but an integral part of a wonderful community.

Together, Alex and Lily continued to create outstanding web projects, surpassing expectations and leaving their clients amazed. Their passion and dedication were fueled by the genuine camaraderie they shared with their colleagues at WebWizards Inc.

As time passed, Alex realized that their journey as a web developer had been transformed not only by their skills but also by the amazing people they had the privilege to work with. They learned that a kind coworker and a supportive company could make a world of difference, turning an ordinary job into an extraordinary experience.

And so, the tale of Alex, Lily, and the remarkable WebWizards Inc. serves as a reminder that in the vast realm of work, the bonds we form and the culture we foster can be as impactful as the tasks we accomplish.