folex

how to use NPM through SSB? is there a doc or guide?

Yes, it's a struggle. I fell-back to just using TV's browser for watching almost anything.

> If you mistype it and nuke more than the last commit, that's also a bit bad - and fairly easily done.

If you ever run into this, you can use `git reflog` to see the history of your local actions. It's possible to revert almost any action with it.

Reset a few commits that you've never pushed to remote? No worries! Just go to `git reflog`, find a point before it happened, and `git reset` to it.

    $ git reset --hard HEAD^^ # OOPS
    $ git reflog
    c48300f3 (HEAD -> master) HEAD@{0}: reset: moving to HEAD^^
    527e26e0 (origin/master) HEAD@{1}: commit: air-interpreter-wasm = "=0.14.10"

    $ git reset --hard HEAD@{1}

And you're back before "OOPS" :) It's really hard to lose changes once they've been committed.

For some reason, 78 RPM (https://www.locserendipity.com/Listen.html) doesn't work for me - I press Random, then link, then Play, and nothing happens.

Chrome, MacOS 10.14, no adblock

or fluence.network

Disclaimer: I'm just describing an annoying technical problem, it's not a blocker for the use of Elm. Elm _is_ great :)

I have been using Elm for a kinda-simple project on my work: dashboard for microservices, deployment configs, nodes, etc.

One of the biggest time-drains was debugging JS-Elm port interactions, looking whether there is a mismatch in types.

Cuz the error looks like this:

  Elm eventreceiver failed:  Error: Trying to send an 
  unexpected type of value through port `collectPeerInfo`:
  [object Object]

I know of no way of even looking into that `[object Object]`. Simply logging its fields would already be a relief, lest telling what field/type caused the error.

Elm is awesome, its compiler is awesome, but its ecosystem is kinda stalling, isn't it?

I mean, a lot of libraries aren't updated to the last lang version, debugging JS-Elm interactions been a real challenge for years, yadda yadda. Overall I'd say Elm ecosystem doesn't receive enough attention to survive.

I'm not complaining, I'm just sad about that and kinda surprised I didn't found a mention of that in the OP article.

I think "1 container = 1 process" is a common misconception. There should be a separation of concerns, but there's no reason to go to extremes where it doesn't make sense.

S6-overlay people lay it out pretty neat https://github.com/just-containers/s6-overlay#the-docker-way

Same in Russian, rooster (petooh) is used for high pitched voice crack. "Made a rooster".

OMG, I've been dreaming of this tool for years. Thank you!

Does it work offline?

I just learned about S6 recently. It simplified daemon supervision for me a lot.

Grigorik book is awesome, must read

The Denial of Death by Ernest Becker is also good

How is discovery implemented? Is there a DHT or some gossipping?

I found only this:

> However, we believe it should be possible to bootstrap Wildland without any Wildland-specific infrastructure, such as supporting some custom network protocol

Does this mean that RnD haven't yet touched networking?

Fluence Labs | 100% Remote | Rust, Distributed, Compiler, WASM runtime

https://fluence.network/join.html

Our primary project is Fluence, an open application platform, where apps can build on each other, share data and users. Fluence is powered by a decentralized computing protocol that enables applications to evolve quickly with composability and monetize by licensing even low-level components. Fluence serves as an open runtime for internet applications; the new alternative to proprietary platforms, and APIs.

Fluence | https://fluence.network/join.html | Remote

Our primary project is Fluence, an open application platform, where apps can build on each other, share data and users. Fluence is powered by a decentralized computing protocol that enables applications to evolve quickly with composability and monetize by licensing even low-level components. Fluence serves as an open runtime for internet applications; the new alternative to proprietary platforms, and APIs.

    - Distributed Systems Engineer
    - Compiler Engineer

It's so strange to have this "areas of death" in our towns. You turn the wrong way - you're dead. You saw the wrong color - dead. I understand that it takes some evolution to solve that, but it's SO. STRANGE.

Imagine people who never saw that concept - high speed (>30mph) roads near pedestrians. And then someone comes and says "Let's build these danger zones with custom rules, they will allow people to leave public transport for personal vehicles. And if you step it wrong, you might get killed!".

Would these people agree? Would they take it as a natural idea? Insane.

Hi! Sorry for the late reply.

Here's a screenshot of my screen from the time of writing the comment https://i.imgur.com/ngD1Xkj.png

I'm on a macbook pro 15.4-inch (2880 x 1800).

I see you've changed background, thank you for that! <3 Now it is far far better. Though I still find myself having to try harder to read the text on such color. I'm not sure of the reasons, though. Maybe it's me, maybe it's f.lux.

(though f.lux is on Movie Mode, meaning the dim and color correction are lighter than default)

P.S. I do not know of and never experienced any color perception problems.

Thank you for your tremendous work!

You may take a look at Fluence's ideas on that https://fluence.network

It basically allows you to share your code to others in exchange for a fee. If someone builds an app or service that uses your library, and it is paid within Fluence, you will receive a fee. This works transitively.

Background gradient makes me dizzy after reading a single paragraph

> The ISRG's approach of working directly with maintainers to support rewriting tools and libraries incrementally falls directly in line with our perspective here at Google.

Incrementally – that means in-place. You can't fork and rewrite incrementally since there will be no adoption/users of the fork.

Also they talk about maintainers of the projects. I think that largely means original authors and maintainers, not forks.

I don't see how you come to that conclusion. Could you clarify? Thanks :)

Strangely no mention of High Performance Browser Networking https://hpbn.co

I also would mention Distributed systems for fun and profit http://book.mixu.net/distsys/ while being not exactly about network programming, it is likely a next step for anyone who's building apps that is scattered across several backends/services connected by the network

Nice tool to play with! Unfortunately, it freezes if you have lots of drawings

Would be awesome to have at least single test + run + output example in the README. At least as a screenshot, link to playground or something. I open website, see marketing, open github, see marketing.

So many great books! Thank you.

Though I can't seem to find a PDF of 'Search for simplicity' :(

Looks like another marketing article, empty of any insight.

Well, I'm not just hand-waving (at least I don't think I am), I'm actually got burnt by this. I was building a demo of my app on top of libp2p, and then I discovered that I need to issue domain name and certificate for each node in my p2p network.

This wasn't hard – caddy2 makes it super easy. But I see it as a pretty weird requirement. I don't understand, why can't I sign some data with public key without being on secure origin.

> The only reason you can think of is a weird conspiracy? I didn't mean to assume conspiracy theories, I agree that this is a pretty unprobable story. I'm just saying: "It's so weird that my only sound explanation is a weird conspiracy theory", meaning that I don't understand how this came to be, and motivation behind that :)

There's a great wasm-crypto library out there, and while its authors are doing amazing work, there's much more effort put in WebCrypto by a lot more people.

There's also an option to compile some e.g. Rust library to wasm, and use it, but it could hide some exotic security vulnerabilities that arise only in this narrowly-adopted use case, so it's a pretty high risk.