wesleytodd

I didn't intend to imply it was standard. In fact I meant that it was not standard and that is why I was lucky.

This mostly. But also I don't self identify with a strongly held ethic. I identify more with a balanced approach where sometimes ethics are a guide, and other times the outcome is as or more important, just depends on the situation.

In the case above, both my ethics and the outcome pointed me in the same direction. In others the might conflict and I do a cost benefit analysis.

Personal anecdote:

I was contacted by a facebook recruiter a few years ago. I started the process and also started thinking about if I would like working there. I realized that I disagree strongly with the product, its effects on society, culture and politics. But more importantly I realized I hadn't used the product in like 3 years. I just said no thanks before even finishing the "take home" exercise.

At the time I was not a college grad, I was a team lead at a startup. This was before all of the recent news (2016?). It turns out I was right to make that decision.

I think there is strong incentive for engineers who commit to working on projects which they would actually use themselves. I am not overly ethical as a person (although I do have opinions I try to stick to), but I am very happy to have the opportunity to work at companies with products I actually use.

I think this is outdated. I tried in Chrome, FF and Safari, and even when I follow what the original linked article does it still does not work.

Preach

I got a new MBP for work, and every time I go home to my ~2015 model I am so happy to not be typing on this new shitty keyboard, and that is to say nothing of the oversized trackpad always accidentally causing me to move my cursor with my palm.

Yep, anecdotal evidence :)

I will say, where I am now (bay area FANG company) it is WAY more common to have traditional CS background and also be a high performer.

I attribute that to a biased selection in SV, and not an actual correlation of CS education to higher skill level.

I noticed that as well. I have always thought there might be a correlation between self-taught and self selection for success in a topic.

Anecdotally, I was self-taught, and many of the highest performing engineers I know where also. Most of the average performing engineers I know were traditionally educated in CS.

Complexity is a choice in most programming ecosystems. The most simple applications I have ever worked on are node applications.

In some ecosystems it is more consistently complex (Java?) but others just have many approaches with different complexity levels for you to choose from (node?).

What is amazing to me is that twitter still does not have a solution for sharing mobile links to desktop users. It is a really bad user experience.

I hadn't heard of Overnet, so here is a wiki for others like me: https://en.wikipedia.org/wiki/Overnet

That said, it seems like "what makes it better" is that it hasn't received a take-down because this isn't attempting to be a solution for copyright circumvention ;)

>For example it exists both in React and JavaScript

There is a funny hot take in there somewhere...

My argument is more that forcing tech companies to invest in distributed data ownership tech would push that forward in a way that would enable more competition of services because your data would be portable, not locked into vendors like it is now.

In the short term it might result in less variety, but only until the tech proliferated and reached maturity. Then services could simply spin up on top of the data that you already host yourself. So you would have to take on the responsibility of finding a good way to host the data you want available (probably from your phone), but after that you would be able to use any service willing to operate on your data, but your data would be in public standards, not proprietary storage inside a facebook/google/amazon data center.

Here is an interesting take on this "why?" by @pfrazee:

https://www.youtube.com/watch?list=PL37ZVnwpeshG2YXJkun_lyNT...

Check out beaker browser and fritter:

https://beakerbrowser.com/ https://github.com/beakerbrowser/fritter

Built on top of dat, it is basically this kind of architecture.

It was not intended to provide privacy, the the distributed data store. If you want privacy you probably just want to have a private swarm, which is perfectly fine to setup. Just implement a client with a whitelist or another mechanism for the privacy you want.

Also, I am quite aware of how disruptive this ideal would be to most of our current large internet companies. I don't think it will realistically change any time soon, and am sure it would have side effects which would have to be balanced. But the direction we are headed now seems much worse to me than the alternatives.

Yeah I don't want to be hosting data I have not vetted either. I think being aware of the content any device you own is serving on the net is a good thing, even if it reduces the amount of people willing to do it for others.

TBQH if small companies cannot host user data that is good too. It should be very difficult for companies of any size to house data they are not willing to defend legally.

Check out Dat: https://datproject.org/

I think the faster we make companies liable for the content on their servers the better. Why? Because I want distributed/federated data to become an actual priority to these companies. I want it to hit their bottom line when they get sued for content uploaded to their servers so they consider keeping the data owned by the user who generated it.

One can hope

Lol, down to 340. It was ~200 in January. So it is only up 60% this year.

I am a professional developer who primarily uses React and I actively avoid most of this. I keep up with the community so know (or at least know about) almost all of this, but choose not to use it all.

The direction I have seen react go is exactly the opposite of the reason I liked it in the first place. It was simple and JUST A VIEW LAYER. How it became all of this is just typical software devs over complicating things for themselves IMO.

Sure! (at least I don't see why you wouldn't be able to)

I think you are missing the point here?

Everyone is a server is pretty much the opposite of "serverless". The article is just illustrating the migration path from traditional web assets from centralized servers and how you can use them in the distributed web.

A real life use case would be something like:

You want to build a financial tracking app in the distributed web. But your bank is the central source for your data. With the method shown in the article you could request the api endpoint from bank.com inside your p2p/Beaker app then load that data into local storage/a dat archive/memory and use it to track your data. Think mint but without giving your bank credentials to a 3rd party.

I think "laws or misstakes by big corps" are exactly what we are seeing happen #Facebook #GDPR

I think the really interesting things here are more than just "support new p2p transports/protocols". The things Beaker is doing around changing the way we author the web are the real important pieces, and finding the "middle ground" or transition path is one of the keys to success. So, to answer the OP as well, supporting loading assets from traditional servers is pretty much a requirement for authors I think.

> If you publish a dat archive, how do you notify Hashbase to pin it?

This is provided by hashbase in their ui. Sign up for an account and add your dat. It is email based, no credit card/address unless you go over the data cap.

If you are uncomfortable using the service you can run your own node, it is open source: https://github.com/beakerbrowser/hashbase

dat://pfrazee.hashbase.io/blog/dat-and-servers