You cannot really hide it. The launch has to be public to warn airplanes and ships so they can avoid the area. And once the launch is public, such a failure is quite evident to anyone who was interested in following it, so you might has well publish the news instead of trying to hide the unhidable.
By quantity of oil, I would think an oil spill is more damaging.
However, the damage from the sum of all oil spills pale in comparison to the damage of burned fossil fuels. But that’s because we try not to spill oil too much, that’s expensive to waste it.
Defense money is not lost, it pays people within your country. And you can even decide whether it goes to big corps or small companies.
Sorry, my autocorrect changed its into it’s.
Overlay it with a map of electricity emissions and it will fit nicely with a few small exceptions (like any small country neighbouring Poland, they will have bad air regardless of their own production).
Tailscale surprisingly was the fastest, even faster than plain Wireguard, despite being userspace. But it also consumed more memory (245 MB after the iperf3 test!) and CPU.
Do we know if this is a variation due to the test protocol or Tailscale is using wireguard with specific settings to improve, slightly, its speed?
With Tailscale and other mesh VPN, by default all your machines are client and servers. If you have 3 machines A, B and C, when machine A wants to send something to B it will connect to the server that B has.
These mesh VPN have a central server that is used to help with the discovery of the members, manage ACLs, and in the case one machine is quite hidden and not direct network access can be done act as a relay. Only in that last case do the traffic go through the central server, otherwise the only thing the central server knows is that machine A requested to talk to machine B.
You still have to trust them if you want to use their server, but you can also host your own server (headscale for Tailscale). Though at this point you still need to somewhat trust Tailscale anyway since they re the ones doing the client releases. They could absolutely insert a backdoor and it would work for a while until is is discovered and would then totally ruin their reputation.
One thing to keep in mind is that the websocket sync is not straightforward to set up with vaultwarden and the proxy. If you don’t have it working, then your client does not necessarily sync on every change.
Maybe this is related to this, with sync not being performed by the client you were using for modification?
If you are in an enterprise environment, it is easier to sell Ubuntu - at least there is a company that can provide support for it behind. Companies want to make sure someone is on the hook to fix an issue that would be blocking to them, and this is much harder with something like Debian.
That’s why Red Hat is used that much in companies, and what Canonical main revenues are coming from.
But as a selfhoster, I use Debian by default for my servers. Only if there is a very specific need for Ubuntu would I switch, and I am frankly tired of the Snap shenanigans on my desktop (thinking of migrating to PopOS or KDE Neon).
I don’t know if there is any specific utilities for that. You can always export your settings and reimplement them in lldap: this should be doable with a python script.
I never really understand why LDAP was so complicated. There must be needs in big setups that I am aware of but strangely I always found it not intuitive.
Yes, same for me. On android DAVx5 is perfect, and on MacOS, iOS there is native support. For Linux and Windows, your mileage may vary (fairly easy on Linux but very different variations and some require additional software).
It supports a proper sync (my wife’s shared events do show up on my phone and I can modify them there) and the address book is specific to each user by default, but you can create shared address books as well. Again, that is synced two ways.
For LDAP, by default nextcloud only reads it. But you can enable LDAP writing as well.
I do this with nextcloud (and lldap for the user management). Though that could probably be overkill for just contacts and calendars.
How were you even able to cross the parking lot? It’s not like the Toyota Camry can ever return the salute so would you basically become stuck in a salute forever?
If you use the linuxserver.io image, as of last month yes. They migrated to everything updated through the docker container.
I’ll provide an ELI5, though if you actually want to use it you’ll have to go beyond ELI5.
You contact a web service via a combination of IP address and port. For the sake of simplicity, we can assume that domain name is equivalent to IP address. You can then compare domain name/port with street name/street number: you need both to actually find someone. By default, some street numbers are really standard, like 443 is for regular encrypted connection. But you can have any service on any street number, it’s just less nice and less standard. This is usually done on closed networks.
Now what happens if you have a lot of services and you want all of them reachable at address 443? Well basically you are now in the same situation as a business building with a lobby. Whenever you want to contact a service, you go to 443, ask the reception what floor they are in, and they will direct you there. The reception desk is your proxy: just making sure you talk to the right people.
Looks like they had to respond again
https://www.reddit.com/r/pics/comments/14rn8zd/the_rpics_moderators_cant_respond_to_reddit/
/u/ModCodeofConduct,
Thank you for your recent message.
We appreciate your concerns regarding /r/PICS being marked as NSFW, and we hope that you will be reassured by our response. In short, the shift in question was not a sudden change, nor is there any risk of users being confused… and most important of all, an abrupt reversion would itself constitute a violation of the site-wide rules that you cited.
On June 16th, 2023, /r/PICS (then /r/Pics) asked its subscribers to vote on the state of the subreddit, and they overwhelmingly decided to feature only “images of John Oliver looking sexy.” On June 20th, 2023, a second poll was held, and it was determined that “any and all media featuring John Oliver” would be allowed. This also precipitated a change in the subreddit’s name from “/r/Pics” to “/r/PICS,” with the latter being an acronym for “Posts Illuminating Comedian’s Sexiness.”
As we moderated /r/PICS, however, we discovered that large amounts of profanity and offensive content – both of which are listed as NSFW by Reddit’s policies – were present in non-NSFW threads. This was problematic, as users expecting work-safe experiences were very likely to encounter non-work-safe material. Rather than abruptly alter our rules without first consulting the community (which would have confused users), we asked on June 26th, 2023 for subscribers to refrain from offering any NSFW content in non-NSFW threads.
We also requested a response from Reddit on that same date.
By July 3rd, 2023, the amount of profanity and offensive content in /r/PICS had not declined, and Reddit had not responded to us. It was publicly announced that we had no choice but to mark the subreddit as being NSFW, so as to adhere to Reddit’s own mandates. It was also made clear that our longstanding rules – rules which should have seen /r/Pics (in any form) being a NSFW community from the get-go – would be unchanged; that neither gore nor pornography would be allowed, but that tasteful nudity, profanity, and “offensive” content would continue to be acceptable. To reiterate, while we do celebrate a British comedian’s undeniable allure, we do not allow anything sexually explicit to be posted.
Our surfaced resources – our sidebar, our rules, our wiki, and our announcements – make all of this exceptionally clear, but since Reddit provides no method by which users can be required to read said resources before participating, the visible marking of /r/PICS as NSFW is vital to establishing reasonable expectations. Furthermore, as Reddit assures its partners that their advertisements will not run alongside profanity or offensive content, the aforementioned marking is also in said partners’ best interests. That same assurance indicates that moderators “set their own standards for conduct and ‘appropriate’ content,” indicating that /r/PICS is solely responsible for determining what is and is not offensive (and policing accordingly). A failure on our part to appropriately list /r/PICS as NSFW would therefore run counter to what advertisers have been told.
We do understand that the shift may have caused some minor issues for Reddit, however, and as we have no desire to harm the platform, we are more than willing to discuss the situation with you. Please respond to our previous request for communication, and we will look forward to exploring productive paths forward. In the meantime, to ensure that /r/PICS is adhering to all of Reddit’s guidelines and requests, we would be happy to revert the NSFW setting, restrict posting, and remove any and all content that could be considered “offensive” by anyone. If this compromise does not meet with your approval, please offer a publicly visible comment in response to our open letter. We understand that you are likely very busy, so we will wait until Friday, July 7th before taking any additional steps.
I did consider it, and I have not cancelled the old one yet. But that becomes more expensive than migrating to the higher end plan without CG NAt of the provider.
I have been using Bookstack, I like it though it is missing a few features I would love: