Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MN
Posts
5
Comments
1,044
Joined
2 yr. ago

  • OP is peddling misinformation because it's not true that "Proton took the stance" of anything.

    Except Proton's official Mastodon account made another post afterwords doubling down on the CEO's comments. They ended up taking down the post due to getting a ton of backlash

  • Then better ban all of Europe. Right now America is giving us even more reason to be anti-American.

    Aren't there several European countries with the problem of far-right parties gaining power in their governments? Germany literally just stripped firearm rights from their version of these groups earlier this week

  • No, that's actually correct. The device is at an angle, so there would be some reflections of the "top" that reach the nearly horizontal viewing angle for the "camera". I recommend looking into the topic of optics a bit

    What's actually inaccurate is that it's perfectly mirrored for the observer. That wouldn't happen in real life - the angle the device is positioned would cause the reflection of the top to be scrunched up

  • When I try to run "sudo nano /etc/systemd/resolved.conf.d/adguardhome.conf " it opens up GNU nano 7.2 and tells me at the bottom of the screen that the file is actually a directory and refuses to let me copy/paste anything into it.

    EDIT: Looks like the issue for me is with nano. It's trying to make this a directory instead of a file. I'm able to get it working with vi. If anyone is haveing the same issue, you have to delete the "file" you made with nano, then make a new one with vi before it'll work.

    That being said, the last portion regarding the DHCP conflict also isn't working, probably due to the formatting not being specified.

    EDIT2: Looks like the real issue for fixing port DNS port 68 (the DHCP conflict) is a bit more complicated. There's multiple different possibilities for what the file you need to modify can be named.

    Personally, the solution I'm going with is to just disable port 68 for adguard. According to this source, the only downside is having your router handle DHCP, which I'm fine with at the moment. The source I posted refers to port 67, but it works for port 68 as well.

    If anyone reading this would prefer to let Adguard use port 68 by setting up a static IP address, This guide is more detailed and also includes some of the variances in filenames you might come across to better solve the problem for your setup.