3dfan

The subscription costs money? I don't see any info about pricing.

Can't decentralized exchanges be completely anonymous?

If a user sends some ETH to an adress and on some Bitcoin address a balance shows up - how would the SEC want to regulate that?

Let alone exchanges that are just a contract on Ethereum and only exchange tokens on the Etherum blockchain. What is the SEC going to do about those?

And what would happen if some country in the world tokenizes their property. Say a certain token on the Ethereum blockchain means ownership in a company in Sweden. What if a US citizen buys such a token by sending ETH to a smart contract?

So many questions.

Shouldn't these have been kinda answered already in regards to international exchanges? What if a US citizen buys stock on the Euronext Paris, the French stock exchange? Would the Euronext Paris have to be registered with the SEC? What if they are not? Are they committing a crime in the eyes of the SEC?

How does it work? Do you upload an SPA and then you download something that can be uploaded to the appstore?

How can your customers be sure you do not inject any faulty or malicious stuff into their apps?

Is the business model in-app purchases? For what do the users pay?

What's your business model?

Via ads?

Isn't the revenue per generated site super low? How can domain owners put in all the work to bring their own monetization and still pay you?

ASO is like SEO for appstores?

Soon AI will not need a lot of training data anymore.

Anybody will be able to let their computer listen to one Metallica record and say "Do you hear this? This is called heavy metal. Can you make an album like this? With distorted guitars, a screaming singer and heavy drums?" and the AI will understand the whole concept and make a new heavy metal album.

How do you earn money? Affiliate links?

How do the properties get onto homestra? Do landlords find your site and enter the data + pay you? Or is the model different?

First, no, you cannot reduce a thousands of words long legal document to a few words like you did and say "Easy, this is how it works". Those thousands of words are there for a reason.

Second, good luck, figuring out what you have "a contract, permission or a lawful task" for under the specific circumstances of your site.

Third, good luck, making and understanding an "agreement that binds them" with every provider of every piece of infrastrcuture you use. Good luck doing that for even a single piece of infrastructure.

The problem with the GDPR is that it is a monster of a legalese text:

https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELE...

Which nobody understands.

Which, depending on how you read it, might make participating on the internet practically impossible. An IP is considered personal data, so in theory you cannot use foreign infrastructure like a CDN.

Which certainly makes the internet as we know it impossoble. An internet where everybody builds tools on their site that everybody else can embed on their site. Because that would mean IPs flowing around between sites.

Which gives a huge disadvantage to Euroeans. Because Europreans have to show cookie banners and stuff to everybody around the world. While the rest of the world has to only show them to Europeans. Look at your favorite website through a proxy inside/outside the EU. It starts with an annoying popup only in the EU.

Which cements the stronghold of Google and Co, who 1) only have to bug their European users and 2) have the legal resources to cope with this insanity. Startups and indiemakers don't. So there will be even less of them in the EU. And the ones who exist will have to waste their time on this instead of building their products.

It seems to be a universal law of software projects:

1: Start out lean and simple. Often replacing an old complex one

2: Become more complex over time

3: Be replaced by a new lean and simple one

Oh yes, I use the map too sometimes.

The reason I mostly use Gnovies is that I often watch together with my girlfriend. So we each put one movie into Gnovies "enter 3 movies you like" form and after some experimentation we usually find a new one we both enjoy.

I am a huge movie fan. And always lost in thoughts. So I guess I will go through the whole "reflective" list and see if there is a movie I don't know yet.

Lists of "popular movies" on Netflix etc never click with me. Most stuff out there is too kitchy for me.

One tool that works for me is Gnovies, which finds a mix of 3 movies you put in:

https://www.gnovies.com

By the time people are allowed to let their cars drive unsupervised, the crash rate of AI versus human will probably be 1:10 or so.

So even when those cars ram into fire trucks from time to time, it would be better to let them do their thing. Otherwise people will grab the steering wheel, drive drunk, sleepy, angry etc and ram into all kinds of things again.

Currently, there are 6 million car accidents per year in the USA. Almost 100 people die in car accidents every day. So there is a ton of data to make the decision.

Is that the shortest way to write it in Cypher?

SQL needs 48 chars:

    SELECT name FROM cities WHERE population>1000000

    MATCH (n:cities) WHERE n.population>1000000 RETURN n.name

I think the language the developer writes their queries in is most important. It is very easy and logical to express what you want in SQL. Say we want to show a list of cities with more than a million people. Easy:

    SELECT name FROM cities WHERE population>1000000

Sounds scary.

I would not want to use a CDN with some hidden limits. Especially not if I don't even get informed when rate limited.

I can imagine them rate limiting me in a way that I will never notice. Like only limiting requests from some other country or continent.

What is a good CDN for a site that has about a million visitors per month? And how much would one have to expect to pay for it?

    You can point the _acme-challenge
    record to another domain using a CNAME

That's what I call a pain in the ass.

It's still a pain in the ass to manage wildcard certificates with letsencrypt.

Especially when your DNS registrar does not support DNS changes via API.

And even if the registrar supports it, you have to build and maintain the code that talks to the API. Yuck.

I wonder why they don't allow whover controls the domain name to use the domain/.well-known/acme-challenge to create wildcard certs that are valid for all subdomains of that domain.

So far the need to store images in this folder did not come up.

Can you give a use case?

It is simply evolving.

For example when the graphics person wants to save something for the first time, they might make a new file graphics.txt and put in the information they want to keep there.

If they then continue to just grow that one file, all is fine. If they feel the need to have multiple files, I advice them to make a subfolder graphics/ and have their files there.

Search is simply done via grep.

So to see if someone wrote something about logos, we typically do:

    grep -ir --color logo *

We have a directory lessons_learned/ with *.md files.

It's a git repo and everyone can pull/push directly to master.

I skim the commits once a week.

It's basically plain text files. But the md extension triggers some nice eye candy in vim and other browsers.

I think we will keep this structure forever. Maybe we will (additionally) serve the files over http at some point. Maybe we might even add edit / search / push functions over http, but for now I have not planned that.

I have seen CMS come and go. And I'm tired of it. Text files are forever.

Why is the performance of Apps higher? Isn't both just code executed on the client?

Why is an app needed to display things on a map? Isn't that something a website can do just fine?

Which brings up an interesting, more general topic:

Why do we need apps at all? What is the fundamental difference to websites?

Why is this needed in the codebase?

    export const getFullYear = 'getFullYear';
    export const getMonth = 'getMonth';
    export const getDate = 'getDate';
    export const getDay = 'getDay';
    export const getHours = 'getHours';
    export const getMinutes = 'getMinutes';
    export const getSeconds = 'getSeconds';
    export const getMilliseconds = 'getMilliseconds';

https://github.com/leeoniya/uPlot/blob/master/src/fmtDate.js

Yes, crawling and publishing crawled data seems to be a very complicated, grey area.

Did you do some research of the legality of this?