Hacker News new | past | comments | ask | show | jobs | submit | gh02t's comments login

Checking your own IP on Shodan to see if any unexpected services are detected is a good starting point.

There are ways now (as in, very recent) to bypass the ONT for AT&T, people have developed custom GPON SFP module firmware that lets you connect directly. There are also multiple ways to bypass the gateway authentication, be it extracting the certificates or doing Ethernet proxying of the authentication frames.

That’s cool to hear! Sounds like it will need a weekend project some time

Not using Arch anymore, but I did have this issue recently on OpenSUSE Tumbleweed. I switched KDE to Wayland (defaulted to X11 for some reason) and the issue went away. Worth a try if you haven't already.

Thank you for the tip! Unfortunately I can't use Wayland because it breaks the AFK detection in Discord. I would actually prefer to use Wayland, but Discord Linux support is real bad. That said I'll have to take a look because maybe there's a solution that didn't exist last time I tried. And worst case scenario, I can at least decide which bug is less bad.

While I can't personally understand why you'd want to give Discord and its advertisers free information about your application usage habits, issues like these are endemic to rather a large number of Electron apps whose developers refuse to keep the framework up-to-date. Supposedly the issues will go away when they upgrade to modern Electron, and then I'll know for sure just how good the Flatpak jails are at blocking that nonsense.

An off the wall solution might be to bridge Discord to Matrix with https://docs.mau.fi/bridges/go/discord/index.html and then use a Matrix client, but no idea how well the bridge supports AFK detection as I haven't used the Discord one. Generally the other bridges to Matrix I have used support status and presence pretty seamlessly, though. Don't think any of the bridges support voice chat, however, so depends on what you use Discord for.

Also perhaps try Discord in the browser instead of the desktop app?

Just some random thoughts to try.


Counterpoint/anecdata, I've had 3 MX Master mice and 2 died in under a year and the third lasted about 2 weeks past the 2 year warranty expiration. And this was babying them, no mistreatment.

I gave up and switched to a clone (Rapoo MT760) that I actually like more.


Meshtastic let's you select different compromises between throughput and range. The main limitation is that everybody has to agree on the same setting up front to be able to communicate with each other within a network.

The default (and most widely used, including on the de facto public channel) setting is one of the longer range options and gives you around 1 kbps, and it's quite usable on the default for normal texting and positioning telemetry with a handful of active users in my experience. The fastest setting is over 20 kbps and still gets ok range, the slowest is a mere 0.09 kbps and is only useful in some limited scenarios.

It's legitimately useful, and I actually use it regularly. Mostly for hiking, as I do a lot of hikes where we split and meet up. It's also far cheaper than commercial options, and getting close to being as polished as the commercial options like Beartooth or GoTenna.

https://meshtastic.org/docs/overview/radio-settings/


It's much cheaper to just buy an optical HDMI cable if you need a long point to point run, it's like 50 bucks for 100 ft. The cool stuff you can do with HDMI over IP lies in switching the signal to different endpoints on demand and things like multicast to multiple receivers, both of which are things you can do with off the shelf HDMI over IP gear.


Yeah, OP is comparing this to Google/Amazon/Apple/etc devices but this is being developed by the nonprofit that manages development on Home Assistant and in cooperation with their large community of users. It's a very different attitude driving development of voice remotes for Home Assistant vs. large corporations. They've been around for a while now and have a proven track record of being actual, serious advocates for data privacy and user autonomy. Maybe they won't be forever, but then this thing is open source.

The whole point is that you control what these things do, and that you can run these things fully locally if you want with no internet access, and run your own custom software on them if that's what you want to do. This is a product for the Home Assistant community that will probably never turn much of a profit, nor do I expect it is intended to.


> Yeah, OP is comparing this to Google/Amazon/Apple/etc devices

Thanks; it seems I actually needed to spell that out in my post.


THANK YOU. I've been looking for something like scanservjs for ages as a web frontend to my network scanner to feed Paperless. For whatever reason I never could find something when I would search. That looks like exactly what I wanted, penciling it in for a weekend project.


Apart from eBay and specialized reseller websites you can actually find some good deals on used enterprise gear onAmazon through third party stores. I've bought a few different things and had excellent results universally. The real trick is just knowing what to search for, which servers or computers are popular in enterprise and on the end of their lifecycle. Dell, HP and Lenovo servers and mini PCs that are sold to enterprise and are a couple generations old are what to look for.


> I deploy my self-hosted stuff with Docker, which means that not only does each device need to have the root CA added to it but every Docker image that talks to the internal network needs to have it as well. This ends up being a mix of the previous two problems, as I now have to figure out how to mount the CA on an eclectic bunch of distros and I often then have to figure out why the dockerized application isn't using the CA.

FWIW, I solve this problem with wildcards + a central reverse proxy for containerized apps. I host most services on a subdomain of the machine that hosts containers, like "xxx.container.internal", "xxx2.container.internal", etc. Instead of each container doing it's own SSL I have one central reverse proxy container that binds to 443 and each app container gets put on an internal Docker network with the reverse proxy. Reverse proxy has a wildcard certificate for the host system domain name "*.container.internal" and you can just add an endpoint for each service SNI. I'm using Zoraxy, which makes it very easy to just add a new endpoint if I install a new app with a couple clicks, but this works with lots of other reverse proxies like Caddy, Nginx, etc. If containers need to talk to each other over the external endpoint for some reason and thus need the root CA you can mount the host system's certificate store into the container, which seems to work pretty well the one or two times I needed to do it.

I haven't really solved the annoyance of deploying my root CA to all the devices that need it, which truly is a clusterfuck, but I only have to do it once a year so it isn't that bad. Very open to suggestions if people have good ways to automate this, especially in a general way that can cover Windows/Mac/iOS/Android/various Linuxes uniformly since I have a lot of devices. I've experimented with Ansible, but that doesn't cover mobile devices, which are the ones that make it most difficult.


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: