@scottalanmiller said in Notorious Short-seller labels Ubiquiti Networks $UBNT as FRAUD:

They sound like Donald Trump writing Facebook ad copy.

Thanks a lot. Now my monitor has coffee all over it from laughing mid sip. Lol

@jaredbusch said in PiHole for Friends and Family:

I don't get the point of this. I mean it is a cool concept, but it is to much work.

What's not to get? This is being used to limit who can access the cloud hosted Pi-hole server to only those whose DDNS domain (and ergo IP address) is listed. It makes the server DNS access non-public for those with dynamic IPs who are setup with a DDNS domain.

Do you have another recommendation for limiting server access for DNS services to a limited IP that is dynamically assigned by the ISP?

I agree it's been a lot of work for Romo who's kindly provided us with the script but in the absence of a better solution, this is extremely useful.

@guyinpv That's a pretty tall order indeed.

I've been poking around with Ryver. It's a hosted app that is free to use. You create your team and login and it combines your standard chat features (like the standard stream of content you'd see looking at Facebook Messenger - no context but threaded which is useful and not context sensitive). They also have "posts" which would be like posts here on ML that are context based and messages inside the posts as replies are kept related to the context at hand.

You can create sub teams where you remain the admin and invite others to join those private teams. In these, your communication on both chats and posts is limited to those with access.

If you want a global public forum, then anyone with login can view and participate in those chats and posts.

This allows you to create private teams per client and then use the chat + post functions to keep context sensitive information together and general chat threaded.

They also integrate with a number of other apps which may help close the gap for you.

This only addresses some of the features you're looking for so I'm interested to see what others will recommend.

https://ryver.com/ryver-vs-slack/
https://ryver.com/why-ryver/
https://ryver.com/feature-tutorials/

@jaredbusch Oh, and good luck. Truly, I mean this. If you or anyone here is affected by this breach. This is not data that I would be comfortable having out in the open. No matter what lame "identity protection" Equifax may be offering as reparations.

@jaredbusch

@jaredbusch said in Equifax Has 143 Million Americans Data Compromised:

@nashbrydges said in Equifax Has 143 Million Americans Data Compromised:

@jaredbusch That's totally relevant. Lmao. Agreed they suspect the breach took place between May and July when it was discovered, once it is discovered, the responsible thing to do is let the affected individuals know immediately. Not wait 6 more weeks. That's just stupid and irresponsible.

Not really. Because it also takes time to first, plug the hole, then figure out what was actually taken.

Now, I am not trying to defend Equifax because they have a horrid track record in the first place. But your assertion that it should be immediately announced it assinine.

It is this type of mentality that is wrong with so much of the public. Facts are important. Not your emotional reaction, that will very likely be proven wrong.

It's interesting you read this as an emotional reaction since I'm unaffected by this breach. I have no skin in this game. But what I am talking about is corporate responsibility. Something that I would think both you and I may understand better as SMBs.

Everyone recognizes when the wagons are being circled and no corporate entity would suffer this type of breach without their first reaction being one to cover their asses. I'm much closer to my clients and their needs. I understand the reputational impact this could have on my business. Yeah, they've taken a hit with their stock but my guess is, the full scope of the truth may never be discovered even with the class action lawsuits already being filed. Those are premature in my mind, but a responsible entity would not have waited this long, especially given the sensitivity of the data acquired in the breach.

@dustinb3403 said in Equifax Has 143 Million Americans Data Compromised:

In 2014.. .

There were about 125.9 million adults in the US

So literally everybody is f***ed at this point. Time to go to creditors and tell them to refuse to provide credit based on the methods they've been using.

Yep. Freeze your credit profile.
https://krebsonsecurity.com/2015/06/how-i-learned-to-stop-worrying-and-embrace-the-security-freeze/

@jaredbusch That's totally relevant. Lmao. Agreed they suspect the breach took place between May and July when it was discovered, once it is discovered, the responsible thing to do is let the affected individuals know immediately. Not wait 6 more weeks. That's just stupid and irresponsible.

You have to ask yourself why they waited 6 weeks before disclosing this breach. I get that they want to investigate the breach and have as many answers as possible but the flip side is that, this means that for 6 weeks, people's data has been out there. That's 6 weeks of unknown exposure. That seems irresponsible.

@aaronstuder I have a separate instance running Nginx but regardless, why would you not recommend on same server? I see no reason why that would be a problem.

@aaronstuder That's the web server installed by default with the Pi-hole script for the admin page. Nginx would serve as the proxy.