Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Apr 22 05:57
    plan-do-break-fix opened #624
  • Apr 13 13:46
    nponeccop commented #623
  • Apr 13 11:12
    linci8210 opened #623
  • Mar 26 09:14
    paulbjensen commented #619
  • Mar 26 01:52
    nponeccop commented #619
  • Mar 21 10:26
    paulbjensen commented #619
  • Mar 15 22:48
    nponeccop commented #619
  • Mar 15 22:35
    nponeccop commented #619
  • Mar 14 09:25
    paulbjensen commented #619
  • Mar 14 09:24
    Travis socketstream/socketstream (master) passed (969)
  • Mar 14 09:23

    paulbjensen on master

    refactor: fix a lint suggestion fix(deps): update dependencies chore(CI): use LTS and current … and 13 more (compare)

  • Mar 14 09:23
    paulbjensen closed #620
  • Feb 19 22:00
    Travis msand/socketstream (fix-transport-bundling) errored (4)
  • Feb 17 22:35
    Travis msand/socketstream (fix-transport-bundling) errored (3)
  • Feb 16 20:10
    Travis msand/socketstream (fix-transport-bundling) errored (2)
  • Feb 16 19:15
    Travis msand/socketstream (fix-transport-bundling) errored (1)
  • Jan 05 13:58
    nponeccop commented #619
  • Dec 31 2020 16:52
    Travis socketstream/socketstream (develop) errored (968)
  • Dec 31 2020 16:33

    paulbjensen on develop

    Create codeql-analysis.yml (compare)

  • Dec 31 2020 15:31
    paulbjensen commented #619
Robert Hall
@arxpoetica
I feel like we should try to actually schedule a post mortem on this, since we both seem to be figuring out the related issues—
Just to learn
Wylie Кулик
@kulicuu
ah hey ! yeah the library is closing here in a few minutes but i may be on later
and tomorrow 08:30 -- 16:00 ish, UTC+2 or whatever this is here.
yeah on further discussions, i agree.
UTC+3
Wylie Кулик
@kulicuu
Indicating we should continue with the modularisation of SocketStream -- continuing to break off core components into optional modules. In the end we'll be able to think of SocketStream more as an ecosystem than a framework. Or, as a set of materials and tools to draw upon in a given application.
Paul Jensen
@paulbjensen
I agree, I think the tricky bit is going to be untangling some of it.
Robert Hall
@arxpoetica
+1
Henrik Vendelbo
@thepian
IMO we should factor out decisions about session tracking. Apps are super important and would need local storage backed tokens/sessions rather than cookie based.
Henrik Vendelbo
@thepian
It seems packing assets was a binary choice for all views rather than per client. Shouldn't that be a flag per client/bundler ?
Paul Jensen
@paulbjensen
Good question. I don’t think it was considered to enable asset packing on a per-client basis.
Henrik Vendelbo
@thepian
Ok, will assume that it is acceptable to just update missing view assets
Paul Jensen
@paulbjensen
Hi everyone, back from holidays (Iceland, Italy). I’m going to be going to New York from 15th-20th to talk about SocketStream at NYCCamp. If anyone has any particular things htye would like to see in the presentation, let me know
Paul Jensen
@paulbjensen
Hi everyone, I put the slides from the talk at NYC Camp up at speakerdeck here: https://speakerdeck.com/paulbjensen/socketstream-nyccamp-2015
Wylie Кулик
@kulicuu
! awesome nice (! & thanks !)
reminds me i really need to write some tests for the engine
Henrik Vendelbo
@thepian
I plan make the SS internals use gulp internals for packing assets, running servers, live-reload etc. It will then be possible to define custom tasks through ss. or per client definition
Paul Jensen
@paulbjensen
I’ll take a look today, Thanks Henrik
Henrik Vendelbo
@thepian
Should be passing now
Henrik Vendelbo
@thepian
Should we make the default app generation depend on Express? It is the canonical framework. I don't see any popularity of the default http package, and the basic documentation is super confusing
Paul Jensen
@paulbjensen
Hi everyone, I have some good news, Henrik is the new project leader
Henrik Vendelbo
@thepian
For version 1.0 I'd like to have builtin support for ES6, but conversely I'd drop Coffee. Merely in terms of default project creation and primary examples. Any objections, thoughts?
Henrik Vendelbo
@thepian
The second thing I've been thinking of making is a move away from building assets when starting in production by default. It means that the builders must work on your target machines, so you really need to test that they work there. Instead I think building on CI or dev machines is a better option. Building on production would still be possible, just not the common example.
Vicary A.
@vicary
+1 for vanilla js
benemorphy
@benemorphy
nice frame, I will try it
Henrik Vendelbo
@thepian
Anyone trying out stuff with the new SocketStream 0.5 ?
nodecraic
@webworkio
hey, if anyone has any remote remote , designer, DevOps or Sysadmin jobs they can post them at http://webwork.io
quocnv
@quocnv
hi all
Paul Jensen
@paulbjensen
Hello
Mikael Sand
@msand
Hello
Paul Jensen
@paulbjensen
A lot changes in a year and a bit in Node.js land. It looks like there are a few tasks that could be done to get things up to date.
In terms of supporting the latest stable node
Paul Jensen
@paulbjensen
Merged a commit to run travis tests against 0.12 (legacy), 4, and 6 of Node.js
Manish Chandra
@chandrajob365
Hello Everyone
Can some please help me in understanding as why websockets or socket.io is used to make chat application if same can be achieved by TCP sockets ?
Mikael Sand
@msand
Well, websockets is essentially the thinnest abstraction on top of TCP, which is available in the browser. So, if you want no installation, single click on a link to start chatting, you need to use the apis available in modern browsers
Mikael Sand
@msand
also, QUIC has been gaining traction the past years especially regarding traffic between chrome and google infrastructure, this gives you a UDP based, no head-of-line blocking multiplexed streams, with zero round-trip-time encrypted communications, with actual encrypted payload data sent already in the first packet. But, only chrome/ium/opera and the caddy server support this so far
Manish Chandra
@chandrajob365
thank you @msand :)
Mikael Sand
@msand
you're welcome :)
Mikael Sand
@msand
also, if you're making a peer to peer chat, you might want to use SCTP as your level 4 protocol, it combines most of the good properties of both TCP and UDP and is supported in most operating systems and also in browsers using WebRTC
Mikael Sand
@msand
SCTP is also used in SIGTRAN, to carry the vulnerable Signaling System No. 7 (which is used to set up and tear down most of the world's public switched telephone network (PSTN) telephone calls) over the IP layer. The vulnerable SS7 allow cell phone users to be secretly tracked, eavesdropping, to bypass two-factor authetication (2FA) to do unauthorized withdrawals from users bank accounts, etc.
https://en.wikipedia.org/wiki/Signalling_System_No._7#Protocol_security_vulnerabilities
@chandrajob365 if you have a rooted android device available you might want to install SnoopSnitch to detect if this happens to you
Mikael Sand
@msand
a similar threat vector applies to the DNS system, as it's UDP based and uses the first response which looks correct, so any device on the network/wifi/isp can spoof responses, telling you that the ip of your banks domain is their ip, and give DNSSEC records telling you to expect their public key when connecting, enabling simple man-in-the-middle attacks, this can be circumvented by using DNSCrypto and DNS servers supporting DNSSEC themselves, such that you know that you're communicating with the DNS server you expect, and that the DNS response records have not been tampered with while in transport. Essentially just install something like https://simplednscrypt.org/ choose one or two DNS servers to trust and tell others to do the same
Manish Chandra
@chandrajob365
I have made a chat app with socket.io .
Scenario- Now need to store messages into localStorage of browser , when disconnect event is emited and fetch / sync that storage once user reconnects.
Issue - But problem is that if I am emiting some event from inside of "disconnect" handler back to client and there on client side inside handler for this event localStorage.setItem('msgText', msg). Its not saving to local storage.
Any suggestion is most appreciated on this ?
nponeccop
@nponeccop
Hi all. I'm going to revive 0.4.x as per #619
nponeccop
@nponeccop
Hi @/all socketstream/socketstream#620 is at release candidate stage, so I suggest everyone to test it by npm install git+https://github.com/nponeccop/socketstream.git#hotfix-0.4.6. ss-coffeewas patched too: npm install git+https://github.com/nponeccop/ss-coffee.git#hotfix-0.4.6