MeowdyPardner

I’ve been happy with the tp link TV-IP324PI, it’s a Poe bullet cam with a simple web interface (I don’t think it requires JS, but at any rate you just need to log in once to set a password, make sure upnp is off, and adjust camera/encoding/fps/text overlay settings to your liking). There’s also the amcrest IP5M-B1186EW-28MM, another similar Poe bullet cam with night vision that works local only. I’ve used both for several years and I think they support onvif but I had no issues using the rtmp url with zoneminder

I think a blocklist of common sources of biased and sensationalized / misinformation sources would be the best option. It would definitely be a ton of work to whitelist every good source, and you especially want to encourage smaller trusted industry-specific sources (think like pv magazine), there are a lot of those small high quality sources that are geared towards industry professionals. With a short blocklist you could probably cover a significant portion of the loudest biased sources of misinformation.

I actually just saw that Dansup is working on adding optional opt-in support for PhotoDNA in pixelfed if an instance admin adds a PhotoDNA API key, I wonder if that was spurred on by this report. Hopefully Mastodon also looks into adding support.

I would recommend getting a separate client radio device for several reasons:

• You can position it better for reception
• Get a device with directional antenna so you can point it at the best AP
• You won’t use up 1 band of a dual-band router
• You won’t be limited in your main router firmware choice to only those that support client mode on a radio

Personally I would get a nanostation loco 5ac (non-loco is bigger and probably isnt needed) and flash openwrt on it (that will free any airmax radio from the proprietary airmax limitation), configure the 5GHz radio to client mode with the apartment wifi details, and put in the desired mac into the mac field if you need a specific mac besides the device default. Make sure the radio is set to wan zone so that forwarding works and plug the lan cable from the radio to the WAN of whatever nice router you have.

I used to carry around a nanostation with this config set to xfinity access points with a small script that would pick a random MAC from a list I gathered from wardriving client MACs that I saw authenticated with xfinity hotspots. That way if I ever needed an ethernet connection for a non-wifi device I could just power up the radio and run the script to pick a new mac until I got one that was “remembered” in someone’s xfinity account.

Edit: to clarify, I think the way I set it up was to run dhcp client on the radio’s uplink and then hand out IPs via dhcp server on the lan port, so I think you’d be triple natted, but since you would need to double nat anyway to get around the MAC authorization it probably isn’t hurting speeds any more than it already would be.

Lately I’m the second one every day of the week

I recently switched from mullvad to Mozilla and it’s been a smooth transition. I don’t worry that much about some logging because I just need something to connect my torrent client to so I don’t get a letter. I used to have a subscription on mullvad but they got rid of recurring subscriptions like last year, and when I went to change my payment method I got locked out and forced to use one time refills.

I don’t like that they force you to use their app though, so I’m still shopping around for alternatives that can just give you the ovpn or wg.conf since an all obviously can’t be run on my router or my synology

I think this answer is the most accurate. People get too hung up same names on different servers. There will always be multiple versions of a community whether they have the same name on different servers or whether one of them snagged the og name and others prefixed with Real_x / True_x. Imo I like it this way better because there’s less favoritism to the one that comes first / people can’t universally squat on a community name

This is the solution. I reverse proxy from a digitalocean droplet running haproxy which sends traffic via send-proxy-v2, then I set the tunnel subnet as a trusted proxy ip range on traefik which is what haproxy hits through the tunnel, which causes traefik to substitute in the reverse proxied original ip so all my apps behind traefik see the correct public IP (very important for things like nextcloud brute force protection to work)

Swipe typing is the only thing that keeps me using google keyboard. Their implementation is the only one that works well for me. I think I used to use Swype before, that feels like forever ago

Hmmm yeah this does seem to be proxying login info. Ideally it would be done like elk.zone and mastodon where it kicks you out to an oauth flow that returns with an app token you can later revoke in your account settings. But I’m guessing that doesn’t exist for lemmy yet.

On the bright side the UI looks amazing

It uses the zip archive feature that they allow you to request and export so at least it doesn’t use a direct connection or API. I think there is also some EU rule or something about requiring it because Dansup was asking about filing a complaint because of the export format being convoluted or something, not sure of the details but hopefully that means there’s some legal weight to the export feature sticking around.