rajesh-s

Eg: repl.it

Is the experience chaotic? Somewhat like letting the co-driver control the car simultaneously?

I came across this article today [1] where a popular journalist in India was tricked to think they had a job offer at a prominent University by an elaborate phishing scam.

After this I started thinking about the security of modern day domain redirects in the context of phishing. One could register thexyz.edu or something similar that's close enough to xyz.edu for phishing and then directly domain redirect.

The commoner, who may have the basic instinct to verify the source of the email might just try to look up the domain from which the email was sent but if that redirects to the real domain they maybe convinced that it's the actual one.

Are there any mechanisms to prevent this kind of malicious domain redirect that can be misused? What are your thoughts on this from the security perspective of the larger crowded who may not be well versed with technology?

[1] https://twitter.com/Nidhi/status/1350024214997155840?s=20

I submitted a feature request to GitHub recently and was wondering if this really made sense.

Two situations: 1. Academic courses (MOOCs included) require students not to publish progress/code publicly during a course 2. You worked on a personal project, which you don't want to make public because you believe you have other plans with it. But you still want to be able to show it to selected people (such as a prospective employer)

But having a version controlled repository is really helpful in both these scenarios. It's also important for one other thing, specific people (professors, potential employer etc.) to know of what your approach to assignments/learnings from the course was. At the moment, there is no way of showing someone the depth of learning/work you did during a course/project unless you mail them the zipped repo.

I believe, link-based sharing for private repositories with view-only access would be incredibly useful. This would allow prospective employers/academic faculty to access this link (lets say from a CV) while still maintaining Honor Code compliance or personal interests. Adding someone as a collaborator to a private project just to show them your code does not make sense. It might help students/developers to choose who has access to their private repositories.

Let me know what you think!

Is mirroring a good option? (lets say mirror github repos to gitlab so that if you lost access to the former, you still would have your data). Local backups don't tend to be reliable in terms of maintenance and long term archival costs.

Have consolidated tech companies created a risk of single point of failure OR are they safe to be considered too big to fail?

What would be the consequence of it on the internet as we know it? Are we prepared?

When it's a company like Google you're talking about, it's just hard to imagine a day when platforms like YouTube or Gmail might be killed off.

Are there legal clauses that would prevent such a thing? Or does the corporation have complete freedom in such matters.

I was just reading this https://news.ycombinator.com/item?id=23832437 and keep seeing this every once in a while. What flow do you follow to backup years or your projects from such platforms?

Or is it intended to be a product marketing brochure of sorts? For example, https://hubs.ly/H0r91td0

If you find them useful, do you have any tips for new students stepping into the industry on reading whitepapers.

It would make migrating between services easier which is good for everyone. How do such standards get conceived or make progress in general?

Have there been identified that exploited vulnerabilities like Meltdown/Spectre before researchers discovered and disclosed it through proper channels? Just trying to understand the impact & lifecycle of dealing with vulnerabilities (esp. in h/w)