lub

OVH prominently uses water cooling including custom components with their own design.

https://blog.ovhcloud.com/water-cooling-from-innovation-to-d...

https://blog.ovhcloud.com/water-cooling-from-innovation-to-d...

https://blog.ovhcloud.com/new-hybrid-immersion-liquid-coolin...

> One of the big advantages of DDG's bangs is that you don't have to re-type/paste the whole search query. Instead, you click the search bar in DDG, type `<space>!g<enter>`. That's vastly simpler and faster than re-typing the query, then `<space>!g<enter>`.

At least in Firefox you can also re-enable the search box and just use that. It's even accessible via it's own shortcut (ctrl+k).

> Moving the feature into a plug-in was a really dumb move though. It totally killed discoverability of this unique selling point of Firefox.

It's actually usable now without extra addons. Just right click the "+"/new tab button or go to about:preferences#containers diretly.

Did you try this?

  networks:
    - host

https://docs.docker.com/network/host/

That's one of the reasons I like matrix. Real multi-client support within the same account and each client is independent of each other.

Sounds like the customers' data itself is still available?

> All customers should immediately download backups of their websites and databases through cPanel.

I currently use sway on a 35" WQHD and a 14" notebook and IMO tiling window managers are actually more useful on large monitors.

On small screens I often have programs in basically fullscreen, because of the limited space. But the bigger the screen the better you can actually tile it beyond simple half/quarter splits.

TLS doesn't necessarily mean everything is encrypted with FTP, because data and control channel have to be encrypted independently.

See for example https://security.stackexchange.com/a/115565 or https://en.wikipedia.org/wiki/FTPS#Secure_data_channel for more detailed explanations.

Most of the time both are encrypted when configuring TLS, but it's not as easy as with IMAP or SMTP where you basically disallow all commands except STARTTLS.

Why TLS-SNI-01 was disabled: https://community.letsencrypt.org/t/2018-01-09-issue-with-tl...

Explanation that renewals will be disallowed after 1 year deprecation period: https://community.letsencrypt.org/t/march-13-2019-end-of-lif...

And as you seem to be talking about ACMEv1/v2 instead of TLS-SNI-01 (which I originally thought); it will be supported as long as June 2021 in some cases: https://community.letsencrypt.org/t/end-of-life-plan-for-acm...

ACMEv2 was introduced, because it is much closer to the actual spec. Enforcing this ensures that there are actually ACME implementations out there, instead of proprietary "Let's Encypt ACME" implementations. https://tools.ietf.org/html/rfc8555 https://github.com/letsencrypt/boulder/blob/master/docs/acme...

To me this seems like a sensible compromise between backwards compatibility and their mission for standardized automated renewals.

I think the author is confusing three things:

* Let's Encrypt - the actual CA

* certbot - probably the mentioned python software

* ACME - the protocol, which had a change in the supported challenges

Also there are alternatives for all three points. There are other CAs implementing ACME, there are other ACME clients and there are still CAs supporting the old 'send an email and click a link' domain validation.

And sid (unstable) is the neighbor who breaks the toys, which is why the name never changes :)

> It's like saying I bought a petrol car but I should have a legal right to fill it up with Diesel or make it work with electricity. It's illogical. The packaging said petrol and so I knownlingly bought petrol.

Though it's not really uncommon to modify a car for autogas or electric. Often it's also possible to change the radio receiver to e.g. one with android car.

I kinda expect the same freedom to modify other products including smartphones.

Enterprise IT people here. We cover our ass in true enterprise style by consuming website filter lists from a provider and MitM TLS. Doesn't matter if they use WebRTC or HTTP, as long as the website is in the correct categories.

Worst case we could disallow WebRTC via DPI and whitelist it for category conferencing.

employee (A) should've setup auto renewal

> chat

This already exists: https://chat.mozilla.org/

You can use it with your Firefox account.

it's just a cube

Although I think it's still a long way to usable and interoperable p2p, matrix does support voice+video chat (in 1:1 chats p2p with signaling via matrix; otherwise via jitsi meet integration).

3rd party identifiers like phone numbers and email addresses can be registered and discovered via centralized service. At least for phone numbers it's not really possible decentralized.

The picture suggests this is Super_L, a key most people use all the time. Typically you use it to open some global menu or shortcuts related to your window manager.

Windows devices normally have a Windows logo printed on that key. Purism just decided to print their logo instead.

What you want is named delegation and there is a document about it in the synapse repository:

https://github.com/matrix-org/synapse/blob/master/docs/deleg...

Just in case you weren't already aware of it :)

Is ctrl+c handled; by the terminal emulator?

ctrl+l allows to clear when the prompt is non-empty, maybe parent poster meant that

afaik jitsi.riot.im (the Jitsi Meet instance used by Riot) is provided by New Vector, not Atlassian

You have to use the Mozilla SSO and use one of the login options there. Removing the registration link is an open issue.

You have to click on "Sign In" and use the Mozilla SSO. Hiding the registration link is an open issue.

relevant: https://pretix.eu/about/en/ , which is used e.g. by the 36C3

There is progress on Python 3 support:

> Preparation for py3 (PR #3061, #3073, #3074, #3075, #3103, #3104, #3106, #3107, #3109, #3110) Thanks to @NotAFile!

https://github.com/matrix-org/synapse/releases/tag/v0.28.0