moreira
The internet is built around this, and we've all collectively decided that it's OK.
But to your point, their robots.txt does allow this kind of access, so this argument is moot - they explicitly allow bots like archive.org's to crawl & index these pages' content.
They might've started with PHP, but even that stopped being a thing once they switched to Hack, their home-grown language, ~10 years ago.
[0]: https://engineering.fb.com/2021/04/29/developer-tools/rust/
e.g. If a JavascriptCore vulnerability allows RCE on a Mac running whatever old version, write something to exploit it and execute the "say" command on that Mac, so anyone running that version can go to that webpage and literally see "wow this is a real exploit that actually works and anyone can abuse".
I'd love to see that. Kind of like the XSS script alert triggers, stuff where you can just paste a bit of code and prove that it -is- exploitable, without it actually doing anything harmful.
I know this was an off-hand remark that you're probably not thinking much about, but you're absolutely right, and it might be worth seriously considering it. Moving to the US is probably the single biggest improvement you can make to your career and opportunity options. You will never have as much opportunity in Europe as you will in the US, not in the tech world. You might be able to eke out some success in Europe, but it'll pale in comparison to what you could've achieved in the US.
Their reasons are irrelevant.
OSs didn’t come with browsers. Microsoft bundled IE with Windows. Now every OS comes with a browser.
Responding to things can wait till I'm back at a computer. If it's urgent, the watch can make calls, and if you're using a bluetooth headset, it's indistinguishable from a phone.
I don't travel without the phone, though, it is great having easy, fast access to everything (maps, browser, tickets, etc). The watch can do most of that but it's clunkier, and for me it's not a hill worth dying on.
So I do think you can achieve what you're looking for - rely less on your smartphone while still being 24/7 reachable. It is definitely be worth looking into.
[0]: https://en.m.wikipedia.org/wiki/IAd [1]: https://searchads.apple.com/
Something like: If you end your contract with someone because you think that they were in violation of the terms, you have to clearly list what your reasoning is for it, with no tolerance for black box answers.
DMCA takedown requests include the list of offending URLs. This should be made similar. "We terminated our contract because this, this, and this signal, make us think that you're in violation of its terms". You can then appeal, and obviously if the two parties can't come to an agreement by themselves, you can at least use the legal system.
Otherwise, we're living in a world where contracts between two parties mean nothing. Anyone can pull out of anything at any time for any reason, with no notice.
They now have cachet/reputation, and deeper pockets, and can easily start up and get funding for anything they might want to do.
Just making a slow, healthy profit with a company might not be enough for them.
It's a really strange (and wholly unnecessary) cycle.
That doesn't seem right. As a developer, if I were the CEO of a company, I would not be able to read progress from the legal team, or finance team, or any other team. What's going on with that lawsuit? No idea. Do I know how long it'll take to wrap that up? Nope. I can't understand any of their jargon. I still gotta make decisions about it.
I don't need legal competence in order to run the company or make decisions about stuff, and I shouldn't need technical competence either.
It's on us, as developers, to communicate clearly and give answers and reasonable estimates, so management can make their plans and adjust priorities if necessary. The process we use to generate those answers (agile, git commits, deployments) is entirely up to us and could not matter less to the business, at the end of the day.
"How does git deal with the problem that if we store changes forever, the file size grows indefinitely?"
Even though Git uses deltas for diffs to reduce space usage, it still technically grows indefinitely, same as CRDTs. So the answer is it doesn't, and it doesn't matter.
If the size of something actually becomes a problem, -then- it can be handled (e.g. Git LFS).
With CRDTs, depending on what you're doing, it might never become a problem. Keeping all versions of a document is entirely inconsequential, as an example. The size might grow indefinitely but how many edits is a document going to have, realistically?
The social networks of the past were useful as a way to keep in touch with people. MySpace, early Facebook, and the countless others from back then. Now everyone’s online 24/7, and accessible on multiple services all at the same time, all the time. You don’t need social networks to keep in touch with anyone anymore, their original raison d'être is gone.
What’s sought after now is meeting -other-, new, like-minded people and content. For that we have twitter, Reddit, TikTok, and whatnot. People want their bubbles. We’re all here on HN for that exact purpose.
This doesn’t sound right. You are not going to agree with 100% of someone else’s decisions. No matter how much you discuss something, no matter if you understand all the ramifications, everything there could possibly be. Sometimes you’re just not going to agree with the direction someone else is taking, and you’re going to have to accept it.
And that’s okay. It’s not toxic to disagree with someone, or to accept that even though you might disagree, they’re going to do X their way (or that you’re going to have to do X their way because that’s what they want). That’s not office politics, that’s life.
GitHub are no longer legally able to provide the service, and so those people no longer have access to GitHub the service. Nothing code-related.
When I said "standard characters" perhaps I should've been clearer. I meant "they're non-emoji characters". Sorry, I didn't realise it would cause confusion.
♠♦ There's a whole bunch of them[1]! ♦♠
[0]: https://www.compart.com/en/unicode/U+2665 [1]: https://www.compart.com/en/unicode/block/U+2600
I feel like a lot of people would do well to revisit the old adage not to discuss politics, sex, or religion, particularly with strangers - or worse, potential customers.
You say this as if it's something that's happening, but it's not. There's a few pockets of self hosted bits here and there, but that's not new. We are not coming back to decentralised systems, and we will -never- go back to that in any significant number.
Most people are not going to give up the cloud to go back to bare metal. Most people are not going to give up their zero-maintenance SaaS app to go self-host something. All of it is just too convenient, and you then also have the inertia working against you; there's a whole generation of developers now that has grown up without ever administering a server. They're not gonna give up their Lambdas and drop down to a lower level, just like I'm not gonna give up my interpreted languages and drop down to C, even though it'd perform a hell of a lot better.
I'm with you - I like self-hosting, and I run everything I can on bare metal, and I hate everything costing money every month. But there's no future in which people decide "oh I'll give up the convenience and the extra money I can make from this" and go back to the old way of doing things.
The cloud has outages too, though. If you've been here long enough you've seen plenty of cloud-related outages. The truth is, outages happen, on cloud or otherwise. They might've avoided this but they might've been hit by yesterday's AWS outage. [0]
I don't think they'd gain much from migrating, and to the best of my knowledge they haven't.
You asked how some people to live without notifications, and I gave an example of how. That's it.
1. General awareness about what's on your plate. You don't need a reminder, you just need to know that you have meeting X at Y hours, or Z appointment on this date.
2. The difference is that you check email/IMs on your terms, which means that you decide when you want to take a break from whatever you're doing to look at and respond to anything in your inbox. If you have notifications on, your focus will keep getting taken away from whatever you're doing. Depending on what you're doing, this may or may not be important to you.
You were able to do it, but what happens to them when you're not around? Does their team have the required experience to handle it? That's the difference in cost. It's like DYI - yes, if I have all the skills and experience I can do everything myself incredibly cheaply, but... I don't. So I gotta pay.
But if your team does have the skills and experience, it's definitely worth looking into.
I do think people deeply underestimate what can be achieved with a single (or two, if you need a standby) dedicated Linux server these days. A single server can easily go up to 2TB of RAM and 128+ cores. Long before you ever get to a scale where that's a limitation, you'll have more than enough resources to figure things out.