I have been using this alongside MyFitnessPal and it is great! I look forward to getting rid of MFP so my data is mine.

The dev is responsive and quick to fix bugs and implement features, too. Thanks @TraceApps@lemmy.world!

Actually, I moved it to a proper repo. I also created a script to get the proper food diary info from MFP.

https://github.com/nomad64/mfp-to-nutritrace

Yeah, feel free to link to it or integrate it into NutriTrace directly. MFP doesn’t allow users to export a lot of their data and what they do allow is pretty minimal (ex: food diary doesn’t export the food diary, simply a diary of each meal).

I don’t plan on supporting it, so it might break whenever MFP decides to update their API. But I am just glad if it helps even one person.

I created a helper script to export custom foods from MFP and store them in the NutriTrace JSON format, in case you find it helpful. https://gist.github.com/nomad64/87cf935d8373d730383c5a0e98693c94

Nice! I will have to look into this when I have time in the coming weeks. Looks like a cool project!

Is there a way to migrate a food diary from another app like MyFitnessPal?

Link to the interview where this article seems to be deriving its information from: https://www.pbs.org/newshour/show/whistleblower-responds-after-doj-confirms-doge-mishandled-social-security-data

A consolidated (and structured) torrent file has been released: https://github.com/yung-megafone/Epstein-Files/issues/1#issuecomment-3860836655

Currently clearing data from my seedbox to get this added.

Thanks for the links. I downloaded the docs and will add them to the pile.

I don’t see this posted here yet. Below is the Github repo link for an index of torrent files, DOJ links, and mirrors, for every dataset. https://github.com/yung-megafone/Epstein-Files

I have been seeding all of the datasets since Sunday. The copy of set 9 has been the busiest, with set 10 a distant second. I plan on seeding them for quite a while yet, and also picking up a consolidated torrent when that becomes available. Hopefully you are able to get connected via the Swarm.

I am a Plex guy and host Jellyfin along with other various services that aim to de-Google my family members and friends.

I give out Plex access pretty readily and don’t charge for it. Honestly, companies and governments are more focused on the “big fish” IPTV private providers than randos like us hosting media servers.

Still working on de-Googling people…

I am seeding sets 1-8, 10-12, and the larger set 9. Seedbox is outside the US and has a very fast connection.

I will keep an eye on this post for other sets. 👍

Not sure if it is open source, but I switched to ReoLink a while back and have been very happy with it. Good Home Assistant integration, no subscription, and everything can be local (store video clips to an onboard SD Card).

I have been using various Debian-flavored Linux variets for several years in both desktop and server.

Recently I got a System76 laptop for work because they are food quality, repairable, and mostly “just work”. The main issue I have run into is Cisco Secure Client (formerly AnyConnect) simply breaks in Ubuntu/PoP. If I do get it to install by ignoring Cisco’s shitty instructions, it either won’t route traffic once connected or corrupt itself attempting to auto-update.

It is purely a Cisco issue because they don’t put much effort into their Linux VPN software. Other VPNs not only work easily, but can also integrate into PoP Cosmic. Cisco and their restrictive nature just make the process impossible.

Heck, you can’t even download their VPN software without a Cisco contract. So if my company doesn’t provide the correct version or distro package, there is no way for me to get it. Since most people on the helpdesk don’t know anything about Linux, they simply provide the generic Linux.tar.gz file instead of the DEB or RPM files.

I gave up and installed Windows on a second NVMe.

I will save this one for work!

Definitely looks like a storage array. Based on how the drives look, maybe an EMC Clariion (CX or CX3 model)?

I have used Docker Swarm in my homelab for years without big issues, you just have to be aware of its limitations. For example, I use SWAG for my reverse proxy and it works better as a compose deployment on an individual docker node because then it can identify incoming IPs. All of the backend communication runs on internal networks, which helps isolate them.

I like using Swarm at home because it is simple and easy while providing good scalability and security (yes, I know podman would be more secure, but I haven’t taken that plunge yet).

That being said, Docker Swarm isn’t used in the industry much. So if you are looking to expand on your IT skills, K8s is the way.

Each network is different. I did this for my network which has multiple subnets and internal DNS servers sitting on the “server” subnet. The “server” subnet is excluded, since devices in there are more tightly controlled (and it would create a routing loop).

Granted, it may not be the best way, but here is how I did it:

• Create Firewall Alias group (type: hosts) with IP addresses of internal DNS servers (PiHoles, in my case).
• Create Firewall Alis group (type: URL Table IPs) for external DNS over HTTPs servers (content: https://raw.githubusercontent.com/jpgpi250/piholemanual/master/DOHipv4.txt)
• Create NAT Port Forward to route all traffic on port 53 to the alias (TCP/UDP, source: network, destination: !network on port 53, redirect target: DNS alias, redirect port: 53) for each network
• Each network (except the “server” network) has the below rule set (order is important)
  • Allow TCP/UDP 53 to DNS alias
  • Drop all TCP/UDP 53
  • Drop all TCP/UDP 853
  • Drop all TCP/UDP 443 traffic to external DNS over HTTPs alias group

Since NAT port forward rules are processed before interface/network rules, any device using port 53 for DNS (regardless of the IP address they have set) will automatically (and transparently) get redirected to my PiHole servers. The drops are in place so devices that try to use other common DNS methods are blocked. Generally, those devices will then default to the DHCP DNS servers.

I have been running this config for a few years and have found a few downsides:

• You can’t visit websites that have the same addresses as their DNS hosts, ie: https://1.1.1.1/
• Although https://github.com/jpgpi250/piholemanual is updated regularly, it has contained the odd false-positive (GitHub pages had a weird overlap at one point) breaking legitimate HTTPS traffic
• My PiHole servers are configured to allow queries from all origins (theoretical security risk)

Hope this helps! And remember to be careful when messing with DNS and clear those caches when testing.