parisk

The whole scammers thing is true. We have faced it with SourceLair. Thankfully there is 3DS 2 now and you can be super strict with which transactions you can accept. IMO the safest way to go is accept transactions, where you have no liability.

Also, using a SaaS service providing a complete checkout experience can make this super easy for you.

Great questions.

The encryption key is generated in the browser. This key is being used to unseal your vaults. When you create your account, the key is being exported (downloaded) to your file system. Every time you sign in afterwards, you need to import (drag and drop) the key to the browser — it is never transmitted to our servers —, so you can unseal your vaults locally.

No product can be free. We believe that €39 per year is a great price for what you get; a ridiculously easy to receive sensitive information securely with end to end encryption, that does not even require both parties to have an account.

Hello there,

I am Paris, one of the creators of Vaulty. Thanks for your comment.

Vaulty end-to-end encrypts/decrypts data in the browser. No sensitive information is ever being transferred over the wire.

This is actually the whole point. The easiest way to share end-to-end encrypted data even over insecure channels.

I hope I answered your concern! You can give it a try for free to see how it works at https://vaulty.tools/guest/vaults/.

Thanks for sharing this. Wow, that's plain bad.

Thanks for your comment.

(1) Was the charge for the ride apparent before hailing the not-technically-a-taxi?

Unfortunately, not.

(2) If not, what app was this?

I am not naming the app intentionally. I do not want to shit on anybody's work to be honest, even though I might disagree strongly with it. I might as well be dead wrong about this and missing an important point.

Thanks for sharing your thoughts.

I do not have a problem with exceeding business cost with high profit margins. I think that's OK and actually I believe it's the right way to build a sustainable business. I do have a problem when charging for conceptually wrong reasons.

When using software, instead of traditional means, to do an existing job, it gets way cheaper. That's when you don't get to charge £15 for using it.

If you do need to charge £15 for some reason, please do. It's not the software I am paying for though in that case and I need to know what I am paying for.

Thanks for sharing your story. Sounds like my country, Greece, a few years ago. Letting strangers in your car is high risk, especially during night and even more in particular areas of the world. Cab hailing apps already workaround this, since all routes are hailed by passengers with verified personal details. This means that it's not easy to violate and leave. Even less in the UK, where most cabs have CCTV inside.

Thanks for your comment. All your points are valid. I do understand that and I have no problem paying premium for certain services, such as high risk ones. The problem here is its marketing as "technology fee because of high demand" at £15 for a £4 (fake) route.

Thanks for your comment. I just tool their word for it :). That's interesting though. If you can share a link validating that, I can update the article to better represent reality.

Communication skills are necessary for all job positions.

Remote working is quite new to us though. People have worked on site for thousands of years, while remote working just appeared in the last century or so and it has different communication needs.

My guess it will take 10+ years from now to cultivate remote communication skills so that they work intuitively for the majority of software developers.

Spot on. Nothing to add here. Couldn't help but share: https://twitter.com/pariskasid/status/1101068226677608450.

Definitely not the end of the world. I was very happy though to understand why relational databases is still the right choice for the most web applications, to store their data.

Well, we will never find out now!

I am happy you are interested in the State of Progress. The next article is on its way.

Great comment. Let me reply.

The content of all articles is sourced from our experience on working on commercial products and open source projects, no just plain though sharing.

Let me share some more insights on the previous topics:

- "Relational vs. Object/Mongo store" this article is based on our experience at sourcelair.com. Choosing Mongo for our main data store has caused us more problems than it solved, and we have spent tons of hours working this out. After running this in prod for 3 years, we have a strong opinion on this that you should not use an object store for your main back-end unless you are a super exception.

- We we choose Swarm: Docker is a relatively new tech and while its adoption grows it has not yet the maturity and footprint of projects like MySQL or Postgres, so each case diverges more from another. This is why here we talk about "When does it make sense to use this" instead of "You should do this".

Hope I covered your question, but feel free to continue the discussion if you 'd like. It's an interesting topic.

Hi wingerlang,

Thanks for your comment. The first article will be published by Monday. A sneak peak on what I am working on right now for this blog is referenced at https://news.ycombinator.com/item?id=13069757 as well:

1. Well-structured repositories (What makes a repo well structured? Why should I do so? How can I do it?) 2. Why you should choose a traditional relational database as the main back-end of your web application, instead of an object store (e.g. Mongo) 3. When and why to choose TypeScript (or any other type-safe programming language)

If you believe that these topics are of interest to you, feel free to follow us. It would be great to hear your feedback on our articles as well.

Thanks a lot!

OK, I get it better now. We are not forcing or pushing anyone to follow us if they don't feel like it.

I am going to share with you though the topics I am working on right now. I expect the first one to be published by Monday.

1. Well-structured repositories (What makes a repo well structured? Why should I do so? How can I do it?) 2. Why you should choose a traditional relational database as the main back-end of your web application, instead of an object store (e.g. Mongo) 3. When and why to choose TypeScript (or any other type-safe programming language)

If you believe that such articles are in your interest, then feel free to follow.

Thanks for your sincere comments. I really appreciate them and take them into account for the future.

P.S.: The above are working titles. Most probably they will be refined and shortened.

Hi dozzie, you certainly got a point. We wanted to clarify our mission first and then progressively publish articles.

We are developers that prefer small and incremental updates to big (bloated) releases and this is reflected also on the way we publish.

As far as for coming back... you don't have to! You have the following options:

1. Add our RSS feed to your feed reader: https://stateofprogress.blog/feed 2. Follow us on Medium: https://stateofprogress.blog/ 3. Follow us on Twitter: https://twitter.com/stateofprogblog

Thanks for your comment, I hope you like what we have been up to!

Nah, I misinterpreted the word "connection". Xterm.js aims to be as close as possible to the original xterm's functionality as a terminal emulator, that runs in the browser.

Xterm.js is a front-end library only. You can use the "attach" addon though to connect it to a WebSocket stream and interact with a process.

We have an open issue at xterm.js to improve the performance of the terminal. While xterm.js has decent performance right now (can handle lots of incoming data), there is much space for improvement.

For more info take a look at https://github.com/sourcelair/xterm.js/issues/150 and feel free to take part in the conversation.

Hi rmetzier,

As mentioned in its GitHub repo GoTTY lets you "Share your terminal as a web application".

xterm.js is a front-end only library; a terminal emulator that runs in the browser.

This means that xterm.js could act as the front-end of GoTTY, but it uses hterm instead, which is a similar project.

Hi dakami,

I think that SourceLair (https://www.sourcelair.com) could fit your needs.

It let's you work on Node.js web applications in your browser and write both client side (including React JSX) and server side JavaScript.

You also get an HTTPS public URL (subdomain) that works out of the box with Node.js, while it integrates with Git and GitHub in order to collaborate and lets you deploy your projects to Heroku with a single click.

You can try it out for free at https://www.sourcelair.com.

Disclaimer: I am one of the people who co-founded and built SourceLair.