7 items tagged “linkedin”
2024
“Link In Bio” is a slow knife (via) Anil Dash writing in 2019 about how Instagram’s “link in bio” thing (where users cannot post links to things in Instagram posts or comments, just a single link field in their bio) is harmful for linking on the web.
Today it’s even worse. TikTok has the same culture, and LinkedIn and Twitter both algorithmically de-boost anything with a URL in it, encouraging users to share screenshots (often unsourced) rather than linking to content and reducing their distribution.
It’s gross.
2018
The current linkedin.com homepage clocks in at 1.9MB of CSS (156KB compressed). After re-building a fully-functional version of the homepage with CSS Blocks, we were able to serve the same page with just 38KB of CSS. To be clear: that's the uncompressed size. After compression, that CSS file weighed in at less than 9KB!
2014
What is the best way one can expand his or her professional network?
Go to events—local meetups, conferences, tradeshows... there’s no better way of expanding your professional network than to attend events and build in-person relationships with people.
[... 46 words]Why was LinkedIn Events shut down? Why isn’t there now a social network for business events?
Our site Lanyrd offers LinkedIn signin and works as a social network for business and professional events. You can read more about our LinkedIn integration here: Use Lanyrd and LinkedIn to get more out of professional events and conferences
[... 62 words]2012
How does Linkedin use Node.js?
They use it for the backed for their mobile app. Here’s an article with more information: http://venturebeat.com/2011/08/1...
[... 29 words]2011
What are some good social media events that will take place in 2011 in Middle East and North Africa region?
User StartupDigestME on Lanyrd follows entrepreneurship events in the region which may also cover social media topics: http://lanyrd.com/people/startup...
[... 45 words]2009
Project Voldemort. Yet Another “big, distributed, persistent, fault-tolerant hash table”—this time from LinkedIn, released under the Apache 2.0 license. The approach to consistency is interesting—instead of using distributed transactions, they use versioning and “resolve inconsistencies at read time”. It also uses consistent hashing (as seen in libketama) to select servers. The design document has lots more information.