Blërg, a microblogging platform • Hacker News Board

Re: Blërg, a microblogging platform

#61

Post by cambalache » Mon, Jan 11, 2021, 7:28 PM UTC

skrebbel wrote: post #52

cambalache wrote: post #44

Unnecessary "complicated" name? Check! Butt-ugly interface? Check! Mentioning the technology used to build it as it were a feature? Check! So a typical tool created by a developer who thinks the average guy think and act like them.

I can't figure out what made you decide to post this to HN. The author of this app has obviously been having a great time. Why the sour grapes? What are you so mad about?

Not mad at all, just describing what it is a common occurrence with these type of tools, you (well, not you) can take the criticism in the right way and change things to gain more users(which I suppose is the goal here) or you can get defensive and artificially place extra beliefs on the other person to assuage your discomfort. Life is always about choices.

Re: Blërg, a microblogging platform

#62

Post by bytex64 » Mon, Jan 11, 2021, 7:37 PM UTC

Hey guys! Glad (and a little panicked) to see this get some more attention. I've shut down signups/logins because I don't have time to moderate, and right now you really have to moderate. :|

So long and thanks for all the barfs. :)

Re: Blërg, a microblogging platform

#63

Post by monsieurbanana » Tue, Jan 12, 2021, 9:59 AM UTC

pathtracer wrote: post #16

doix wrote: post #10

Earlier quoted context omitted.

> Goldman Sachs does a lot of work in erlang but mostly to limit turnover on the dev side - try getting a job if all you have on your resume is years of working with a language nobody else uses, you can do it but it’s going to take a lot more effort on your part. My take on that is slightly different. Choosing a fairly esoteric language as a company reduces the amount of effort it takes to review applicants. Right no…

> Post a job advert for erlang, you'll get significantly less applicants because there are fewer erlang programmers. In general I would agree with you, but does that work everywhere? I could see how that works in some tech focused locations like Silicon Valley. But if I would try to hire Erlang developers around here I would not find a single one. Unless of course I would hire remotely and try to compete with SV comp…

> and try to compete with SV company salaries

That assumes that everyone that is worth hiring is already in SV or somewhere else with a similar salary.

Re: Blërg, a microblogging platform

#64

Post by f6v » Wed, Jan 13, 2021, 1:04 PM UTC

tsukurimashou wrote: post #34

nickdonnelly wrote: post #30

Earlier quoted context omitted.

You likely need to delete your service workers for Twitter and let it re-create them.

That's pretty unacceptable considering the size of the userbase, most of them probably never heard of service workers

I’ve been in software development for almost 10 years and I had no idea about service workers.

Re: Blërg, a microblogging platform

#65

Post by nickdonnelly » Thu, Jan 14, 2021, 10:04 PM UTC

f6v wrote: post #64

tsukurimashou wrote: post #34

Earlier quoted context omitted.

That's pretty unacceptable considering the size of the userbase, most of them probably never heard of service workers

I’ve been in software development for almost 10 years and I had no idea about service workers.

I believe this fix only applies if you have an old version of their service workers. I remember reading some esoteric nonsense about why it's the case. I agree with the user you replied to, it's absolutely absurd that doing this is the "fix."

Re: Blërg, a microblogging platform

#66

Post by jimis » Sat, Jan 16, 2021, 10:08 AM UTC

bytex64 wrote: post #62

Hey guys! Glad (and a little panicked) to see this get some more attention. I've shut down signups/logins because I don't have time to moderate, and right now you really have to moderate. :| So long and thanks for all the barfs. :)

Awesome to see you answering here! It's obvious that your little experiment has had the honour to be hammered many times by thousands of people, so I'm curious to hear your experience.

Has it been running on a single node all these times? What are the hardware specs? How many requests per second did it handle? Has it gone down because of the load? What was the bottleneck (network, cpu io)? How did it fail (crash, slowness, fire ;-)? Do you have monitoring data to show? How many twitter-like active users would it be able to serve from that single node?

Thanks, and Blërg! :-)