267 karma · joined January 14, 2015
The fact that Kopia has a UI is awesome for non-technical users.
I migrated off restic due to memory usage, to Kopia. I am currently debating switching back to restic purely because of how retention works.
I’ve had an eye check, a few months back a general medical. Both were fine/no significant changes. I rarely drink, no drugs. I feared a series of migraines might been response but I’ve been assured otherwise.
I so far figured it’s too much skim reading, a lot of very poor sleep, being on the edge of burn out and maybe a touch of post COVID brain fog.
Your post is encouraging me to start doing something about it.
I don’t have much to add but it’s reassuring to know that I’m not alone
Also for ref :)
Highly recommend both libraries!
You are competing with https://grafana.com/, https://www.metabase.com/, https://superset.apache.org/, etc.
At work I ran email servers professionally and with good deliverability for years. My own email server was arguably longer lived than those at work, just much lower volumes. IP block was clean, DKIM, SPF, rDNS, etc. all setup correctly.
I thought I had no deliverability issues. I interacted with mailing lists regularly, the odd email to friends and family and I was firmly in your camp until I had to deal with a death in the family.
I think this was shortly after Microsoft BPOS became Office365. It became very very clear very very rapidly that to certain orgs I just wasn't hitting the inbox. And there was jack shit I could do about it. That was the end of my mail server, and it's certainly got worse over time.
In development mode with inotify you get python hot code reloading. In development mode the XML (with a handful of exceptions regarding menus, and ir.actions) will be read from disk on refresh.
At work we use Dockerized Odoo based on a [Doodba](https://github.com/Tecnativa/doodba). We use [click-odoo](https://github.com/acsone/click-odoo) to manage module upgrades (amongst other things). Dev workflow is largely managed through [invoke](https://www.pyinvoke.org/) tasks.
I do wish there was hot code reloading for the views (xml), but realistically if you’re making an app of any complexity the views in the backend are the small part and likely not where you are spending the majority of your time.
Website stuff is absolutely 100% stuck in the past at the moment, imho.
In 2005 the Royal Mail was fully privatised. Since then I personally feel the amount of unaddressed mail has increased. But that might be in my head
They were deprecated in 1803.
Our path has been Ansible -> Ansible+Docker -> Docker Swarm -> k8s. We absolutely don't need k8s, but the other options all had downsides.
1. Nomad was on our list and probably would've been better, but there were no managed Nomad solutions at the time and it was not as widely used as other solutions
2. Our time on Swarm was /ok/, but it was more and more obvious that being on the lesser walked path was a problem, and it's future made us run away from it
3. k8s gave us a nice declarative deployment mechanism
4. We can switch to a managed solution down the road with less friction
The two typical scenarios are;
1. You want to use the same IP space multiple times across different networks (i.e. multi-tenant)
2. You have a bunch of different networks that you really never want to ever be able to talk to each other (you can allow it through routes, etc. but by default this does not happen). Although you can achieve this with VLANs and ACLs, on a single routing table, rules can become a real pain in the ass to manage very quickly
You could use this for stuff like guest or IoT networks.
Which display, if you don’t mind me asking? I’ve had a similar idea for a while, but haven’t seen a display that felt reasonably sized or priced for a hobby project
CoC basically takes VSCode addons and modifies them just enough to get them working in conjunction with neovim.
I'm not saying that it's a bad laptop. But there are just so many little annoying things about it after coming from the MBP and MacOS;
* Trackpad is subjectively worse, but I can't tell you why beyond its just smaller - but I am objectively much less accurate with it and trigger tap-clicks when I don't mean to. The trackpad positioning is also slightly uncomfortable to use.
* Fan noise - the fan curve has it ramping up earlier than a MBP
* Windows was hosed out of the box (fine, fixable, but it wasn't a good start)
* The "soft" covering results in so many fingerprints
* Webcam on the bottom bezel is an awful angle
Pros;
* Great screen, touch is a nice add-on but found I rarely use it now
* Keyboard isn't terrible
* Power adapter isn't a brick
Would I do it again. Honestly, not sure. My daily driver isn't the laptop and I just deal. If I had to use the laptop daily, I'd probably reconsider.
I do a fair amount of work with companies that do "EDI" over CSV (or worse CSV-like - think 2 CSVs jammed together with different formats, no headers, no support for escaping or quoting) and fixed width documents. I can absolutely assure you that humans do open these files in notepad far more often than I'd like.
Often one of the main reasons they don't use things like X12, ASCII separators, etc. is because a "human needs to open it at some point" was a prevailing business decision some number of years ago (think "what happens if the IT system fails? how can we still ship stuff even in a complete emergency") and now it's baked into their documented process so deeply its like shouting into the wind to alter things. Third party warehouses are the worst at this.
* Removing an errant font-config lcdfilter configuration entry (this was a left over from when I was running "infinality" and should have been removed)
* Switching font from Noto Sans to Ubuntu
Its not perfect, but its a lot better. I'll probably play with oversampling (rendering X at a higher resolution and scaling down like OSX) at some point to see if I get the quality I want.
Maybe it’s subjective, maybe it’s a measurable thing. I’ve not looked, but I feel KDEs text rendering is worse on my daily driver.
I've been looking for a decent solution for pxe and cluster-api. I've not pushed the button on any as I feel like they're all a little immature. Admittedly I've not had time to set up any in a test env yet. Any recommendations?
From an ops point of view it’s simple to deploy and I’m yet to hit any really sharp edges. However the lack of cronjobs and init containers is an annoyance, but you can work around them.
Mirantis’ recent announcement of further dev on Swarm after the initial announcement of only 2 years of support has not helped. I had been looking at moving to k8s. I’m now undecided if we should just continue with the plan to dump Swarm or keep it.
That's probably about it. Right now, I'm jumping on the k8s bandwagon, but looking to keep it simple. As much as I'd like to look at nomad seriously, too many times I've been caught by not looking at the mainstream.
I don't think the post you're replying to is really saying "no innovation". I think it's more subtle.
The "problem" with DoH is that you need to look at it with several different hats, and I feel very few people make it clear how they're complaining about DoH.
* From a consumer perspective DoH is a good thing (mostly)
* From an traditional/enterprise/business-like environment perspective it's inserting itself in the middle of the stack and may cause headaches with a few things (not limited to leaking internal names to external resolvers), unless it's just blanket disabled/forced to a local server (which may not always be practical for different reasons) - currently
Ultimately who do we have to blame for this but ourselves? Organisations have tried to get encrypted DNS off the ground in traditional DNS infrastructure and clearly failed to meet the required timeline.
I personally feel like the problem, just like with IPv4, is that traditional DNS infrastructure is "fine" (i.e. it works). We don't have a great motivation but we do have fear of breaking the many many many boxes which are un-upgradeable/critical.
Having been down this path, without the time to dedicate fixing/working on a driver, I wouldn't even consider a non-"blessed" language in combination with MSSQL anymore. It was too much pain.