As someone who has read these terms in passing but is unfamiliar with them: What the fuck?
azl
Just some advice for others who want to avoid the same experience: The larger the roads, the less interesting the roadsides. Interstate highways were made for getting from big city to big city and are rarely scenic or memorable.
But IT is not marketing, which is the subject of this discussion...
Calling Meta "Facebook" tells me all I need to know about the engagement that random opinion blog will attract.
Logged in... was nice.
Yes, this is totally possible and I did it for a couple of years with OPNsense. I actually had an OPNsense box and a pfSense box both on Hyper-V. I could toggle between them easily and it worked well. There are CPU considerations which depend on your traffic load. Security is not an issue as long as you have the network interface assignments correct and have not accidentally attached the WAN interface to any other guest VM's.
Unfortunately, when I upgraded to 1Gb/s (now 2Gb/s) on the WAN, the VM could not keep up. No amount of tuning in the Hyper-V host (dual Xeon 3GHz) or the VM could resolve the poor throughput. I assume it came down to the 10Gb NICs and their drivers, or the Hyper-V virtual switch subsystem. Depending on what hardware offload and other tuning settings I tried, I would get perfect throughput one way, but terrible performance in the other direction, or some compromise in between on either side. There was a lot of iperf3 testing involved. I don't blame OPNsense/pfSense -- these issues impacted any 10Gb links attached to VM's.
Ultimately, I eliminated the virtual router and ended up where you are, with a baremetal pfSense on a much less powerful device (Intel Atom-based). I'm still not happy with it -- getting a full 2Gb/s up and down is hard.
Aside from performance, one of the other reasons for moving the firewall back to a dedicated unit was that I wanted to isolate it from any issues that might impact the host. The firewall is such a core component of my network, and I didn't like it going offline when I needed to reboot the server.
The service described in the article has nothing to do with courts, regulation, enforcement, or the legal system. It is used by city maintenance to identify elements of public property in need of attention, such as abandoned vehicles and potholes in the asphalt. It is being adapted to identify accumulations of trash and other indicators of illegal camping which are important to maintainers of public spaces.
This is part of the problem with using terms like "homeless" to describe the occupants of an illegal campsite. There are numerous reasons one may choose to camp in a public space.
- Some are truly struggling to regain their financial footing and either the assistance programs are not helpful or they are unable to utilize them.
- Some are sick which causes them to be unable to participate functionally in society, and they have "fallen through the cracks" of services designed to support them.
- Some reject housing in favor of a lifestyle that demands less effort or accountability -- possibly in service of addiction, which ties into #2 above.
All members of society should have access to shelter (or a safe campsite, if that is our preference) and our basic needs met. As members of society, we shall follow laws which describe, for very good reasons, why we cannot simply erect a camping tent in a city park.
The problem with ignoring campsites is plummeting hygiene and safety. Waste is generated by day to day life and must be collected or eliminated. As campers accumulate and abandon the implements of a semi-permanent hovel: furniture, bedding, tarps, etc., the surrounding area transforms into a dumping site.
The technology described in the article already identifies potholes and illegal parking. It does not identify people or their race. Surely it could evolve into something with more potential for abuse, but in its current capacity, it is quite a neutral tool.
We have collected a lot of data on the "ignore and do nothing" solution -- the outcome is a scientific certainty. Using tools like this to measure progress (for better or worse) seems like something that would help generate support for other solutions, such as extensive expansion of low-cost/no-cost housing services.
There are some SRV and other records which you add for the AD-provided services (kerberos, gc, ldap). This allows your Windows clients to find the domain controllers for authentication via your non-Windows DNS. I think I might have followed a Microsoft or other article when doing the initial setup, but once getting those items in place I haven't had many issues.
I do. 4 or 5 users and several computers plus virtual server members. I still use Linux for DNS which works surprisingly well after the initial setup.
I did it half for practice and half for fun, but having the authentication backend makes it good enough to keep around.
Nice. Might come in handy for others considering how common that USR modem design was. I would have liked to see a power-on shot to see how well the PETG lights worked.
The ads also show users interacting with their physical and virtual environments smoothly, without difficulty seeing around them or spatial positioning glitches, which does not at all describe the current state of Meta OS. I've been a Oculus/Meta user for 10 years and the UI is definitely not an Apple experience. (p.s. I hate Apple and love Quest 3)
Wearing a Quest while working on a car sounds like a great way to lose a finger, or destroy the part I'm trying to install/repair. I can feel the frustration bubbling up when I imagine trying to assemble furniture while wearing a headset clamped to my face with a super tight headstrap. Man I'm so pissed now.