[–] [S] 10 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

I saw the domain before you edited it lol. I went to the site and have zero ads on mobile, although I did have an empty placeholder in one spot where the ads would have been.

Make sure the following domains are blocked on your pihole:

html-load.cc
githack.com
cdn.statically.io
revcontent.com
pub.network

Then, make sure you have these two lines as entries on your mobile adblocker:

/ad-shield/e/*$script,third-party
/cdn-cgi/zaraz/*

If there is a specific url you'd like me to look at, feel free to message me.

Edit to add: even better than the individual domains, to add https://cdn.jsdelivr.net/gh/hagezi/dns-blocklists@latest/adblock/pro.txt as a list and then just include the githack.com domain. Pihole supports adblock syntax, so you'll be fine with this.

  • source
  • parent
  • context
  • [–] [S] 4 points 3 weeks ago (2 children)

    FYI you can point your home router to NextDNS and quickly get whole-house coverage that way. This is good for things like smart tvs, Roku/android boxes, kindles etc.

    Installing directly on your phone & laptop is best for devices that will travel outside of your home network.

  • source
  • parent
  • context
  • [–] [S] 22 points 3 weeks ago

    I've heard that before but I haven't seen an ad in years. But I'm probably not the norm. Between userscripts, ad-removing frontends like invidious and choosing services like Lemmy over the competition, you can pretty safely remove ads from most platforms. Of course, Jellyfin helps 😂

  • source
  • parent
  • context
  • [–] [S] 35 points 3 weeks ago (12 children)

    What is a DNS sinkhole

    A DNS sinkhole is a little program that sits in between your computer and the DNS server that provides your internet lookups. It looks at all of your DNS requests in an unencrypted format. If a DNS lookup from your browser, mobile app or any other internet connected machine matches an entry it has in its "blocklist" then it returns a value of 0.0.0.0 (or some other customizable value including NXDOMAIN). But if the DNS entry is not on the blocklist, then that request will be forwarded to Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9) or other DNS provider and get an accurate value for the DNS lookup.

    Most of the time, the blocklists consist of adware domains such as Google Ad Services, Facebook Ads, Amazon Ads, etc. This has the effect of removing ads from devices that normally are unable to block ads such as ads inside mobile apps, ads in Roku, etc.

    how is it related to the content of the article?

    The article indicated that the malicious spyware was transmitted through viewable ads on the target's mobile device. This is combated most effectively by using a DNS sinkhole.

    I should note that the article does not mention if current blocklists would have thwarted this attack. However, it does say that the ads were transmitted, in some instances, via Google Ad services, which these blocklists do effectively target.

  • source
  • parent
  • context
  •  

    I host my own instance of invidious behind a reverse proxy. It's awesome. I use Redirector for Firefox so that when I'm on the interwebs, YouTube videos and embeds redirect automagically to my self-hosted invidious instance. I used the setup instructions in the Invidious-Redirector documentation.

    Recently, I was on a new website and the embed didn't redirect. I tried to figure it out, but couldn't. The best I could do was try changing /embed/* to /oembed/* but that didn't work.

    So I thought I'd ask here: How would you go about setting up a rule or multiple rules to sort this?

    Edit to add: If you go to the new website, make sure you either have AI chatbots blocked in uBO or create a rule ||autonomoustechnology.ai^. Otherwise there is an annoying AI chatbot that pops up that you'll want to block.

    [–] [S] 4 points 1 month ago

    You're not wrong. If CrowdSec is your entire approach, it's a little weird. But I use it as a (small) part of my overall blocking strategy. I use other lists and frankly, block most IPs by default. Those other IPs aren't counted in the email screenshot though... only the CrowdSec based ones are coming through. I think a lot of the 137k above are just scanning bots to be frank.

  • source
  • parent
  • context
  • [–] [S] 5 points 1 month ago

    Sure. So OpnSense is the real gem here. Or really any solid firewall/edge device CrowdSec is an optional (free) add-on module in OpnSense. It's immediately operational at a minimal level without any registration. However, if you choose to register within the CrowdSec UI then you can load up more lists and tie it to your instance.

    I also load up Hagezi's Threat Intelligence Blocklists into my OpnSense firewall rules, which get updated (by him) on a rolling 12 hour basis. I also have OpnSense query Github every 12 hours to pull the updates.

  • source
  • parent
  • context
  • [–] 13 points 2 months ago

    It’s not going to be one conversation, btw. I think that’s the key thing to understand: you’re not trying to figure out how to talk to them about end of life planning one time, you’re trying to figure out how to talk to them about full-life planning maturely from now on.

    This is so important. Don't take them out and have a State of the Union dinner. That's gotta be the absolute worst way to achieve your objectives. You want many bite sized, topic-bound conversations over a sustained period of time.

  • source
  • parent
  • context
  •  

    Original post here [redlib link].

    Written by deluan

    The next release normalizes every ID in the database into a single format. It runs a one-time migration on first start. The PR with this change will be merged this weekend: https://github.com/navidrome/navidrome/pull/5824

    If you run develop or auto-update, this lands soon (this weekend) and without warning. Make a backup of navidrome.db now. The migration is one-way, so rolling back (if needed) means restoring that backup.

    The short version:

    • Takes ~30s to ~1m20s on my 96k-track library (QNAP Celeron). Scales with library size.
    • Everyone gets logged out once. Web UI and clients using the Navidrome API need to log in again. Subsonic clients authenticate per request, so they are unaffected.
    • Song IDs change, album and artist IDs do not. Clients that cache song IDs (offline downloads, cached playlists) may need a re-sync.
    • Cover art gets re-fetched, so the first browse after upgrading is slower.
    • Share links keep working.
    • Nothing is lost: favorites, ratings, play counts, bookmarks, play queues, scrobble history and Last.fm / ListenBrainz links all survive. No rescan needed.
    • One manual fix: .nsp smart playlists using inPlaylist or notInPlaylist keep the old playlist ID on disk and need updating by hand.

    Full write-up: https://gist.github.com/deluan/917ebc243c8b486101de857ffae6739b

    If you can, please test it with your favourite client once it is merged, and reply here (or on our Discord) if anything looks off.

    EDIT: For app/client developers: I'll merge the topSongsByArtistId PR at the same time as this ID migration. This means that you'll be able to detect if a server is migrated by checking the getOpenSubsonicExtensions response and looking for the topSongsByArtistId extension.

     

    Seen in a SF Muni station

    Edit to add: Jeez, relax. I was on my way home from a doctor’s appointment and saw that ad. It made me chuckle so I posted it here.

    If seeing this post really upsets you, take some deep breaths and keep scrolling. With any luck, you’ll have fully healed in a couple of days.

    view more: next ›