Thomas DeMarchi from Team Sentivate answering community questions

SENTIVATE IS A HYBRID WEB BUILT TO BE A VIABLE & REALISTIC REPLACEMENT FOR THE MODERN WEB

Thomas Marchi Co-founder & Developer

Ok just read the wallpaper and I have multiple questions, mostly about UDSP.
You claim TCP error checking is a hassle and a waste of resources, but I don’t see how you can ensure reliability and ensuring the end user gets the data if you throw all error checking and retreanmission out the window…

TCP has a reliability layer built it. UDP doesn’t so the answer is simple we coded one. One word HTTP3. Drops TCP for UDP like we have been saying. It’s a mixture of HTTP and QUIC.

How does UDSP behaves on a network with 30% packet loss for example? with TCP you would see a ton of retransmissions and slowness, but the app would still work

Yes TCPs reliability algorithm is outdated trash. Look at QUICs for a detailed over view of what the current implementations look like. People who ask this seem to be confused with how protocols work. You can build these additional layers on top of UDP like the encryption layer and reliability layer.

Why build your own browser and not a plugin for existing browsers? this will make adoption easier

Not possible need much lower level access. I would look into the restrictions placed on browser extensions and the access available to them.

If you tried to retrofit things into chrome via extensions one would need to use channels there wouldn’t be a fluid form of communication and would be slower than the alternative because of all the middleware you are going through. Best way is to use Electron which is based off of Chrome and Node. Package it up and ship. That’s how you do that correctly. This project is was too big and way too complex for it to be a simple chrome extension hahahaha. I laugh a bit every time I hear that.

Do you have interoperability plans? how would a regular non sentivate user access sentivate applications?

Server & Client modules very easy. Plug and play environment via Node & NPM.

Another confusion I see if that you assume that when shipping the browser you need to install Node. This isn’t the case it’s all packaged up ready to go. If you are developer working with Node or attempting to use a Node module I seriously hope you have Node installed or chances are you need to start back with the basics haha. Much like any project dependencies are needed during development. Skype uses Electron which uses Node are people installing Node before they install Skype? Of course not it’s all packaged up into one install called Skype. It’s a click and run depending on your OS.

What are your thoughts on QUIC? seems similar in some aspects to UDSP

If I were to pick a protocol most similar to what we are building it would be MinimaLT meets WebSockets. QUIC is still designed to transport HTTP and is not designed for real-time long lived bi directional streaming.

QUIC is designed to fix the faulty parts of HTTP while still transporting and working with HTTP. Nothing like we are doing. We are throwing those semantics out the window total waste of time. Would buy us time not a solution.

If we are paying homage to anyone from UDSP it’s Minimalt. As to why we mention them all the time. QUIC is being merged into HTTP. For us that’s an abomination and a total waste of time in the long run. Although we fully understand why it was done for the sake of the bottom line and to save bandwidth. The margins it has are small though because they are still using Half of HTTP to make HTTP3 with it. It’s all about why they are building it and what are they doing with it. That changes the design and capabilities of the protocol. Once you put yourself in a box have fun getting out. We make no attempt at putting UDSP in a box. There is a tremendous amount of flexibility there.

Performance wise, isn’t javascript slow when compared to some lower level programming languages like C? further, javascript doesn’t come by default on most operating systems, which would make it harder to get the suite of tools working on other OSes if adoption starts to rise.

Again seems to be a none dev question. Firstly it’s called ECMAScript. Secondly Node supports native modules and has a huge lower Level API than traditional “JavaScript” in the browser. Node also supports native modules which can be written in C,C++ and even Rust. If anyone chose to write this in C I would ask them to have their head checked out to say the least.

It’s very easy to install Node. That’s just silly. More importantly long term Rust is the most likely candidate a long with a Java and Swift port for mobile usage. C and C++ is highly unlikely and also comes with many security related concerns that Rust eliminates.

Another important note is remember the web has a new language called web assembly which after perfected will have drastic speed improvements over standard ECMAscript running in a browser. Although I’m personally skeptical of its performance when it comes to Node as compared to native modules. Our money is on Rust & Swift as of late. Node/ECMAscript has an advantage that not a single language out now has. Massive amounts of active developer support, constant new language improvements exceptional at handling asynchronous operations with async/await. Node compared to any other environment has a super low barrier for entry and is quick and easy for new comers to pickup. God forbid we chose python or C++. We need to make sure we can build and build quickly. From a golden build we can easily port although we will be avoiding languages like c++ and or C. I use to write server backends in C that wasn’t very fun and the language is extremely unforgiving. Not suitable nor the smart choice when it comes to mass adoption. It’s about people not the machines. Many devs and people forget about the human component in all of this

That’s all my questions

whitepaper was a great read and this surely looks like a promising project!

Synopsis

Sentivate has currently a market cap of around 3m$ it is ranked even lower on Coinmarketcap cause the circulating supply is not correct. (the true supply is 1.3b SNTVT)

While the project itself is more than ambitious, the dev team behind it is working nonstop and no one seems to know more about the topic than Thomas.

He’s always approachable, loves a challenge and a discussion, as you can see above such “Interviews” happen regularly and critique is very welcome.

While the project is still in early stage, it already achieved a huge community of dedicated followers and supporters.

Recently Chico Crypto joined the team as advisor and he’s doing a superb job breaking down the complicated project into interesting and understandable Videos.

Another addition is Ali Alexander who has some connections to Twitter CEO Jack Dorsey himself.

These are not people that jump easily on a train, they are both well known and get approached by massive amounts of requests, both of them had 2–3-hour conversations with Thomas DeMarchi and both were blown away.

I do get the critique when you never have talked to Thomas, I too get approached a lot by projects and seeing such a low cap you easily dismiss it.
All I can suggest is, overcome your prejudice and talk to the team, ask difficult questions, challenge them.
I assure you, you will be amazed.

From the scale of what they are trying to achieve its hard to rate Sentivate, but you could compare it to Holo which is currently rated at a 212m$ cap.

Sentivate would have a 70x from here to achieve this rating and don’t forget we are still in a semi-bear market.

200m caps were nothing to write about in 2017.

But let us stay realistic, Sentivate still has a lot to prove, and a lot to show.
I am eager to see more of this undervalued project.

Some links to dyor:

Hybrid Web, Blockchain, & Cryptocurrency

https://twitter.com/sentivate 
https://aritysoftware.com
https://sentivate.com
Exchanges
https://app.stex.com/en/basic-trade/pair/ETH/SNTVT/
https://idex.market/eth/sntvt

brought to you by:

tehMoonwalkeR
TG announcement channel: https://t.me/tehmoonwalkin
TG discussion channel: https://t.me/joinchat/FgncLw8SKo3w_nrlvmpeUA