Update 3:
Nice little command line monitoring thing set up :)

Update 2:
Second update, second terrible quality gif!
Keyboard controls working over a web server!
Also there's loads less latency now since I'm using websockets :)

The IT head of my Client's company : You need to explain me what exactly you are doing in the backend and how the IOT devices are connected to the server. And the security protocol too.

Me : But it's already there in the design documents.

IT Head : I know, but I need more details as I need to give a presentation.

Me : (That's the point! You want me to be your teacher!) Okay. I will try.

IT Head : You have to.

Me : (Fuck you) Well, there are four separate servers - cache, db, socket and web. Each of the servers can be configured in a distributed way. You can put some load balancers and connect multiple servers of the same type to a particular load balancer. The database and cache servers need to replicated. The socket and http servers will subscribe to the cache server's updates. The IOT devices will be connected to the socket server via SSL and will publish the updates to a particular topic. The socket server will update the cache server and the http servers which are subscribed to that channel will receive the update notification. Then http server will forward the data to the web portals via web socket. The websockets will also work on SSL to provide security. The cache server also updates the database after a fixed interval.

This is how it works.

IT Head : Can you please give the presentation?

Me : (Fuck you asshole! Now die thinking about this architecture) Nope. I am really busy.

Managed a 97% reduction in bandwidth usage for our internal host monitoring tool by converting the dashboard from using AJAX polling to websocket events.

Completely unnecessary but wanted an excuse to do some development with websockets. (:

That moment when you work the whole day to write a discord bot from scratch. No discord.py and other wrappers. Pure websockets, oauth2, https, json loads here and there. Understanding how the discord API works was a real challenge, but I did it :).
Most of my time was spent on discord's gateway connection and identification system.

The bot can renew its token, get all the guilds it is part of, all the channels and users of these guilds, send message and communicate with the gateway.

Tomorrow I will start connecting it to a voice channel and let it "speak". Thinking of combining text-to-speech with it, but I am not sure how well they are going to harmonize together.

Built the rough verson of my whatsap notification listener with websockets and now to intergrate it into a chrome. Extension time for chrome.

And they said i wont be able to view my whatsap messages at work

I wrote an application to demo at a convention coming up. Which feeds tcp data from arduino devices to real time d3 maps via websockets.

Demoing today, and the owner starts talking about a project he saw that which lit up some lights to a device in the room via the internet. In this same meeting he casually mentions he wish he had developers who could do that type of stuff.

The disconnect is massive and soul breaking.

So here I am reinventing the wheel making an HTTP server in C.
Finished implementing HTTP/1.1 and WebSockets support and now I find out the current thingy is HTTP/2.
Well that's fine, I'll add support for that later. In fact I kinda dig it since it uses binary conventions instead of plain text ones.
I dig a little bit and find out there already is an HTTP/3 going around which uses UDP.
Why me.

i'm writing a custom web server for a project (esp32 based)

each 4 connections system crashes (cannot bind socket anymore)

i was so angry with espressif thinking that was their fault (bad implementation of posix sockets)
but is mine...

today i did another code review and I just discovered that i missed a fucking close() in the websockets handler
fuck
fuck
i wasted a month on this issue.

A made a realtime collaborative fireworks webapp ;) Happy 4th of July! It uses websockets on a Node.js server.

I'm a web dev who decided to take a shot at mobile development (My first mobile app mind you). I'm writing a mobile app and one of it's features is communicating to my server via websockets.

So I write the code, click to send the data and my server doesn't receive it. Fuck. I check why. I log everything. Nothing.
I spend several of hours and I'm exhausted by this point so i call one of our mobile developers to help me. Turns out my emulator didn't have a WiFi module. FUCK.

Alright so I compile it to an apk and install it on my phone. I popped open a terminal and started my local node server.

I click on the mobile app...

NOTHING LOGS. FUUUUUUCK.

And this is the best part.
Apparently I deleted the console.dir call from my server that executed when it received some data from an emitter.

I only thought of this last night at 2am so I got up and checked. Yep. Kill me.

(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:

Blazor is the next Silverlight.

It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.

Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:

1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML

Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.

If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.

Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:

gRPC

For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.

The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.

And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.

Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.

Seems like the push notification system in the DevRant app now uses websockets. Awesome!

Created a Service for drawing online. Just as a canvas test. My friends seem to like it. :D

It's a WebSocket based system, I hate that node module but it works.

Don't know why but web sockets are such a turn on for me when I code :D
#NeedToBeSocial

Sorry, need to vent.

In my current project I'm using two main libraries [slack client and k8s client], both official. And they both suck!

Okay, okay, their code doesn't really suck [apart from k8s severely violating Liskov's principle!]. The sucky part is not really their fault. It's the commonly used 3rd-party library that's fucked up.

Okhttp3

yeah yeah, here come all the booos. Let them all out.

1. In websockets it hard-caps frame size to 16mb w/o an ability to change it. So.. Forget about unchunked file transfers there... What's even worse - they close the websocket if the frame size exceeds that limit. Yep, instead of failing to send it kills the conn.

2. In websockets they are writing data completely async. Without any control handles.. No clue when the write starts, completes or fails. No callbacks, no promises, no nothing other feedback
3. In http requests they are splitting my request into multiple buffers. This fucks up the slack cluent, as I cannot post messages over 4050 chars in size . Thanks to the okhttp these long texts get split into multiple messages. Which effectively fucks up formatting [bold, italic, codeblocks, links,...], as the formatted blocks get torn apart. [didn't investigate this deeper: it's friday evening and it's kotlin, not java, so I saved myself from the trouble of parsing yet unknown syntax]

yes, okhttp is probably a good library for the most of it. Yes, people like it, but hell, these corner cases and weird design decisions drive me mad!

And it's not like I could swap it with anynother lib.. I don't depend on it -- other libs I need do!

I have been keeping this inside for long time and I need to rant it somewhere and hear your opinion.

So I'm working as a Team Lead Developer at a small company remotely based in Netherlands, I've been working there for about 8 years now and I am the only developer left, so the company basically consists of me and the owner of the company which is also the project manager.

As my role title says I am responsible for many things, I maintain multiple environments:
- Maintain Web Version of the App
- Maintain A Cordova app for Android, iOS and Windows
- Working with pure JavaScript (ES5..) and CSS
- Development and maintenance of Cordova Plugins for the project in Java/Swift
- Trying to keep things stable while trying very hard to transit ancient code to new standards
- Testing, Testing, Testing
- Keeping App Stable without a single Testing Unit (sadly yes..)
- Just pure JavaScript no framework apart from JQuery and Bootstrap for which I strongly insist to be removed and its being slowly done.

On the backend side I maintain:
- A Symfony project
- MySQL
- RabbitMQ
- AWS
- FCM
- Stripe/In-App Purchases
- Other things I can't disclose

I can't disclose the nature of the app but the app is quite rich in features and complex its limited to certain regions only but so far we have around 100K monthly users on all platforms, it involves too much work especially because I am the only developer there so when I am implementing some feature on one side I also have to think about the other side so I need to constantly switch between different languages and environments when working, not to mention I have to maintain a very old code and the Project Owner doesn't want to transit to some more modern technologies as that would be expensive.

The last raise I had was 3 years ago, and so far he hasn't invested in anything to improve my development process, as an example we have an iOS version of the app in Cordova which of course involves building , testing, working on both frontend and native side and etc., and I am working in a somewhat slow virtual machine of Monterey with just 16 GB of RAM which consumed days of my free time just to get it working and when I'm running it I need to close other apps, keep in mind I am working there for about 8 years.

The last time I needed to reconfigure my work computer and setup the virtual machine it costed me 4 days of small unpaid holiday I had taken for Christmas, just because he doesn't have the enough money to provide me with a decent MacBook laptop. I do get that its not a large company, but still I am the only developer there its not like he needs to keep paying 10 Developers.

Also:
- I don't get paid vacation
- I don't have paid holiday
- I don't have paid sick days
- My Monthly salary is 2000 euro GROSS (before taxes) which hourly translates to 12 Euro per hour
- I have to pay taxes by myself
- Working remotely has its own expenses: food, heating, electricity, internet and etc.
- There are few other technical stuff I am responsible of which I can't disclose in this post.

I don't know if I'm overacting and asking a lot, but summarizing everything the only expense he has regarding me is the 2000 euro he sends me on which of course he doesn't need to pay taxes as I'm doing that in my country.

Apart from that just in case I spend my free time in keeping myself updated with other tech which I would say I fairly experienced with like: Flutter/Dart, ES6, NodeJS, Express, GraphQL, MongoDB, WebSockets, ReactJS, React Native just to name few, some I know better than the other and still I feel like I don't get what I deserve.

What do you think, do I ask a lot or should I start searching for other job?

Hi Guys,

Has anyone used websockets in their projects?

Want to know what problem did it solved and what kind of project it was ?

Ugh. Challenges. I need to create a 3D two player online game with the new HTML5 WebSockets, and I'm using a free 000webhost server which I barely have control over. Does anyone know how to connect two client connections together in PHP?

I hate javascript and all the shitty frameworks it has.

Background: I'm coming from Ruby on Rails world. Ruby is a nice short language built primarily for developer's happiness.

I recently started working on a meteor.js project. Oh boy that framework is terrible. Do I even have to start from all the dependencies failing to install because npm is shit, installs everything locally and only recently discovered lock files?
Fetching a post and its author from the database looks like a fucking space rocket compared to Rails' ActiveRecord fetching.

Meteor.js fetching:
```
Meteor.publishComposite('posts.all', {
find() {
return Posts.find(); },
children: [{
find(post) {
return Users.find({ _id: post.authorId });
}
}]
});
```

Rails ActiveRecord fetching:
```
Post.includes(:authors)
```

Sure, you might get more benefits like meteor uses websockets and it's all a single language, but that piece of the code above that I have to deal with all the time now...it gives me cancer.

Alrighty. So websockets don't like to forward through Apache2's reverse proxy. Nginx here we come...

Linuxxx I need yo help pls

Honestly i only started making a multiplayer game because i wanted to make websockets in scala

cors, really don't have time to fuck around today

I would like to call out the moron who decided to control docker through HTTP when the maximum time the server can take to finish the task is longer than the HTTP timeout.
If you expect things might time out, you don't use a HTTP request. You use a resource and poll it, or Websockets, or possibly SSE.
Shoehorning your API into a frame that obviously doesn't fit doesn't help anyone. Just admit that you don't know what HTTP is and use a regular TCP socket with regular pings.

I had to choose a subject for a math project. So I selected encryption (elliptic curve). I decided to make an interactive demo website. First time working with node, websockets, large numbers and latex. Most fun project I ever did. I am still proud on the result and how fast I did it (~3 weeks)

I need a framework that does http and websockets for C++. I have seen many that offer a crap load of stuff like widgets, Json, templates... I only need the protocols!

Do you guys have any experience in this?

So I was reverse proxying this new Social network app's API and saw an interesting endpoint

It was a websocket relaying what each live user's doing every 2.5s, to power the "xyz typing" under a post, or a simple online/idle.
The app's "live posts" ie most-recently created posts was also powered by it since they knew each user's state (instead of a periodic API call)

The performance is good even tho it's a new company + enough users

but now im curious how prevelant state-management is using such websockets .-.

if not taxing, i might move any API call which ive to ping every 15s or less to a live WS

Network code is hard. Events come all the time and it's really difficult to account for all orderings and uncanny timings. Have you got any advice, book or paper about it that I should read?
I'm using node and websockets btw.

HOLY FUCK I never thought that using async websockets in Django 3.x will be THAT much pain in the ass...
Also my next contribution will be their docs for sure, the examples are so fucking bad (linters are crying and begging me to kill them)

Does anyone know why websockets aren't used far and wide for APIs? I mean not like chat applications, but the typical webapp, say an online shop. For me it seems kinda wasteful to fire separate requests with tiny payloads all the time. I currently use moleculer and socketio for a quite big project with multiple websites and backend containers, and so far, i haven't found a disadvantage.
So what have i missed?

CGI is fun, websockets are fun, why on earth is it so fucking hard to have both of them with proper switching using at most one extra program apart from my handlers?
By proper switching I mean that you actually track connections and upgrade headers to decide what to do, rather than forcing websocket connections onto a separate HTTP resource just to tell the difference.

Can't remember the last time I've been so happy about something I've made :D in my smarthome project, state is synchronized between devices with websockets, and everything can be configured via Json files :)

Can I just say, fuck app wrappers.

Why? Well let me tell you the story of cordova.

My plan was to make a leaderboard kind of thing for the tablesoccer we do at the place I'm interning at.

How it would work:
app -> create game -> API -> live feed
Buttons (flic) -> API
API -> RTU -> live feed

They use Symfony internally and externally, so that was my first go to.

I couldn't find any way to do Symfony that can do RTU without running another service.

As they really want an app but it's not their core domain I looked around for options for wrappers and decided to put RTU on the backburner.

Setting up cordova was slightly annoying but was okay. I got to building the base app.

Then I thought, maybe let's get RTU working with cordova. Looked at the options that were available. Decided to check out socketio since it had an tutorial for cordova. Tried it and it didn't work. Went over the whole internet but nobody seems to have a solution that works (the most recent post being 2017)

So I thought, let's get websockets to work instead, but again. Seems like O just can't get it to work.

So, guess what I'm going to do?
AJAX ever 1 second to the API.

Why the hell does RTU have to be so hard cordova. You are the only open source wrapper that's both multiplatform and easy to set up. Why can't you just work...

I might just call it quits on the app and just make a mobile friendly website instead.. Where socketio and websockets just work. As does SSE..

I'm tired, so sorry for the rambling I hope somebody can make sense of this mess.

I don't have any experience with cloud providers and I need to get a server for a project.
The website will be up for 3 weeks, access will probably be very uneven, the total user count is somewhat below 2000.
The site will probably be quite interactive and real-time, content may be changing every few seconds for an hour and then remain unchanged for days. I will also need either SSE or websockets for this reason.
What should I consider when selecting a cloud providers? Do you have a good one? My ideal provider would scale resources according to traffic like I've heard AWS does, but I want to hear your opinion first especially considering I know very little about how server load works.

Alright, here we go again with issues on Vector. (My home server that we're transitioning our website, infiniit.co to.)

I'm trying to get the email server up and running. It's a PITA which is evident by the fact we are now on attempt number 6, at least on the 6th VM now. At this time I'm installing a Ubuntu 16.04 LTS ISO and I'll be installing IRedMail unless someone else has any recommendations. So far I've had nothing but problems doing it manually, installing dovecot and postfix, trying to get them linked, and then the last failure was sending a test email locally.

Also, a continuation of the last issue that I had here, now my VMRC isn't working anymore for some reason. Ive forwarded websockets but it won't work unless I use local IP since everything (except direct local IP connections) is running through an apache VHost setup... My head hurts. Help pls.

Working with friend and using nodejs websockets and SVG to build online multiplayer lazer screen arcade like games.

The only delay is having to stop every couple of minutes to restate how cool this is.

Started learning python async with curio and trio just two days ago, and I must say I'm really having a blast.
I have a few pending ideas to combine it with websockets (also first time I'm learning how to use them).
Haven't had this much fun with python in a while!

Also, sidequestion: how can return a value from an async function with curio or trio? I can't find a proper answer or example about that, other than some hints about memory channels in trio

So any fellow Socket.io dev here know how to reduce the delay of my app? When I send an event it sometimes takes like 10 seconds to send the data to the server then to 2 other clients using io.sockets.emit. I'm on LAN where the server and the sender client is connected with a switch then the receiver is on wifi which is connected to the same switch so it's not far away.

Anyways it uses WEBSOCKETS so it should be fast right???!?! Is windows keeping my packets back? (poor packets :( they just wanna arrive :( )

Not a rant. Request suggestions.

I am developing a Sublime Text plugin for real-time code monitoring ( screencasting) using Websockets. I would like to know if it makes any sense to develop such a plugin. Also, please suggest some use cases so that I can increase the features of the plugin. Point out if it already exists. Thanks :)

>new feature in application uses external API
>external API has unreliable response times, requires polling to get results, no way to set up webhooks or whatever
>tech lead proposes asynchronous system which will queue up user requests for processing and use websockets to warn frontend clients of finished query results
>higher ups say it will take too much time, make tech lead cut back in scale and treat external API like a regular synchronous REST API
>team dutifully implements feature within the constraints of the new smaller scope
>higher ups try out the feature, find the usage experience is extremely shitty, but don't back down, they only let tech lead scale back to original scope in small increments that still allow new problems to show up
>feature takes up same time or longer, but with more damage to the mental health of developers

At least I'm not in that team

Looking for WebSockets... when this explanation appears

...or just Forever Frame in IE because... because it is IE

"Never use websockets when HTTP you can use" -- Mark Twain, or some shit

Would it be possible to use (S)FTP protocol in conjunction with push technology rather than pull? Perhaps websockets since both use TCP?

Say, something like an external server periodically sending my server files and when a new file arrives, I will get a notification. This instead of constantly polling my directory to check if there are files in it.

I think I can see this done with an Angular page that gives me a notification when a new file arrives on my FTP.

I think it might turn into an interesting little hobby project..

To the Backend Ninjas out here.
Ive written rest APIs before but know I'm asking myself how I would implement user messaging for my app.?

Use Rest and poll the server?

Use websockets and keep the connection to the server?

Or is there something that I don't know?

Man I'm getting old Everyday there are thousands of new things....

Wasted an hour or two on that...
After changing the library I used, was trying to test that my Java WebSocket client was reconnecting as I intended upon losing connection.
Me : Why are you making the rest of the app bug you stupid fucker? The old one was doing fine!
WS : ...
Changes code, looks on SO a bit.. Gets despaired.

Then it struck..
The "rest of the app" was connected to a sensor.. On the network.. From which I disconnected to mimic a loss of connection...
😭😢😂😂😂👌

open plain TCP socket with javascript in browser, websockets are stupid

Question.
I have a java app to monitor and send aprox every 3seconds a json with data to a client who will present it on a single fancy display, there will not be other clients ever, only this single one. Shall I go websockets and push the data, and wait for it there or shall I go rest and ask for the data every 3 seconds? Im planning to use node on the client regardless of the solution. ?

Yesterday. Mean stack exam tomorrow. Only study for the websocket question. Go to the exam. Teacher says pick a question. Folded paper with questions on table. One is not neatly folded, so can see through. Says websockets. Pick question. Forget half the stuff about http protocols. Still got a B. :D

Now, time for coffee.

Has anyone developed websocket server in Nodejs?

I am planning to use socketcluster. Has anyone had experience using it? Is it good or should I go for something else?

I am free, I am free of the bull, of working with tools that don't have websockets, I am free

Okay, I hope a few people can help me with this; what are the benefits/reasons to use MS technologies? I'm talking about .NET, ASP, Windows Server, Powershell...

I've never understood it. I love Nodejs because you don't have any packages unless you ask for them. Alpine Linux is amazing! It runs on 8MB of RAM from fresh and doesn't need much more space to install.

You want .NET core? 140MB download. You're configuring database connection strings? Feel free to type in whatever you like, it'll parse and replace with some magic variables that have come from some other random file.

I was using Powershell recently, needed to set an env variable. Bash is happy with "export name=value". You want to do that in Powershell? I just googled it and found an entire 40-minute read discussing how to set env vars. Why?! It should be one command, and I don't know who thought that "Get-ChildItem" was _obviously_ referring to env variables.

It seems to me that everywhere MS has got their hands on development-wise, it inherits the typical sales bullshit. No no, you can't call them "websockets", they have to be branded "SignalR" and add tons of overhead. You can't say "disable notifications" it has to be "focus assist". I'm really surprised something as simple as a keyboard hasn't become a "varied user input device" or something of the like.

Am I alone in thinking this?

i want to deploy websockets on multiple servers with horizontal scaling. i don't know what to use. redis pub/sub? haproxy? i wanna know your opinions. ❤️

Okay people couldn't get a response anywhere so I'm going to do this here considering we have a bunch of geniuses here. I need to create a tunnel in nodejs or java to forward connection from client to server. Need to do this because my damn client can only use ports 80/443. Anybody wants to brainstorm?
These people have so much of garbage data yet want to keep everything secure as hell.

[Help|advice needed]
Can anyone tell me how to realtime sync data in android?
The backend is nodeJS and I've read about using FCM woth sync adapters. Can I use websockets for this?

Baeldung.com has the just worst guide to Java Spring Websockets. They even mix up endpoints and show just the wrong code.