It actually is a fairly sailent point, although for as much as Claude has improved, there's still a chance it goofed. I've seen it happen, but that's why, if I am worried about stuff getting yeeted, I work off a git repo/branch so that if all else fails I can revert. (even if it's just docs)
> so tell me what benefits that has over having no dmarc record at all ?
The the existence of a DMARC assertion record in the DNS changes how the MTA (the receiving system) assesses the authentication of the message and authorization of the sender with SPF and/or DKIM, as per rfc7489 (and now also rfc9989).
No DMARC results in the MTA falling back to the original assessment method as defined in the original SPF and DKIM RFCs. These RFCs have design flaws and don't define the assessment flow all that well, they leave a lot up to the MTA's digression/interpretation.
So, the existence of a DMARC record with p=none is fundamentally different over not publishing a DMARC assertion record at all. It's just that with p=none you don't enforce the MTA to reject the email if it fails authentication/authorization, you're leaving it up to the MTAs digression.
If you could only choose from github, gitlab and atlassan then I suppose.. But really anything newer that stays in existance has to be focused on quality from early enough to not be defined by path dependence problems and bad choices like those 3.
Because I don't trust someone else to not train or steal our source code, or, even legally, introduce some silly cause after we are invested/locked into their infra, that allows them to do whatever with our property.
And on equal footing, I trust our security more than theirs. Case in point.
The IQ of the smartest human, the perfect memory storing and recollection of computers, the fact that it never tires. I don't know if it's AGI but it's already something greater than us.
*everything. I've really been using it since 4.x. Imagine this: being able to upgrade a system in-place with freebsd-update from minor to major to minor version without everything breaking or having to say a prayer before. And that's just one thing I love about it. Clear separation of userland (/usr/local/etc), rock-solid stability in networking, zfs on root.
I had to do 'bonded' interfaces on Debian the other day. It's what, 5 different config files depending on which 'network manager' you use. In FreeBSD it's 5 lines in /etc/rc.conf and you're done.
And don't even get me started on betting which distribution (ahem CentOS) will go away next.
I actually laughed out loud. Try upgrading CentOS to Rocky vs FreeBSD 11 to 15 ( that's FOUR major versions from 2017 I think ), and tell me again how good it is.
In LTS environments where I need to upgrade OS's, FreeBSD is a no-brainer.
> I actually laughed out loud. Try upgrading CentOS to Rocky vs FreeBSD 11 to 15 ( that's FOUR major versions from 2017 I think ), and tell me again how good it is.
I laughed out loud, there is no in-place upgrade mechanism for that in those distros and never has been, that is the nature of those distros. They release patch/security updates until they go EOL, which is measured in units closer to decades than years.
I don’t have a problem with BSDs. That’s cool you like upgrading in place.
The best and most laugh-inducing part of your whole point is that centos now not only allows you to do in-place upgrades, that’s the whole fucking point.
So then what's the point of mentioning Rocky as CentOS's successor ? In what way is it 'succeeding' ? That you can do a fresh install of Rocky ? And those stuck on CentOS can't upgrade ? Really useful those decades of support if your distro goes belly up
You don’t know this ecosystem, clearly. I’m not going to explain it to you much more than I did.
Centos was the free version of red hat. Like redhat, centos never fucking ever offered in-place upgrades. Centos moved to stream as a sandbox for redhat, and rocky took over as the free redhat.
Ask an LLM or something, this level of ignorance is unbecoming.
You should go re-read this. All I said was I hated ubuntu. I don't even know what paradigm you're inquiring from at this point, and I have no clue how to answer your question.
We were never in agreement or disagreement. You've been arguing against a stance I don't have.
BSDs are cool. They pushed the OS ball forward on server/home computing, video game consoles, etc. Linux is also cool, they pushed the OS ball forward on server/home computing, video game consoles, etc.
There is a long and storied history of computer operating systems. This conversation has shown me you're not aware of said history. You should go learn yourself up some.
You actually said Rocky was a successor to CentOS as well, which is what I responded to. As someone that tried to upgrade CentOS to Rocky, I can tell you that it may succeed it in name only, if that's what you meant. Physically you have to start over. If you re-read my first reply, I said as much originally.
Weird, I feel I'm talking to an LLM with a limited context window.
>>Centos didn’t go away. It changed. Rocky (et. al.) took the old centos role, and >>I see this as a win/win for everybody.
>>Ubuntu is the disaster Linux distro, I won’t touch Ubuntu if I have any other >>option.
My team of 6 people has been building a software to compete with an already established piece of software written by a major software corporation. I'm not saying we'll succeed, I'm not saying we'll be better nor that we will cover every corner case they do and that they learned over the past 30 years. But 6 senior devs are getting stuff done at an insane pace. And if we can _attempt_ to do this, which would have been unthinkable 2 years ago, I can only wonder what will happen next.
If the goal is to simply undercut the incumbent with roughly the same product than it doesn't really matter if the incumbent starts using LLMs too as their cost structure, margin expectations, etc. are already relatively set.
100%- which is what I'm telling everyone. I am in big tech and it doesn't matter that I can write what I used to in 1 week in 5 minutes. Meetings, reviews, design docs, politics, etc. etc. mean how much code is written is irrelevant. Productivity in big tech is pretty low because of organizational overhead. You just can't get anything done. Being able to get more work done with less people is the real game changer because less people don't suffer from those "coordination headwinds".
Bingo. Most of my employees come from big tech (not faang, but big corps ) where they felt they couldn't really deliver what they wanted and what they're capable of. These guys love to not just code, but to create and deliver stuff.
Yeah I’m curious how much the moat of big software companies will shrink over the next few years. How long before I can ask a chatbot to build me a windows-like OS from scratch (complete with an office suite) and it can do a reasonable job?
And what happens then? Will we stop using each others code?
Just hired a 45yo who excels and loves and thrives doing this stuff. Proxmox, local storage, local backups + offsite backups. 1Pb of data, colocation costs are 5k/month. Guess AWS costs for similar
reply