synestine

joined 2 years ago
[–] synestine@sh.itjust.works 1 points 4 days ago (1 children)

Is the one listed on Flathub not official?

https://flathub.org/apps/org.signal.Signal

[–] synestine@sh.itjust.works 0 points 2 months ago (1 children)

Ah, so you're the kind who loves removed about things online, but won't lift a finger to defend themself, gotcha.

What I mentioned prior doesn't change anything about library management in the slightest, you just wanted an excuse.

[–] synestine@sh.itjust.works 5 points 2 months ago

The reverse proxy is the part that's exposed. CrowdSec watches the logs for intrusion attempts like fail2ban would.

[–] synestine@sh.itjust.works 2 points 2 months ago (4 children)

If you're worried about it, make sure to not use a default path. Then legit clients are fine but these theoretical attackers get stymied.

[–] synestine@sh.itjust.works 2 points 2 months ago

Yes it is completely normal. The Internet is almost but not quite as bad as security wonks claim. Especially since you're not on the default port, most scanners don't have the programming to attempt on Home assistant. Most of them are built for more common exploits.

If you look at your proxy logs, you'll see attempts at various random paths, but those should all be 404 or 403s.

[–] synestine@sh.itjust.works 25 points 3 months ago (1 children)

SSHFS uses SFTP which is built into SSH, so no server to install. Its not as fast as NFS, but requires no setup. For something small like a home lab, that is a big advantage.

[–] synestine@sh.itjust.works 1 points 3 months ago (2 children)

Dozens? Name three, and be sure to include number of aps in each ecosystem.

I'm sure there are dozens of Chinese smart watches, but most that I've seen are white-labels and sorely missing an ecosystem.

[–] synestine@sh.itjust.works 7 points 3 months ago (5 children)

Methinks you underestimate the complexity.

And all the other watch makers I've looked at are not doing, or even considering, what Pebble did.

[–] synestine@sh.itjust.works 7 points 3 months ago

Because good software is hard. The PebbleOS is a gem, and no, no one could in 9 years.

[–] synestine@sh.itjust.works 23 points 3 months ago

Google dumped the Pebble OS code on GitHub when this whole "rePebble" thing (not Rebble) started. Now there's a new phone app coming out soon (or out now, depending on your platform and abilities) that handles old and new Pebbles and modern phone platforms.

None of this is from Google.

[–] synestine@sh.itjust.works 7 points 3 months ago (1 children)

True, but there's not much one can do about others' stubbornness. I've been using cheap Android boxes with Kodi or the JF client installed. They make sense to my non-techie family. Dedicated boxes are better (something that can run CoreELEC, OpenELEC) but those are harder to find.

[–] synestine@sh.itjust.works 21 points 3 months ago (1 children)

Because that basically requires transcoding for modern codecs. H265? Transcode. Subtitles? Transcode. The JF client on the same hardware can usually direct play.

 

Until recently I had been using an EZVIZ DB1C doorbell. I researched before I got it, and it worked immediately when bought. Then the company started playing dirty pool. Over the next two firmware updates (WIth nothing in the notes beyond "bugfixes and imrprovements") they stripped out the ability to use a local RTSP stream then they stripped out the ability to use their Windows-only software to even re-enable any functionality. Then they jerked me around for over a month before they finally copped to what the company had done.

And of course there's no way back to a working firmware.

I know people have mentioned Reolink and Amcrest before, but those models are no longer available.

Is there anything in the way of wired, mechanical-bell compatible doorbell cameras that work with HomeAssistant?

I'm so sick of companies that sell you one thing, then strip out the functionality that made it useful, shoving you into their cloud/app shit or leaving you stranded on whatever firmware the thing came with.

GRR

view more: next ›