🇨🇦

  • 7 Posts
  • 246 Comments
Joined 3 years ago
cake
Cake day: July 1st, 2023

help-circle





  • Anecdotal; but I spent 5ish years pirating via torrents from my home in Canada. Never once used a VPN and received an emailed copyright notice forwarded through my ISP about once every 3-5 days.

    They never went further than that. The ISP isn’t permitted to give out my personal contact info short of a court order, and the copyright holder(s) can’t be bothered to pursue it further to get that info.

    As long as you never reply to the notice; all they have is an IP, a time stamp, and a copy of the letter they sent to the ISP. They don’t know who I am to drag me to court; so first they’d have to sue the ISP for that info. Even then, tieing one specific individual to an entire IPs traffic is next to impossible. Was it the IPs subscriber? Another person in the household? A guest? Someone with unauthorised access? Too many variables/possibilities to prove ‘beyond reasonable doubt’ in a court of law.

    Now a days however I use usenet. $12/year for an indexer, and ~$5/month for access to a usenet provider/server. Fast reliable downloads that always complete within 5min. No more waiting on slow or seedless torrents that potentially take days before giving up and trying another. This is all done though an ssl connection to a private server, so there’s nothing to snoop/get reported for.


  • If you have a static IP address, you can just use A records for each subdomain you want to use and not really worry about it.

    If you do not have a static IP address, you may want to use one single A record, usually your base domain (example.com), then CNAME records for each of your subdomains.

    A CNAME record is used to point one name at another name, in this case your base domain. This way, when your IP address changes, you only have to change the one A record and all the CNAME records will point at that new IP as well.

    Example:

    A example.com 1.2.3.4

    CNAME sub1.example.com example.com

    CNAME sub2.example.com example.com

    You’d then use a tool like ACME.sh to automatically update that single A record when your IP changes.




  • I don’t really see this as surprising. Drones have been used in mass coordinated swarms for things like new years light displays for years.

    It was only a matter of time that gets used as a weapon system/platform.

    A swarm doesn’t give you much advantage over a single drone though. There’s more targets to shoot down, so perhaps there’s a better chance of getting one through drone defenses; but they also lose the stealth factor a single drone brings… Maybe a really wide surveillance view if you combine their camera feeds?

    IDK, doesn’t really seem all that beneficial.









  • :/ shit.

    I’m pretty sure I saw this a few months ago and moved to the beatkind/watchtower fork, but it’s not been updated in 6mo either. (Devs only been active in private repos; so they’re still around, just not actively working on watchtower)

    Guess I’ll find another solution. Hell, I might just put my own script on crontab. Looping through folders running docker compose down/pull/up isn’t too hard really.



  • Darkassassin07@lemmy.catoSelfhosted@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    2 months ago

    A bit of redundancy is key.

    I have my primary DNS, pihole, running on an RPI that’s dedicated to it; as well as a second backup version running in a docker container on my main server machine.

    Nebula-Sync keeps the two synchronized with eachother, so if a change is made on one, it automatically syncs to the other. (things like local dns records or changes to blocklists).

    If either one goes down (dead sd cards, me playing with things, power surges, whatever); the other picks up the slack until I fix the broken one, which is usually little more than re-install, then manually sync them using piholes ‘teleporter’ settings. Worse case, restore a backup (That you’re definitely taking. Regularly. Right?)

    Both piholes use Cloudflared (here’s their guide *edit: I see I’ll have to find a new method for this… Just going to pin the containers to tag ‘2025.11.1’ for now) to translate ALL dns traffic into DOH traffic, encrypting it and using the provider of my choice, instead of my ISP or any other plain DNS. The router hands out both local DNS IPs with DHCP because Port 53 outbound (regular dns) is blocked at the router, so all LAN devices MUST use the local DNS or their own DOH config. Plain DNS won’t make it out.

    DNS adblocking isn’t perfect, but it’s a really nice tool to have. Then having an internal DNS to resolve names for local-only services is super handy. Most of my subdomains are only used internally, so pihole handles those DNS records, while external DNS only has the records for publicly accessible things.