gavanm
https://www.mossy.earth/methodologies/business-ethos
Also in their FAQs:
Is Mossy Earth a charity? We are a social enterprise incorporated as a private limited company in the United Kingdom with a for profit structure. In other words, we are a business and the membership is a payment for a service we provide, not a donation. You pay us to rewild nature, and we do our best to make sure that your money has the biggest possible impact.
Though if that were the case, I'd probably guess there should be more areas at the other site locations around northern Australia - so that might invalidate my guess.
https://en.wikipedia.org/wiki/Jindalee_Operational_Radar_Net...
https://www.google.com/maps/place/28%C2%B019'02.6%22S+122%C2...
https://www.google.com/maps/place/28%C2%B019'36.3%22S+122%C2...
https://learn.microsoft.com/en-us/sql/database-engine/config...
I haven’t had the opportunity to use it in production yet - but it’s worth keeping in mind.
I’ve helped fix poor attempts of “table as queue” before - once you get the locking hints right, polling performs well enough for small volumes - from your list above, the only thing I can’t recall there being in sql server is a LISTEN - but I’m not really an expert on it.
Given the controversy over the Activision acquisition, acquiring one of the major engine platforms, having a major game studio, and already owning the XBox platform might make for great end to end strategic alignment / platform control - but I think it would also be a big regulatory/political fight to get done.
This follows up to this discussion and report last year:
Now that it is closed, and there is no smoke - they can see not just the towers, they now see a long way behind them as well.
There's a small section marked on the back that is specifically for it.
I guess if you move multiple times within the expiry period, you can pull the old sticker off and replace it.
https://www.vanillabeankings.com/blogs/recipes/vanilla-bean-...
I might even have read about it originally from here.
Of course that only helps if they're recovered / identified quickly - once any significant amount of co-mingling happens then it's probably too much effort to track down the origin.
By having a proxy/repeater/site server, you are reducing the amount of WAN traffic you need to send.
The developer uses MFA (TOTP, Push Notification, Yubikey etc) into a virtual desktop inside the organisation (Citrix, VMWare Horizon, etc).
From there, the developer can SSH / whatever into their development environment - which is hosted "inside" the corporate network, or their cloud provider, via internal links.
All code, and dev boxes live "inside" the corporate network, and only keypresses, mouse movement, and screen diffs are sent back and forth.
Most remote access packages can prevent clipboard, USB device, file transfer etc.
If you need a password manager for work purposes, then it lives on the corporate managed network - not your remote laptop/desktop - and to be really paranoid - you only ever "copy/paste" those passwords - you don't type them in.
If you really want to lock it down further, give the remote workers dedicated corporate equipment that they only use to access the remote desktops, so you can prevent some things like screen capturing, and really lock down the software to prevent things like keylogging software/malware.
You also should have the entire development environment segregated from the "business" corporate network as well.
It's only really an issue if you want to have offline developers - in which case I don't have any thoughts ready to hand - (but would expect it to be a very locked down machine, possibly with an even more locked down VM inside it).
As someone who regularly uses multiple layers of Virtual Desktop -> Virtual Desktop -> Remote Desktop, provided the network can handle it (on both your local network, and the corporate network), it works surprisingly well.
I’m not sure about the impact of shipping though.
See: https://www.autoblog.com/2021/03/09/toyota-how-it-avoided-se...
Mostly used a DEC Alpha as a "visible" competitor to our major server provider at the time (Compaq) to try and manage the prices they were charging (at least until Compaq bought Digital, and then eventually bought by/merged with HP).
One interesting thing was that we had a faulty RAM chip that we only discovered due to a bug in website publishing to IIS causing a big memory leak which crashed the server. Once the the chip was replaced, we still had the underlying leak - but at least the server didn't crash any more.
I'm speculating that areas with undersea cables are often marked as "no anchor" zones due to the risk of damage (in areas where such practices are followed).
So the drop in damage from anchors and extended motor boat presence might eventually outweigh the initial damage from laying the cable.
It would be like an internet company trademarking Browser, or a car company called Engine.
I think the nearest car analogy is ODBII ports and data access - ANT+ is a wireless communication protocol, mostly for reading statistics (I think it can also be used for issuing commands).
Hammerhead had a license to access the privately configured Shimano data - and then they were purchased by SRAM (who are Shimano Bike division's main competitor).
As a result, Shimano is (for now) limiting a competitors ability to see the data produced by Shimano components.
This feels very petty to me - most of the data is essentially going to be "which gear is the front/rear in", and "what shifting pattern do you want to use" - though it might also extend to preventing future interoperability (like preventing competing wireless shifting levers triggering the other manufacturers components) - which would be a loss for consumers.
It gets a bit tiring towards the later books, but I recall the earlier ones were quite good.
https://www.goodreads.com/author/show/8979.Patrick_Robinson
There's always the classic Hunt for Red October.
https://en.wikipedia.org/wiki/Countdown_(video_game)
You wake up with amnesia locked in a room in an asylum, and have to figure it out from there.
I don't know the official meaning - but I'm fairly sure it's for the abbreviation "Also Known As" - "AKA".
1 - Hacker News - If there's an interesting article linked, then I'll consider adding the site to my feed (using feedbin since the great Google Reader apocalypse).
2 - Blog referrals - Sometimes existing feed items will link to other articles sites (sourced from, similar problem, etc) and I'll sometimes add those sites.
3 - Search Results / Organic - If I'm investigating a particular problem/issue/topic and find a good blog, then I'll add it to my feed.
4 - Topic Specific Aggregators - in some cases there are people that produce topic specific post summaries (such as the .Net Morning Brew https://blog.cwa.me.uk/ or Michael Tsai https://mjtsai.com/blog/ ) that link articles - again, if the articles are good, or I notice I've visited the site before, I'll sometimes add it to my feed list.
Just checking my OPML, I have around 600 sites (more than a few are likely no longer posting) in my current reader - accumulated over the last 20 years or so - that I've found specifically interesting (mostly professionally, and a few hobby based ones as well). I still get around 60 or so new items per day, and probably skim 20, read 10 in detail, and mark the rest as read.
Like the linked article discusses here, it's no longer possible to easily get a feed from major social media sources - which limits the usefulness of RSS from a purely social perspective (but I've never tried to use it that way) - but if you treat it as a personally curated source of sporadic content, then it's great. In many respects Moderate post volume (quality over quantity) is something I find more useful in what I choose.
On the aggregator front, I try to avoid anything that's too noisy (low signal to noise) - and I definitely minimise subscribing to news sites as the volume is just too high (I tried rss subscribing to The Verge when it was new, but there were too many articles I don't read). For example, i wouldn't use a RSS feed of Hacker News because I probably only look at 1 in 10 articles on it.
RSS is still heavily used for information I find really professionally useful (IT) - but I don't know about other industries.
Possibly the only bugbear I have around the RSS ecosystem these days is that some authors don't include the full content in the RSS feed - which makes offline and mobile consumption more difficult / annoying - I suspect that in some cases it's a result of default choices - and in others it's a deliberate decision as a trade off against improved analysis a site gets from a browser hit.
It helps avoid some scripting / token / API overhead - but I'm wondering what the trade off is in terms of initial setup time.
One general concern I have is around Data (state) consistency of the data after DML operations (insert / update). If the data represents the state of a resource - how do you know if there's a pending operation on it as a result of an earlier Update operation? How is idempotency handled? How are conflicting concurrent state changes handled (one user forces a restart, another initiates a shutdown)? What happens if a change applied to multiple records/resources only successfully applies on some of the resources?
This isn't specific to just this approach though - it's going to apply to any kind of cloud / resource management platform. I'm not sure how they tend to handle it - but a basic single record per resource has limitations around it that mean more work is needed. Maybe you end up with change history records?