0xC0ncord

Previous discussion: https://news.ycombinator.com/item?id=32494497

I was greatly disappointed too when I found out about transmission-cli's deprecation, but I have since found and replaced all uses of it with stig[1] which, for me, does the same thing and more.

[1] https://github.com/rndusr/stig

Jellyfin has an official app for Roku but I am not sure about other platforms like webOS.

My girlfriend and I just did this and had a lot of fun!

There were a lot of times where I thought I figured a word out but ended up having to go through about 5 or 6 really good guesses before landing on the right one. Sometimes little word games like these really can test my vocabulary.

I found that when I started doing this I would just get even more calls, just not the same ones.

I presume this is because these spammers just keep selling other spammers valid phone numbers to add to their own lists.

Previous discussion (2018): https://news.ycombinator.com/item?id=17392995

This reminds me of a racing game series I used to play when I was younger called TrackMania. The racing gameplay dynamic was simply about getting the best time. Getting gold medals on all of the single player tracks is just the beginning. Once you start heading online and looking at the leaderboards you realize just how competitive the scene is in this series of games. This video[1] for example documents some of the crazy lengths that the most competitive players will go to get to the top of the ranks.

[1] https://www.youtube.com/watch?v=ODo_obCblXo

As someone who gets spam from various Gmail accounts on the daily I'm not inclined to believe it's that difficult.

The problem is that the microsoft-edge:// protocol is used throughout the Windows UI and menus and will always open in Edge regardless of the user's preferences. If you click on a link in say, the Settings UI, it will ignore your default browser preference and open in Edge with no way to change it.

From my understanding the other goal that is often overlooked is that limiting resources on unmetered workloads prevents those processes from depriving others (and the host) of resources. It's mostly just a catch-all situation, but I would expect there to be ways to fine-tune this behavior.

I feel like the biggest problem I've had with smart home technology is that there is no out of the box standard for controlling or having access to all of your devices. Almost every device seems to require interacting with it with the vendor's own app or other utility, and so I've needed to install a multitude of at least 3 apps just to control the lights. So not only are vendors trying to compete with their smart devices, but additionally with the apps they've created to even use them, probably to see how much more money they can squeeze out of selling your personal information.

Thankfully, there's Home Assistant[1], which is an amazing project that aims to bridge connectivity and control between all of these devices into a single centralized environment. Pair that up with Tasmota[2]-compatible devices and you can have a smart home that can be completely disconnected from the cloud and in your control.

[1] https://www.home-assistant.io/

[2] https://tasmota.github.io/docs/

Looks very nice! I will have to try it. Do you have plans to announce it to matrix.org's This Week In Matrix (TWIM) updates? If you're looking for more testing and feedback I'm sure you'll get some from the visibility there.

I generally solve this problem by having a module specifically containing the abstract base classes of each of the classes I will be working with that implements either no or bare minimum functionality for these objects. That way, any other module can import this module and have visibility of every other class I will be working with.

From what I can tell, Clang+LLVM is where all the innovation is happening. Clang in particular has seen many new security features for a modern compiler like the implementation of SafeStack[1] and Control Flow Integrity[2]. Even just on the functional side of things Clang has thinLTO[3], which makes building link-time optimized binaries easier on lower-end systems. None of these features are currently planned for GCC.

[1] https://clang.llvm.org/docs/SafeStack.html

[2] https://clang.llvm.org/docs/ControlFlowIntegrity.html

[3] https://clang.llvm.org/docs/ThinLTO.html

There are public and community-curated banlists than any homeserver admin can subscribe to. Probably not exactly a "spamhaus" equivalent, but it's pretty close.

Most bugs that get backported to stable kernels only get backported if they are serious enough or have a CVE assigned to them. Many bugs with potential security implications go unfixed because of this.

I don't think they have any reason to. If a customer wants to share their connection, they're still paying for the bandwidth. If they share it with enough people that they exceed any data caps, that's more money they will need to be paying. Sounds like a win for the ISP to me.

SELinux can and does do exactly this, depending on the configuration. What you'll most often see is that applications covered will have rules that allow it to access a subset of the user's home content (xdg cache, data, etc.) that allow that application to function, and SELinux will use UBAC rules to ensure that user A's instance of that application cannot access the data of user B's.

Profiles are indeed tricky though, and generally something I would consider more easily implemented as just logging in as a different user.

I can't speak much about AppArmor since I'm not too familiar with it.

You pretty much can't, because once memory has been written to at runtime it is assumed to be untrusted. JIT in and of itself is a W^X violation, so the only real solution is to not use it when security over performance is preferred.

I want to add that there is an ongoing effort to stabilize SELinux on OpenWRT[1] as well. Security on OpenWRT has been shaping up very nicely for a while now.

[1] https://aparcar.org/running-openwrt-with-selinux/

While I don't agree with every way that the case against Snowden was handled, I don't agree with the thought that things would be much different if the two sides were flipped. The general attitude towards Snowden is too black and white in my opinion. Traitors can be heroes, too. They are not mutually exclusive.

Even if that scenario is true, there is zero evidence to corroborate it, nor has there been any concluded official investigation into the matter. I don't think it's fair for Twitter to execute that portion of their policy based on assumption alone.

Reading the article, nothing in the repair shop owner's interview strikes me as incorrect or inconsistent. It seems to me that the man is just inarticulate and has never been put on the stage by a reporter before, especially a stage large enough to put a presidential candidate's campaign at risk.

You would have to block entire wordlists to combat subdomains like that. It would make more sense to whitelist subdomains instead, but it would require much more effort in order to determine what subdomains are required for the website to function. Additionally, if the site in question ever decided to change anything around, someone would have to catch the breaking change and have it corrected on the whitelists for the site to function again.