sending personal data to someone else’s computer.

I think this is spot on. I think it’s exciting with LLMs but I’m not gonna give the huge corporations my data, nor anyone else for that matter.

An ultra-marathoner’s attempt to “run” from Florida to Bermuda in an inflatable bubble was cut short when the Coast Guard towed him back to land – for the second time.

https://edition.cnn.com/2016/04/25/us/bubble-man-rescue/index.html

Gonna check it out!
Is it easy to setup automatic responses to the alerts, f.e. restarting a service if it isn’t answering requests in a timely manner?
Have you used it together with Windows Servers too?

[email protected]

There are private GPT solutions coming, f.e. https://www.fujitsu.com/global/products/data-transformation/data-driven/ai-test-drive/
They are aimed at companies that for compliance reasons want to self host.

I wouldn’t trust an llm solution with sensitive information unless I host it myself.

I’ve used SNMP a lot together with nagios so I should be able to handle it. :D

I’ll have a look! Cheers!

Cheers! I’ve heard of Prometheus/Grafana but VictoriaMetrics was a new one. Gonna look into it!

For signal I imagine you’ll find the best answers here:
https://github.com/signalapp/Signal-Android/blob/main/CONTRIBUTING.md
https://community.signalusers.org/c/development/android-development/22

The simple solution is to use another cloud, such as proton drive mentioned below.

Another more technical solution is to setup a vpn at home and use vpn + smb to share files with your phones, this one fails if your computer isn’t always online at home or if your internet provider runs CGNAT.

Your computer could be replaced with a selfhosted solution as nextcloud running on separate hardware, but now we’re firmly in selfhosting land.

The VPN home could be replaced with a VPS that both your home network and mobile devices connect to as a CGNAT workaround.

The KISS (Keep it simple, stupid) principle says that getting another cloud storage is the way to go. If you truly wanna own your cloud then a trip to selfhost land it is.

" in" appears 25 times on the page to be exact, with 16 of those being in the table of contents and 9 being in the text afterwards.
“in” appears 54 times, as you know end up hitting “string” and so on.

Had I known that the functions table of contents was as short as it is I would probably have just scrolled.

After which ctrl+f " in" takes you to the correct chapters. I do agree that a direct link would be more helpful.
And for learning postgresql I agree it isn’t very helpful - using their tutorial links, w3schools or something like udemy if you prefer video format is the way to go in that use case.

I remember back when you were told to learn to work with the documentation, not memorize it, because you will always have access to it as a reference. Maybe bookmarking reference books/documentation will make a come back as the search engines degrade.

Your result returns version 9.0 that went EOL 2021, same as Googles fourth result in OP.
nvm, second result is correct.

I definitely feel the pain when it comes to worthless results nowadays. Though in this case DDG comes through:

Adding documentation to the search makes the “correct” page soar to the top:

Telemetry, licensing and proprietary extensions in VS Code is the whole reason for VScodium to exist.
https://github.com/VSCodium/vscodium

For the curious:
https://lemmy.world/modlog?page=1&userId=6830423

For details follow the link. This is nothing more than the headlines.

Finances
The GNOME Foundation reserves policy says that the buffer is too low to run at a deficit any longer, which it has done for three years. This years budget is a break-even budget.

Strategy & Fundraising
A five year strategic plan has been prepared and a draft approved by the board. A variety of fundraising activies will be launched over the coming months.

Board Development
More directors are being added to reduce workload on individual board members. Non-voting officer seats will be added for the same reason.

Elections
Annual board elections is coming up, 6 seats are being elected.

I consider client devices to be a big risk factor and if I can keep them from having direct access to the Backup NAS and the IoT I consider that a big win. A simple ransomware attack on a client device would find any NFS/SMB shares the client can access and start encrypting - having the Backup NAS on a separate VLAN that only the server can access stops most of those from affecting the backup and makes restoring a lot easier. I would definitely recommend having an offline backup of the NAS as well in case of the server being breached.

I agree with this, protecting everything behind a VPN is the way to go. I help friends setup their vpn client to my stuff if I want them to access an internal service.

• Single switch, yes. Personally I would probably aim for a managed (must have for vlan support) switch with at least 16 ports where 8 has PoE+ (Power over Ethernet) with at least 100W total budget. The goal would be to power access points and that security camera through PoE instead of separate psus.
  A cheaper alternative is to skip PoE for now and buy an 8-port managed switch now and a secondary PoE switch in the future if need be.
• There are access points with VLAN support, so you can have an access point deliver multiple SSIDs that belong to different VLANs. Two things to look for here is Local Management and PoE powered. You don’t want your access points to become paper weights when the cloud management system is shut down. I don’t want to use cloud management at all to be honest.
• PoE allows you to protect your camera and your APs with the same UPS you put in to protect your network rack.

Draw up some plans beforehand, quick example where I forgot your video doorbell that would be on a separate SSID/VLAN through the APs if it uses WiFi. Which is kind of the point with drawing it up. It helps you find out what you missed.

edit: And that is just an example on how to draw it up. I imagine you want your security camera and doorbell to save video on the NAS, so then their vlan need to be able to communicate with the NAS vlan, as another example of missing stuff in the drawing.