hutch120

Oh yeah, great idea. Done!

Fun game! Can I suggest adding a licence file to Github so people know what they can do with the repo.

I remember looking at that fork when the whole licencing thing went down a couple of years ago, but it was unclear how much, if any support it would have. Looks like the project is doing ok.

Like many others no doubt, I invested heavily into the mapbox-gl-js library (pre 2.0). I was able to build amazing value on top of that library including a routing voice navigation app for an aged care facility that is used to this day 24/7/365. It was a very sad day when they changed their licencing model to lock in vendors and I had to walk away from that investment of my time and effort. Luckily I had also worked and contributed to OpenLayers and Leaflet, so with significant effort was able to move my clients to those platforms.

I guess we now have some more insight into why this occurred.

> "In order to use most Services, you must register for or authenticate into a Mapbox account. When you use our application program interfaces (APIs), including our SDK Registry/Downloads API, each request to an API must include one of your account's unique API keys."

We should ask the long term question, what if QGIS and other FLOSS products had broad support and significant resources flowing into them that ESRI has?

The way I think about it, often the same people, certainly people with the similar skillsets are working on all these products, most of them just follow the money.

I think one big missing piece of the puzzle for governments to assess these products is a governance and risk model associated with these products. But software engineers generally don't give a crap about governance, so we need more people who do care about that to invest in OSS. I'm seeing some movement on this like the Github Sponsors initiative.

Stay away from ESRI (ess-ray) - I should get that printed on a t-shirt.

ESRI centralise power, lock you into their technology, and IMHO a digital twin should be doing the opposite. Don't believe the sales BS about ESRI having "free" software, read the fine print, ArcGIS AINT FREE.

IMHO a Digital Twin should be something for the people, by the people! So please stop paying proprietary systems like ESRI and incentivising them to stifle innovation and increases barriers to entry.

If you want to see local jobs, growth and innovation then invest in OpenSource software like OSM (Open Street Map) and QGIS and other Open GIS products.

> "Who doesn't just survive but win?"

A finite mindset?

> "I want to take you back to early 2000 ..."

Does the world still look like the early 2000s?

I see these articles a lot, and always wonder why people go it alone. Can anyone link to a discussion about a distributed community run firewall? Does such a thing exist? If so, please comment.

Me too, Australia.

Interesting that Windy uses a version from 2018. (v1.4)

Government has been sold on the "Hobbes" vision of society and believes an assertion of authority is necessary in order to prevent civil chaos. They will never give money directly to people until this changes. https://issuepedia.org/Hobbes_vs._Rousseau

I looked into vending machines many years ago and the overheads were massive. Insurance, maintenance, local government approvals, stocking, supply chain issues, vandalism, and the list goes on and on... it is a business where you must scale. You need to be running a fleet of vending machines to make it worth the hassle. There are some interesting companies tackling some of these issues in the IoT space.

My 2 cents... generally a product is something that has value to others... so, think about that first. Why is your product valuable to others? Explain your product to at least one person who is not invested in the process that would buy your product if it existed. Ask them lots of questions about why they would buy your product. Would their friends buy your product? Why? Can you pre-sell your product before you even start building it? You get the idea... sell first, build after. Sell a little, build a little, repeat.

@bdon Awesome! The geospatial industry is in need of simpler tooling for specific jobs such as generating tilesets.

Currently complex tools such as QGIS and GDAL do everything, but the learning curve is very steep.

An addon you might consider a feature to drop an image (and adjust it to fit) over the OSM data to generate a XYZ tilesets directly on the customer AWS S3 (or equivalent storage).

This might be a good way to monetise your offering... I know my customers would buy it.

I tried out Disqus about 3 years ago, and found the API horrible... see SOF thread here. Might be worth doing a React wrapper to make it easy to understand how to integrate with frontend. https://stackoverflow.com/questions/48653016/does-the-disqus...

I must be missing something here... is the article suggesting by going to evil.com it somehow has access to the auth cookies of bank.com?? If that is the case then you are screwed. CORS isn't going to save you.

The file Austriaia.zip is data about Austria NOT Australia.

Love it! If you make the sliders update the URL I bet people would feel more inclined to share their settings rather than just play it.

Only if it going to actually hurt to lose it... when did these guys every really get hurt... they hedge their bets exactly so they never put themselves in a position to literally loose their house(s).

I think this adds to the case for Rousseau's Theory of human nature... https://en.wikipedia.org/wiki/Jean-Jacques_Rousseau

Hi All, OurContacts provides tooling to access shared contacts for dynamic and mobile teams.

Nursing, for aged care and home care, is the perfect storm, dynamic mobile teams with a fair amount of staff turnover.

I was also partially inspired by "The Social Dilemma" to take a look at ways to help break away from social media lock in.

I have been building web apps in the aged care sector for a number of years, primarily for home care and other mobile workforce applications.

Yes (sry) you have to create and account and login... for those about to comment, login=skip, it is still the easiest way to build a web app.

Yep, this is where I switched off. If the advice is to "look good" to investors based on the type of spreadsheet program you use you've got bigger problems.

This article, like so many others, seems to think enterprise B2B selling will somehow translate to startup SaaS businesses.

Ask yourself, what is your favourite paid service that you use nearly every day and then talk to your friends about? Maybe it's an awesome game, or a cool weather app, or an accounting package, or whatever... build a product/service that is so compelling that your users will sell it for you.

I'm in no way affiliated with Sabri Suby, but I recommend checking out his concepts... #1 start by giving your customers something for free and begin to build trust. Google this: "Sabri Suby Magic Lantern Technique".

Cool! Can you give an overview of the "Amazing AWS Stack" you have implemented?

A "fund me style" could be something like https://opencollective.com/

Hi, good job the sheet looks great. I was wondering why you choose the licencing model over the fund me style that many are choosing?

I have been looking into this type of system with a colleague for a few years now. We have been working on a concept of an attention based email network which is essentially a way to map our natural limited attention to the digital world.

This type of system requires a mindset that involves multiple parties, not just the receiver, so it becomes a non-trival exercise when considering the attention of multiple parties using multiple email systems.

In a practical sense, we looked at adding a multi party reputation system to the email standard which would involve adding meta data to emails to indicate the "trust" level between the recipients. There are clearly quite a number of technical challenges for this type of system. Fastmail seems to be doing some interesting work in this space.

https://fastmail.blog/2015/12/17/the-endless-battle-against-... https://tools.ietf.org/html/rfc5322#section-2.1.1