greyfox

Yeah it is fairly trivial to check. I called it a SPF record but technically in DNS it is a TXT record. TXT records are just a generic record type used for many different uses.

Here are a few common DNS commands to lookup TXT records:

host -t TXT domainname

nslookup -type=TXT domainname

dig -t TXT domainname

For your barracudanetworks example here we get a few TXT records back but we can see spf.protection.outlook.com is in their list and therefore allowed to send of behalf of the barracudanetworks.com domain. All of the other entries are allowed to send of their behalf too so your email isn't guaranteed to go through Microsoft.

Judging by the Salesforce/Zendesk stuff they probably have ticketing/customer management systems, which means it might be possible to contact them without going through Microsoft's email servers. Notifications from those systems would probably be sending email directly to you instead of routing it through Office365.

I suppose that is a concern, but I think those are cloud IPs they move around occasionally and wouldn't want to make every user update their TXT records.

So for this use case I am pretty sure they would always be DNS names if the admins are following Microsoft's instructions.

It looks like they have you set your txt record to spf.protection.outlook.com which resolves to a txt record with a bunch of their IPs. So if you really wanted to make sure there weren't installs with IPs in their list you can use that txt record to get Microsoft's IP ranges and search for those as well.

You should check for SPF records as well. If they have SPF records (and Microsoft walks them through setting up those records), they would need one for every mail server sending on their behalf.

So it appears that in your case here their MX records pointed at their own MTA that then routes at least some of that email to Microsoft. If they are using SPF records to prevent others from spoofing their email addresses, and if they are allowing Microsoft to send on their behalf there would have to be SPF records with Microsoft's domains in them.

Still no sure thing but a little more checking that you can do.

Your $1 has absolutely changed in value by 10pm. What do you think inflation is? It might not be enough change for the store to bother changing prices but the value changes constantly.

Watch the foreign exchange markets, your $1 is changing in value compared to every other currency constantly.

The only difference between fiat and crypto is that changing the prices in the store is difficult, and the volume of trade is high enough to reduce volatility in the value of your $. There are plenty of cases of hyperinflation in history where stores have to change prices on a daily basis, meaning that fiat is not immune to volatility.

To prevent that volatility we just have things like the federal reserve, debt limits, federal regulations, etc that are designed to keep you the investor (money holders) happy with keeping that money in dollars instead of assets. The value is somewhat stable as long as the government is solvent.

Crypto doesn't have those external controls, instead it has internal controls, i.e. mining difficulty. Which from a user perspective is better because it can't be printed at will by the government.

Long story short fiat is no different than crypto, there is no real tangible value, so value is what people think it is. Unfortunately crypto's value is driven more by speculative "investors" than by actual trade demand which means it is more volatile. If enough of the world changed to crypto it would just as stable as your $.

Not saying crypto is a good thing just saying that it isn't any better or worse. It needs daily usage for real trade by a large portion of the population to reduce the volatility, instead of just being used to gamble against the dollar.

Our governments would likely never let that happen though, they can't give up their ability to print money. It's far easier to keep getting elected when you print the cash to operate the government, than it is to raise taxes to pay for the things they need.

The absolutely worthless meme coin scams/forks/etc are just scammers and gamblers trying to rip each other off. They just make any sort of useful critical mass of trade less and less plausible because it gives all crypto a bad name. Not that Bitcoin/Ethereum started out any different but now that enough people are using them splitting your user base is just self defeating

When you saw that 20v on the board I assume that was right next to the charge port? There are often fuses that should be very close to that connector that you can check for continuity on. Usually marked with zeros because they act like a zero ohm resistor.

Even if the fuse is blown that might just be a sign that something further down the line failed but it would be an easy thing to check at least.

I am not exactly an expert at this but it could just be from heat. Do you have a multimeter to check if current can pass through it still?

Either way it seems like this shouldn't be affecting the laptop when plugged in because it is so close to the battery connector and it looks like the traces are related to the battery connector.

Do you get anything at all (battery/power LEDs) trying to run off of the battery? Is it possible that the charge port failed and the battery is just dead now? Maybe check the battery voltage to see how far drained it is.

I just did a playthrough recently and I think it holds up pretty well. A lot of wasted time on little cutscenes like opening Atla/boxes, and switching characters that gets quite annoying, but gameplay was fine.

One or two bosses that are difficult but a little leveling up, or wiki hints on how to cheese them, and they are a piece of cake. Once you hit the ship dungeon and have easier access to backrooms (since you can buy the fish to enter them) you can grind for gemstones and you end up being able to one hit almost everything from there on out.

Grinding gets a bit boring after a while, I'll admit I enabled some fish point cheats in my emulator after I had one character with a maxed out weapon. Clear that I could easily do it myself but wasn't going to waste that time to upgrade the other weapons I wanted leveled up.

Probably a terrible idea but have you considered a private Lemmy instance? At the end of the day Lemmy/PieFed/Reddit are just forums with conversation threads and upvotes.

Lemmy is probably way more of a resource hog than the other various php options but from a usability standpoint if you have a favorite Lemmy mobile app it would work for your private instance as well.

There appears to be a private instance mode that disables federation.

Well if you rephrase it for a normal car it doesn't sound so absurd. "If your hood won't latch the car won't let you drive at highway speeds?"

A failed latch on a front compartment can be very dangerous because it catches the wind if it opens suddenly at 60+mph. At best you are blinded, or it gets torn off to go flying into a car behind you.

As such, highway speeds should be restricted if the latch is malfunctioning. The real problem here is that Tesla doesn't like dealers because they want that middleman money for themselves, so you often have to drive quite the distance to get it repaired. If this were a vehicle from any of the other major manufacturers most people are probably only a few miles from their nearest dealer.

Normal cars have two hood latches. Your primary latch (that you open with the hood pull in the car) and a secondary safety latch (when you reach under the hood to open it fully) so this problem is an extremely uncommon problem for a normal car.

But since this is a frunk it gets opened a lot more for storage and users would probably not be very happy about having to deal with the secondary latch on a regular basis. So they have motorized those latches for ease of use, and motorizing them adds a lot more points of failure.

Named volumes are often the default because there is no chance of them conflicting with other services or containers running on the system.

Say you deployed two different docker compose apps each with their own MariaDB. With named volumes there is zero chance of those conflicting (at least from the filesystem perspective).

This also better facilitates easier cleanup. The apps documentation can say "docker compose down -v", and they are done. Instead of listing a bunch of directories that need to be cleaned up.

Those lingering directories can also cause problems for users that might have wanted a clean start when their app is broken, but with a bind mount that broken database schema won't have been deleted for them when they start up the services again.

All that said, I very much agree that when you go to deploy a docker service you should consider changing the named volumes to standard bind mounts for a couple of reasons.

• When running production applications I don't want the volumes to be able to be cleaned up so easily. A little extra protection from accidental deletion is handy.

• The default location for named volumes doesn't work well with any advanced partitioning strategies. i.e. if you want your database volume on a different partition than your static web content.

• Old reason and maybe more user preference at this point but back before the docker overlay2 storage driver had matured we used the btrfs driver instead and occasionally Docker would break and we would need to wipe out the entire /var/lib/docker btrfs filesystem, so I just personally want to keep anything persistent out of that directory.

So basically application writers should use named volumes to simplify the documentation/installation/maintenance/cleanup of their applications.

Systems administrators running those applications should know and understand the docker compose well enough to change those settings to make them production ready for their environment. Reading through it and making those changes ends up being part of learning how the containers are structured in the first place.

They are from the Lemmynsfw instance. Probably automatically applied to any post coming from that instance.

FYI the latest SteamOS release (just a couple of days ago) added an option to only charge to 80%.