An nft is more like a receipt. It says you bought it, there’s reference to the item on the receipt, but the item you bought was actually just the floor display and it remains the floor display whether you purchased it or not. You effectively paid for the receipt of buying the floor display, not the floor display itself.
By default they use protocols specific to outlook/exchange/365. Sometimes referred to as activesync or outlook anywhere, which encapsulates their own protocol (I think it’s MAPI?) Over an HTTPS tunnel.
These technologies have had a lot of names.
In the past few years 365 also requires TLS 1.2 at least, and oauth. Oauth is when a mini browser window pops up for your 2FA info, like ms authenticator or duo or whatever your organisation is using. The nice thing about oauth is that it’s compatible with many identity providers, not just MS. The bad thing is that it’s fairly unique that outlook supports it. I don’t know of any other email clients that support it…
Even if you can get passed the login, most mail clients don’t support MAPI over HTTPS the way that outlook does. There are some android/iPhone apps that support it, but that’s not universal either; the naming can fluctuate between the options I’ve mentioned earlier.
The only good way to get this done (speaking as someone who has had to help someone get it working), the organizational email admin needs to enable either pop or (preferably) IMAP, and assign an application password to it. This password is long and usually a string of random characters. It gets saved to your email client software and it is used nowhere else. It’s been a long time since I’ve done this and I’m not sure it’s still supported like this.
I hope that gives you more information as to the challenge ahead of you.
Easy, since it’s open source, anyone could, if they’re inclined, edit the code to do something just differently enough to cause a problem, or unlock features they’re not supposed to have access to, or spoof something that they shouldn’t be able to spoof.
This was a big argument against Windows getting a full Unix style socket in Windows 10, I believe. MS did it anyway and basically nothing changed. The blunt realty is that if an attacker is so inclined, they will find a way. Whether anyone wants them to or not. In the case of Unix style sockets, simply pushing the attack onto a Linux VM running on the windows system is usually enough, at most, moving the attack to a Linux or Unix system is also pretty easy but requires additional hardware (even a raspberry Pi) to complete.
As simply as I can, there’s enough software defined radios out there that you can hack to accurately spoof a genuine (closed source) device with enough effort, that this argument dies on the table to anyone with the technical knowledge to know what it actually means. It’s the same argument as outlawing guns. If you outlaw guns, only outlaws will have guns; which is also total horseshit in it’s own right, but makes a point. They’re making it hard for people (the non-malicious public) to get access to services in the way they want on the basis that it would “make it easier” for hackers to do the illegal. While it may be true that hackers will be able to do some things easier, by not requiring specialized hardware to do whatever malicious thing they want, they’re effectively punishing thousands or hundreds of thousands of people who are not malicious and want open source by prohibiting it, just to make the small number of hackers work harder to do things.
Fact is, if they allow it, they need to invest time and effort into implementing safeguards to ensure that any abuse is caught and stopped. They don’t want to put in that effort. The idiotic thing is that they need to put in those safeguards anyways because other tools exist that can still attack in the same manner. So they’ve saved themselves nothing in the prohibition, made the job of malicious hackers “harder”, and punished a large percentage of their client base for no good reason.
If everything that might cause disruption was forbidden, we wouldn’t be allowed to do anything. Even normal user traffic in high enough quantities can cause services to go down. No malicious intent involved.
If such a thing exists (DIY paper printers), I would like to know more, because the level of frustration I have with all the major printer mfrs I’ve used, is too damn high.
Bonus points if it’s a laser printer, extra bonus points if the components for the printer can be 3D printed (with obvious exceptions).
I just want a good, wired, network printer for everyday crap that I can use once in a blue moon for stupid documents that someone wants me to print, sign, scan and send back to them because they haven’t figured out how to do e-signatures yet… And the odd extra thing I need to print. Every time I print it seems like I need to reinstall the printer or update something to make it work. I buy laser printers so the ink doesn’t dry out before I can use it. The whole thing is so damned frustrating. Also, bluntly, unless you’re doing photo work, never buy an inkjet. They’re cheap, and there’s a reason they’re cheap. Inkjet has better color representation, so photo printers should probably be inkjet, for everything else, do yourself a favor and buy a laser printer. Toner lasts much, much, longer.
I believe you’re referring to “the algorithm”. Which is usually just code for “a bunch of people that view and engage with the content you have viewed/engaged with also viewed/engaged with this”
I understand what they’re doing and I understand why, but sometimes, I just want a reverse chronological feed of my friends activities, so I can keep up to date with their most recent life events.
As someone with a 3D printer, thank you for your service.
I don’t have issues with the things you’ve mentioned, but because less knowledgeable people have gotten into 3D printing, the market for such products is thriving, so I get to enjoy it because people who know less about it are doing it because of the efforts of people like you.
I’m a network guy, so everything in my labs use SNMP because it works with everything. Things that don’t support SNMP are usually replaced and yeeted off the nearest bridge.
For that I use librenms. Simple, open source, and I find it easy to use, for the most part. I put it on a different system than what I’m monitoring because if it shares fate with everything else, it’s not going to be very useful or give me any alerts if there’s a full outage of my main homelab cluster.
Of course, access from the internet to it, is forbidden, and any SNMP is filtered by my firewall. Nothing really gets through for it, so I’m unconcerned about it becoming a target. For the rest of my systems security is mostly reliant on a small set of reverse proxies and firewall rules to keep everything secure.
I use a couple of VPN systems to access the servers remotely, all running on odd ports (if they need port forwards at all). I have multiple to provide redundancy to my remote access, so if one VPN isn’t working due to a crash or something, I have others that should get me some measure of access.