One of the biggest things we need now for Web 3.0 is standards. Basically, guidelines so no matter what blockchain Web 3.0 is on. It in theory should more than less work.
NOTE: If I had to guess I would think we are in ARPANET times if we are to compare it to the normal internet. Or maybe even prior to that. I think we seen nothing when it comes to the full power of Web 3.0.
Here is what I want to see.
- Sites are NFT. Basically, this comes in 2 fold. The first is the bulk of the info could be stored on private servers or private blockchains. I imagine gov, medical, and so on would want to do that. The other fold is the entire site including pictures, videos, and download files is on the blockchain. It could be multiple NFT and the code points to it like it would point to a picture on a server. But if you right click this website and click inspect. The code you see and what the browser uses to show you what the owner of the site wants you to see is mostly what will be on the blockchain in both cases.
- Browsers on Web 3.0 can act as bridges between connected blockchains. Basically, we need standards for browsers to be made which will allow things like NFT to transfer from 1 blockchain to another. And for the browser to adapt and redirect to a new blockchain. I imagine you will see governments using their own blockchain for internal things like taxes. The user shouldn't have to know how to do anymore steps than they need to right now in order to upload a file. In fact, they shouldn't even know if it's on another blockchain unless if they use some inspect or something.
- We need standards on how blockchains should handle data being transfer from 1 to the other, if the company wants this info public (maybe medical files shouldn't be shown, but already public part void any rights and it will be logged). And the blockchain can point to where the file has been transfer to. And how DNS should handle this.
- We need standards to note if a site has been changed, and how to handle that and link creation. IMO it should be earmarked when it was edit, but one of the problems we can solve is link rot. Depending on storage abilities, it might be possible to save the text only or some level of a site when a link is made in a special way. What come to mind is legal opinion papers from the Supreme Court in the USA they have a ton of dead links in them. Well, if they used a special way to make the link which preserves the info. And if there was a way to detect when a
Question in the title, but here it is again
It seems like every top tier team I work in insists on Yarn over NPM, almost unanimously it seems like all of these killer devs know Yarn is the industry standard on serious projects. Why do all documentation across the web default to npm installation instructions and assume you're using npm?
A couple years ago I experimented with Mediatr to create a web api using CQRS. Fast forward a couple years and even though I haven't used it for any formal projects, i've started to see it mentioned more and more, most recently in the following dotnet documentation - https://docs.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/microservice-application-layer-implementation-web-api
Does this indicate a shift towards CQRS as a standard development practice for asp core web api's? Much like how Dependency injection became standard practice when dotnet core was released?
Does anyone else use CQRS in they projects? What are the benefits and issues?
Don't get me wrong, it's incredibly well made and loads at lightspeed. However, there's a lot of other sites I could say do the same. What makes Stripe stand out?
Just looking for references on this topic. Interested in any vendor. Thanks.
I believe the process is -
- Fork the repo
- Work on the feature
- Test the feature to see if it would work on production
- Have the code reviewed
- Send a PR
- Team lead commit squashes and merges your fork to the main repo
My problem is with step 3 and 6. How do I test features I wrote on my own? I would usually deploy the code from my github to my cloud service. But I am not sure if it is good thing to do. When I see it works on my machine and my cloud setup. Then I will let them know I have completed the task. Then comes 6 which is troubleshooting my messy fork. Because I treated my own fork as my own version control this meant that my commit messages won't make sense or even remotely useful to the team lead. They would need to remove all that junk do a commit squash then merge my PR.
I am not sure but it all sounds quite messy. I wonder what does the real life workflow of a full stack team looks like?
All help is appreciated.
I am looking for a way to scrape JUST the text from different articles on the web. The algorithm should be able to handle any URL you can give it. Depending on the journal, or magazine, the article text is stored in different ways. Wondering if this is possible without AI?
I am looking for a way to scrape JUST the text from different articles on the web. The algorithm should be able to handle any URL you can give it. Depending on the journal, or magazine, the article text is stored in different ways. Wondering if this is possible without AI?
