lapser

This is already happening. The likes of Google Home et al already hardcode their own servers. I noticed that no DNS requests were being made through my Pi Hole, so when I looked, it turned out their DNS servers were hardcoded.

However, I'm more worried about when they start hardcoding DoH servers.

It is indeed built on Wireguard, but it is a user space implementation of Wireguard. Maybe that's fine, but kernel space would allow much faster speeds.

Worth noting, the biggest closed source thing from Tailscale is the server side, which has an open source re-implementation call Headscale[0].

[0] https://github.com/juanfont/headscale

Is there an FLOSS project that combines Scrapy scrapers and just makes the results publicly available?

I tried this as an alternative to teamviewer not long ago to help my dad with something. He runs a little bit of an older macOS version because reasons (I'm a bit wary upgrading it because another newer macbook my mum owns basically said the device is unsupported when I upgraded to the latest version).

Rustdesk refused to install because the macOS version was too old. Until Rustdesk runs on many OSes, especially older OS versions, it will be hard to use.

Mind you, it's not entirely clear what OS versions are supported from the website, so I went through a lot of trouble to get my dad to try and install it, only to then be disappointed.

I have hope though! It looks great so far.

Not really. The API these days tends to be JSON so you can just figure out how to it works and what represents what.

For example I've been able to reimplement xmltv scrapers for several sources in less than a 100 lines with Scrapy. It's not hard, just requires a little discretion.

Or you could use the API that the web app has to inevitably use.

Thanks! I saw this in a leaf comment of my original comment. Much better.

Gah, why do we need another blocking addon? Because previously blocking addons have worked out really well. Why can't this have just been a uBlock Origin list?

What's the path to production for mgmt? Is there a plan to get there? Is there a timeline?

I'm not OP, but I think your FAQ (and some other places) comes off pretty strong. It's okay to be opinionated, but your wording comes off as "everyone is wrong, I'm not".

I wouldn't say "scripting focused". It seems to have a good amount of Puppet lang compatibility. It is definitely an alternative to both Puppet and Ansible that doesn't introduce dependency hell.

Vivaldi is still Chromium based. This is WebKit based (or more accurately, the OS provided engine). We need more non-Chromium based browsers anyway.

I'm speculating here, but it sounds like the Windows version will also be the OS provided engine, which would be Edge, thus we're back to Chromium. Which is a shame considering the stink they make about it in this article.

> by blocking trackers before they load (unlike all the major browsers[0])

I certainly like that DDG is pushing for privacy oriented systems and services, but when I read things like the above, and the accompanied page, I become quite sceptical of them. They don't mention Firefox with uBlock Origin, nor do they mention Firefox's Enhanced Tracker Protection (IIRC you get asked if you want to enable on first start up).

[0] https://spreadprivacy.com/browser-privacy-protection/

> Ansible can be plenty slow at time too.

Yep, I've never been a fan of Ansible. Beyond that slowness of it, the fact that it's duct tape of YAML and shell with randomness and a sprinkle of YAML craziness make it really hard for me to like it.

For those of us not up to date, what exactly has happened? Their status page hasn't actually shown why they're having to rebuild.

Personal opinion, I'm sure many will disagree, but I've never been a fan of Ruby. It tends to be slow and, at least last time I used Puppet, there was a lot of dependency issues (from downloading them, to ensuring you run the right version of Ruby among other things). Whereas with Go downloading a single binary takes a whole lot of headaches away. Sure concurrency/performance won't matter much in the case of Puppet like software but depending on a single binary vs lots of dependency is a huge bonus.

This is a weird "open letter" but okay.

I feel like Puppet, for whatever reason, has lost out on things and Ansible won, which is quite unfortunate as Ansible is just not as good as Puppet. I wonder if Preforce will be able to revive the interest in Puppet.

Anyway, if someone plans to move away from Puppet (I imagine someone will, because someone always disagrees with a buyout), I've recently found mgmt[0] which has Puppet-lang compatibility. A big plus (to me anyway) is that it's not Ruby based, and is instead written in Go.

[0] https://github.com/purpleidea/mgmt

Yeah I was trying to figure out what was going on here. Is it blocked cos it's closing or was it blocked from before?

There is SimpleLogin[0] and Mozilla Private Relay[1] as more generic options. I've never tried them as I struggle to figure out how trustworthy they are. At the end of the day, emails are essentially proxied by these products.

[0] https://simplelogin.io

[1] https://relay.firefox.com/

> Generally my workflow when developing scripts (in Python) is to run individual functions in the repl so I can get it right.

As a matter of fact, this is exactly what I do when I write Python scripts too. It helps understand exactly what things do quickly and figure certain smaller things.

> Just wanted to reflect how made-up this sounds to those of us who treat sh like any other language.

What do you think sounds made-up?

Generally my workflow when developing scripts is running individual commands on the CLI so I can see what it's doing so I can get it right. This is not possible with fish unless I start a bash shell, so at that point, what is the point? With zsh, most of the code I would run in a bash script still runs in a zsh interactive session. Sure there a few edge cases, but they're quite well documented.

> Could you also clarify what the specific risk is of opening ports?

I guess I was meant from a firewall perspective. I understand the ports won't be listening but any potential firewall will not be able to block the port unless you have some integration to dynamically get the firewall to open and close ports on demand.

I'm assuming the bore server would have to be listening on all ports right? Doesn't that cause risk as all ports (or lots of them anyway) are open?

Also, seems like it'd be trivial to add TLS termination. I've used ngrok for it's TLS termination when developing GH Webhook listeners.

Sure, that's true. But I've been in companies where they've had major investments and have a pretty significant number of users, and they still had stupid amounts of credits. One of my previous companies was running a third of their infra on AWS credits, and they still long runway in terms of free credits.

Meanwhile, they had to shake off a £1 million a year contract for the next 5 years for 2 DCs. With AWS they were using less than half of that per year (this includes the credits they had). But even if it wasn't cheaper, requesting a new server took days, not minutes. Scaling was not possible. I'll take the credit and potentially get trapped than having to deal with an inflexible mess that is in-house managed infrastructure.

At least bigger orgs are able to afford it by (hopefully) building a cloud on top of their infrastructure, but outside that, the majority should of companies be looking into the cloud. Whether that be AWS, GCP, or the smaller Clouds like DO, it doesn't matter.

I don't know about Qt but at least GTK's docs are terribly bad. Even more so when you want to develop using a language that isn't C.

AWS gives away literally tens of thousands of pounds to start ups. Granted, it's to lock them in down the line but getting free credits gets you further than not having credits.

Cloud isn't about cost though. Cloud is about value. You can scale super easy when you inevitably need it (assuming you've "made it" anyway - whatever that means). You get a burst of new users, it's trivial to add additional nodes (again, assuming you've set up your infra to be easily scalable).

With own hardware, scaling is not as easy. You'll have to do a lot more around plumbing too. Networking, security, many other things that you'll have to address. Stuff that has already been solved for you.

Aesthetics and familiarity? It's a lot nicer to link the user's name directly to their profile, and the date directly to their tweet on Twitter as opposed to having a separately link or whatnot. For many, especially your average Joe/Jane, will expect the aforementioned behaviour.

Oh, this is the missing piece! It seems I'm blocking Twitter's JS if it's not on their site. I didn't even realise and I was confused about what the author meant as I could clearly see the tweet on their site.