We service retail online, via marketplaces (new) and b2b to shops around the world

Crowdfunding Video Demo We’ve been hard at work building Boost, our crowdfunding platform. In this week’s update, we show a preview of the platform in action. Every user of our app can use Boost to raise funds for any project. In the demo video, the user first navigates to a crowdfunding section of the app, and then enters information about the crowdfunding event like duration, funding goal, and background information. This information is then stored to the testnet blockchain. Afterward, the crowdfunding event is viewable in the projects feed. We’ve set the app to automatically approve all projects for Alpha testing. Below we show a video demo of Boost in action: Crowdfunding Smart Contracts We’re continuing to build out various testing scenarios for our crowdfunding smart contracts. At this time, all crowdfunding scenarios run as expected. We’ll continue to test these rigorously over the next week. We’ve also already completed a draft of the documentation for our upcoming crowdfunding smart contract demo. This will allow other developers to test and interact with the crowdfunding smart contract. 1Protcol.com This week, David met with one of the founders of in San Francisco. 1Protocol has created smart contracts allowing users with idle cryptocurrencies to stake them and earn interest. The platform was founded by Stanford dropouts Axel Ericsson and Zackary Lawrence. For a detailed description of their platform, see their white paper . One example use case for their platform is Ether staking in the upcoming Casper upgrade. Using smart contracts, 1Protocol enables users to put idle value to use by creating “Virtual Workers” which link “Capitalists” (those staking currency) to “Operators” (those with idle computing power). Their smart contracts are generalized and can handle Ether and any Ethereum token, and they’re also developing an intuitive front end interface called 1Client to interact with their smart contracts. 1Protocol here Incorporating 1Protocol would be as easy as adding a button to stake idle ELIX and earn interest on our wallet page, and linking our app to their platform via a few function calls. We believe this could be another way to reduce the circulating supply of ELIX while allowing ELIX holders to earn interest. According to one of the founders, they already have strong interest in their platform from owners of cryptocurrencies who don’t wish to cash out their holdings. We anticipate their platform providing a service that if incorporated could further motivate people to use our app. We’re still exploring their platform and conducting further research, and will definitely be testing their Alpha in the next few months and seeing if there’s a fit for a partnership. Expansion We’re currently in discussions with , a software consulting firm cofounded by one of our contacts. AE would provide consulting engineers, product managers, designers, and any other product development resources necessary. We’d be working closely with them on our product. This has the added advantage of gaining help and insight from a experienced with building and deploying great products. Over the next few weeks, we’re discussing the details, and if we choose to use AE we may start with several weeks of contracting work — testing and altering our smart contracts — and then move from there. AE.Studio team We’ve also had the opportunity to speak to several other engineers and one possible intern. We believe in the past week we’ve made significant progress in finding the people and resources to get our product to the next stage. Updated Whitepaper Our new white paper has just been added to our website! Check it out . We’ve been working hard to incorporate the community’s feedback and provide an updated version of our company vision with in-depth discussion of technical aspects. Please provide your feedback on our social channels about the new white paper — we’d love to know what you think. here App UI Redesign We’re currently discussing the possibility of having our previous designer also design our final App UI. We were proud of the new website design, and would like our app to have a similar sleek look. We’ll let the community know when we make a final decision regarding this. We’re also talking to several different designers at this time to allow us to choose from as many options as possible. New Facebook Page We now have a Facebook page! Check it out at facebook.com/elixirtoken Follow and like the page to receive updates from ELIX in your newsfeed. Please help spread the word on Facebook about the platform by sharing the page or inviting friends to like it. New Instagram Page We also have an official Instagram page now. You can follow for updates and Instagram posts regarding ELIX. @elixtoken Sign Up For The Upcoming Newsletter We’ve enabled the Newsletter feature on our website! If you’d like to receive occasional email regarding development of the ELIX platform, you can provide an email in the sign up field at the bottom of the home page. We’ll keep the emails concise and important, and your email will never be shared with others on the list. Be sure to checkout our as well as connect to our social media on , , , and . If you have any questions, let us know and we’d be glad to help clear things up! website Reddit Twitter Discord Telegram

Crowdfunding App Demo, Team Expansion, 1Protocol and New Whitepaper

Disclaimer: I am biased in that I am sick to the back teeth of being periodically bled by software vendors who think they have a cloud service that justifies a subscription based model, you should know that before you read this. Ok I admit that I feel like an asshole for writing this, but in my defense I genuinely love and have done for years, I have it everywhere and its brilliant at its sole job, keeping my super secret 30 digit long passwords safe and reproducing them on demand across all my devices. 1password I think thats why I bothered to write this article, I love 1password so much that I am genuinely disturbed by their recent subscription money grab and also angry because its undoubtedly going to mean that I have to find a new password manager rather than pay regular subscriptions until I die. After many years of faithful service, the good people at 1Password decided that they were not seeing enough return on their investment and some bright spark suggested a , what can go wrong they said. subscription model This is where the wheels started to come off. Its All Adobe‘s Fault Who can blame them? After Adobe so dramatically boosted their short, mid and long term profits in the face of fierce customer pushback by doing exactly the same thing, they are now sitting pretty with that sweet sticky recurring revenue stream, despite boosting the fortunes of their immediate competitors and angering their most loyal fans in the process. The lesson that Adobe taught the software vending world is that the subscription model pays, even if it costs you loyal customers on the road to increased profits and strengthens your competitors in ways that are so subtle over the long term that short term profiteers cannot grasp them. Lets be honest here, any business worth their salt would charge their customers periodically forever, rather than once in return for something tangible with each transaction. Everybody loves recurring revenue, your investors love it, your accountant loves it, your bankers are masturbating over it and this my friends is the real reason a software vendor decided to start charging your credit card indefinitely, not because asked for it. you Subscription based models work really well for specific kinds of technology service, the key word being . Typically when a real IT service is provided, say by a cloud MSP (managed service provider) serving cloud desktops, servers and VOIP to their customers, the customer knows that if they tried to deliver the same service themselves, the monthly costs can be dangerously unpredictable, its why they go to the cloud in the first place. service My point is that when you deliver real cloud hosted solutions and when I say real, I means ones that are complex enough to require tech support and have lots of moving parts, the subscription model makes a lot of sense. It fixes your CAPEX and OPEX in a predictable way and that folks is where the subscription model magic really happens, it removes financial uncertainty. Then you have the Adobes of the world holding a piece of software that has been sold on a perpetual license basis for ever, suddenly deciding to sell pretty much the same thing but on a recurring revenue model. Adobe barely support their software, hardly any of their users ever need tech support to use their software and if they do Adobe is the last group of people they would ask for help with a whole ecosystem full of Adobe training resources freely or privately available on the internet. Even worse, their software barely changes and they have mostly the same core functionality they built their hegemony on a decade ago, I have no idea where they pulled those 500 extra features out of, but this is what happens when a software vendors needs to justify a subscription, you see software bloat and a drift from core functionality towards bells and whistles. 500 new features? WTF! Adobe knew they had hegemony (not quite but almost) over the professional graphic design market and they leveraged that dominant position into a truly massive base of subscribers and killed all the pirates that were plaguing them at the same time, two birds with one stone. For sure they alienated a large number of creatives in the process, but their shareholders were not complaining and why would they, profits massively increased, piracy plummeted and they survived the trauma without any real long term scarring on the core business. They the leap. survived I salute Adobe, they did an amazing job of converting their base to a subscription model, but lets be honest here, they aren't delivering anything that needs to be cloud hosted for any other reason than more money. I was using Dreamweaver, Photoshop and Illustrator locally installed on a perpetual license model happily for a decade before they tried to stiff me, but now I use and and have never looked back. Pixelmator Coda Adobe are not real cloud solution providers who provide a real cloud hosted technology solution, one backed up by real technical support and lots of unknown support variables that mean a subscription model makes sense to customers rather than just the shareholders of the company. Nope, Adobe are quite literally monopolist shysters who drank too much of that recurring revenue subscription liquor and got drunk on it and somehow they didn’t crash their car along the way. Ask any graphic designer over the age of 3o how they feel about it. They definitely will. Of course the rest of the software vending world witnesses this and thought “ ” and who can blame them, who wouldnt want to be richer than they are, which brings us nicely back to the title of this article. why not me too To Catch a Liar: 1Password Edition Now, the more technically aware amongst us know all about the arguments for a subscription based model, we have heard them so many times before as each and every last remaining software vendor peddles them in a desperate attempt to boost their margins at the expense of their loyal customers. We have all heard the song before and it goes a little something like this: More features, cloud syncing across all devices, more features, ongoing technical support you never use, more features that have not yet been disclosed. If you are really lucky you will also hear some variation of: Software companies need recurring rvenues to survive these days, in order to keep updating and actively developing your software we need a subscription. Or that gem: Don’t you want your vendors to be healthy and stable financially? Its total nonsense of course and conveniently forgets that they first built their business on the back of perpetual licensing and that for most of the history of the software space, companies have survived and propspered quite happily with the old perpetual license model. Its how Bill Gates became the richest man in the world in fact, so don’t swallow this nonsense and buy into it, software vendors dont need recurring revenue to survive, they need to in order to survive. sell product We also are probably not going to need the new features that they are now forced to invent in order to justify their subscription, usually this totally ruins good products, when what we actually need is a stable piece of software that does what it says on the tin instead of fantasy features. YOU asked for it! In the absence of anything tangible, like total market dominance, a real product update that is obviously better than the previous iteration or actual technical support, fun marketing and new features are all that remain. Well said Kenn. Lets be clear about what we need, what we actually bought from 1password. We want our passwords encrypted at rest until we need them and we want those passwords reliably synched across devices, its that simple. If you are like me, you probably have 300 passwords in your vault. If you are like me, most of those records consist of three fields, a username, a password, a URL to the login box and are completely text based records. Lets assume that each record is worth 25 characters each, with one character equalling one byte. That would make my entire database (if you can even call it a database) weigh in at 7500 bytes of data. Nothing in other words, less data than my address book. But that doesn't stop them wanting to charge you three dollars a month forever for the privilege of hosting that tiny amount of data and thats just the price they launched their subscription with, that price will steadily rise over time as they test their customers willingness to pay in increments. 1passwords only job is to synch password data across devices and store minute quantities of data in the process, such a small amount of data that until now they did not think it worth putting in the cloud. Before they let you store your password vault on Dropbox or iCloud, something that up until now they thought their customers could handle technically themselves, but now they have decided its to set up and be a cloud service. too technically complicated for most users must They of course are about the whole thing, its why they and keep saying “ ” instead of “we will not do this”, it leaves the door open to those plans changing at a later date without them having to lie. being shady talk about roadmaps for the future not being fixed we have no plans to do this The problem they have is that we all smell a big fat lie in their story, one so obvious that they disgraced themselves trying it on us for size. The story I am hearing from 1password is that they even though they just introduced a new subscription model, it will run alongside their existing perpetual licensing model in perptuity and that amigos is the big fat lie they caught themselves in, I think because they are too timid to go all in. No business person, no investor, no banker, no accountant, no founder would operate two contrasting licensing models, recurring subscription and perpetual and use one to subsidise the other to save face for very long. Now we know. The lie that 1password have caught themselves in is the lie that they will continue to maintain both models indefinitely. Nobody is going to compare the perpetual licensing model, to the more money for less work subscription model and conclude its worth keeping both of them for ever. Adobe taught us this and the with this consensus. industry seems to agree They can deny it as much as they like but we all know which way this road goes, they made it clear when they the month before they launched their subscription service. blatantly jumped up their perpetual license prices So I made a prediciton. I predicted that 1password would drop their perpetual license and local vault model in the face of recurring revenue within 24 months or less and I comfortably stand by that prediction. It is my belief that after a decade spent making very good software that does exactly what it says on the tin, the founders of this company decided to juice up revenues in a big way, probably as a precursor to a sale of the company. The only reason they wont go there is if enough of their users push back, but the problem there is that Adobe taught us that in the face of sweet recurring revenue. no matter how many of us push back, nobody cares Indeed we shall. The 1password team is timidly dipping their toe in right now, hence the two contradictory licensing models sat side my side for the moment, at least until has enough confidence in his new revenue stream to cut the cord and admit where they are going with this over the long term. Dave Teare Say what you like about Adobe, they and convert everyone to the subscription model at the same time, . had the balls to go all in criticism be damned This is a public service announcement and represents my personal opinion. ** UPDATE ** Say what you like about Dave, he is a gentleman for sure and he earned my respect with this comment in response to this article and as a long term 1password fan, I sincerely hope he makes me eat my words. What’s that? You like the cut of my jib? Follow me on Twitter then and give me a CLAP using the clap button, you can clap more than once :)

To Catch A Liar : @1Password Edition

Password Management and Protection - Part 1: The Basics

By now, most of us are accustomed to using CSS Custom Properties on projects. Since its introduction in 2017, CSS Custom Properties, also known as CSS variables, have optimised the code we work with and allowed engineers a finer degree of control when managing values within rules. CSS Custom Properties can be tricky to deal with and aren’t always as intuitive as one might hope. However, when used right, they can significantly reduce boilerplate code and keep things efficient, making our work more productive. While the approach below is not perfect, it works well when writing CSS for building projects. Why Use CSS Custom Properties As far as my experience goes, I can only think of three possible reasons to implement a CSS Variable: We want to use a given value in more than one place,


We know that a value will change in the future and want to reduce our efforts for refactoring,


We need to store dynamic values from JS execution. With this in mind, we can be more assertive about our use cases. Point 3 is less of a concern for this article, but points 1 and 2 are essential. Let's illustrate this using the familiar HTML button element. The Infamous Button Buttons are notoriously tricky to style consistently for such a simple HTML element. Perhaps it’s because they have several different states and applications, regardless - it's usually the first component we Frontend Engineers take on when it comes to a fresh build. Let's have a look at how we could write the style for a button using CSS Custom Properties: :root {
 --color-primary: purple;
 --color-text: black;
 --color-text-inverted: white;
 --color-border: gray;
}

.button {
 --button-bg: var(--color-primary);
 --button-color: var(--color-text-inverted);
 --button-border: var(--color-border);

 align-items: center;
 background-color: var(--button-bg);
 border: 1px solid var(--button-border);
 color: var(--button-color);
 display: inline-flex;
 line-height: 1;
} As far as this example goes, from a technical standpoint, it’s great. It’s clean and straightforward and would get a 👍 from me in a code review. But could we optimise it further? Well, yes. The var() function in CSS is pretty nifty…we’re used to using it in a somewhat one-dimensional way by just rendering out a value; however, it can be more dynamic. The way to do this is by using a fallback value. If we considered the above example, we could rewrite it like so: :root {
 --color-primary: purple;
 --color-text: black;
 --color-text-inverted: white;
 --color-border: gray;
}

.button {
  align-items: center;
  background-color: var(--button-bg, var(--color-primary));
  border: 2px solid var(--button-border, var(--color-border));
  color: var(--button-color, var(--color-text-inverted));
  cursor: pointer;
  display: inline-flex;
  line-height: 1;
  padding-block: 0.875rem;
  padding-inline: 1rem;
} This is far cleaner and will lead to the same outcomes as the previous example - with less boilerplate code. Overriding it in a variation makes each locally scoped CSS Variable (effectively) optional. We can easily now optionally define the variables defined in .button as separate variations: .button:where(.button-secondary) {
  --button-bg: orange;
  --button-border: teal;
}

.button:where(.button-tertiary) {
  --button-bg: teal;
  --button-border: orange;
} Although this technique is not revolutionary, we care how many lines of compressed text are heading over the wire. The less physical memory a CSS file takes up, the better, which ultimately translates to how many lines of CSS exist. In the first example, we’re looking at almost double the amount of code to achieve the same thing in our optimised example. This compound effect has an influential impact on performance and further improves readability and developer experience. If you'd like to play around a bit further, feel free to fork the following Code Pen: https://codepen.io/iamdainemawer/pen/NWmQZMz Support Since April 2017, according to Google Baseline, this feature is well-supported across all major browsers. If you're interested to learn more about Baseline, read my post about Google Baseline and Its Impact You can check for browser support by adding the following statement to your CSS stylesheets: @supports(--css: variable) {} Can I Use - CSS Nesting
CSS Specification - CSS Nesting Module Resources MDN - CSS Custom Properties
CSS Variables Polyfill By now, most of us are accustomed to using CSS Custom Properties on projects. Since its introduction in 2017, CSS Custom Properties, also known as CSS variables, have optimised the code we work with and allowed engineers a finer degree of control when managing values within rules. CSS Custom Properties can be tricky to deal with and aren’t always as intuitive as one might hope. However, when used right, they can significantly reduce boilerplate code and keep things efficient, making our work more productive. While the approach below is not perfect, it works well when writing CSS for building projects. Why Use CSS Custom Properties As far as my experience goes, I can only think of three possible reasons to implement a CSS Variable: We want to use a given value in more than one place, We know that a value will change in the future and want to reduce our efforts for refactoring, We need to store dynamic values from JS execution. We want to use a given value in more than one place, We want to use a given value in more than one place, We know that a value will change in the future and want to reduce our efforts for refactoring, We know that a value will change in the future and want to reduce our efforts for refactoring, We need to store dynamic values from JS execution. We need to store dynamic values from JS execution. With this in mind, we can be more assertive about our use cases. Point 3 is less of a concern for this article, but points 1 and 2 are essential. Let's illustrate this using the familiar HTML button element. The Infamous Button Buttons are notoriously tricky to style consistently for such a simple HTML element. Perhaps it’s because they have several different states and applications, regardless - it's usually the first component we Frontend Engineers take on when it comes to a fresh build. Let's have a look at how we could write the style for a button using CSS Custom Properties: :root {
 --color-primary: purple;
 --color-text: black;
 --color-text-inverted: white;
 --color-border: gray;
}

.button {
 --button-bg: var(--color-primary);
 --button-color: var(--color-text-inverted);
 --button-border: var(--color-border);

 align-items: center;
 background-color: var(--button-bg);
 border: 1px solid var(--button-border);
 color: var(--button-color);
 display: inline-flex;
 line-height: 1;
} :root {
 --color-primary: purple;
 --color-text: black;
 --color-text-inverted: white;
 --color-border: gray;
}

.button {
 --button-bg: var(--color-primary);
 --button-color: var(--color-text-inverted);
 --button-border: var(--color-border);

 align-items: center;
 background-color: var(--button-bg);
 border: 1px solid var(--button-border);
 color: var(--button-color);
 display: inline-flex;
 line-height: 1;
} As far as this example goes, from a technical standpoint, it’s great. It’s clean and straightforward and would get a 👍 from me in a code review. But could we optimise it further? Well, yes. The var() function in CSS is pretty nifty…we’re used to using it in a somewhat one-dimensional way by just rendering out a value; however, it can be more dynamic. The way to do this is by using a fallback value . var() fallback value If we considered the above example, we could rewrite it like so: :root {
 --color-primary: purple;
 --color-text: black;
 --color-text-inverted: white;
 --color-border: gray;
}

.button {
  align-items: center;
  background-color: var(--button-bg, var(--color-primary));
  border: 2px solid var(--button-border, var(--color-border));
  color: var(--button-color, var(--color-text-inverted));
  cursor: pointer;
  display: inline-flex;
  line-height: 1;
  padding-block: 0.875rem;
  padding-inline: 1rem;
} :root {
 --color-primary: purple;
 --color-text: black;
 --color-text-inverted: white;
 --color-border: gray;
}

.button {
  align-items: center;
  background-color: var(--button-bg, var(--color-primary));
  border: 2px solid var(--button-border, var(--color-border));
  color: var(--button-color, var(--color-text-inverted));
  cursor: pointer;
  display: inline-flex;
  line-height: 1;
  padding-block: 0.875rem;
  padding-inline: 1rem;
} This is far cleaner and will lead to the same outcomes as the previous example - with less boilerplate code. Overriding it in a variation makes each locally scoped CSS Variable (effectively) optional. We can easily now optionally define the variables defined in .button as separate variations: .button:where(.button-secondary) {
  --button-bg: orange;
  --button-border: teal;
}

.button:where(.button-tertiary) {
  --button-bg: teal;
  --button-border: orange;
} .button:where(.button-secondary) {
  --button-bg: orange;
  --button-border: teal;
}

.button:where(.button-tertiary) {
  --button-bg: teal;
  --button-border: orange;
} Although this technique is not revolutionary, we care how many lines of compressed text are heading over the wire. The less physical memory a CSS file takes up, the better, which ultimately translates to how many lines of CSS exist. In the first example, we’re looking at almost double the amount of code to achieve the same thing in our optimised example. This compound effect has an influential impact on performance and further improves readability and developer experience. If you'd like to play around a bit further, feel free to fork the following Code Pen: https://codepen.io/iamdainemawer/pen/NWmQZMz https://codepen.io/iamdainemawer/pen/NWmQZMz Support Since April 2017, according to Google Baseline , this feature is well-supported across all major browsers. If you're interested to learn more about Baseline, read my post about Google Baseline and Its Impact Google Baseline Google Baseline and Its Impact You can check for browser support by adding the following statement to your CSS stylesheets: @supports(--css: variable) {} @supports(--css: variable) {} Can I Use - CSS Nesting CSS Specification - CSS Nesting Module Can I Use - CSS Nesting Can I Use - CSS Nesting CSS Specification - CSS Nesting Module CSS Specification - CSS Nesting Module Resources MDN - CSS Custom Properties CSS Variables Polyfill MDN - CSS Custom Properties MDN - CSS Custom Properties CSS Variables Polyfill CSS Variables Polyfill

Using CSS Custom Properties To Optimize Styling Efficiency and Readability

Design Systems: A Front-End Engineer's Guide to Efficient Atomic Design

This Javascript Code Generates Random Quotes

এই জাভাস্ক্রিপ্ট কোড এলোমেলো উদ্ধৃতি তৈরি করে

Dieser Javascript-Code generiert zufällige Zitate

Este código Javascript genera citas aleatorias

Ce code Javascript génère des citations aléatoires

यह जावास्क्रिप्ट कोड यादृच्छिक उद्धरण उत्पन्न करता है

このJavascriptコードはランダムな引用を生成します

이 자바스크립트 코드는 무작위 인용문을 생성합니다

Este código Javascript gera citações aleatórias

Этот код Javascript генерирует случайные цитаты

Bu Javascript Kodu Rastgele Alıntılar Oluşturuyor

Mã Javascript này tạo ra các trích dẫn ngẫu nhiên

这段 JavaScript 代码可生成随机引号

How to Create a Blog using Golang

This is a redacted version of the by CEO David Smooke and COO Linh Smooke sent to 1.3k shareholders. Picture: HackerNoon Team in an All-Hands Meeting. HackerNoon shareholders' newsletter TL;DR Revenue is slightly down, traffic is slightly up, rate of product development is up, expenses are down, and AI is assisting us but is not replacing us anytime soon 🙂 How can you help? Referral, referral, referral: we recently experimented with a Business Blogging Sales Referral Program for a 12 or 52-credit pack. If you think you can help refer customers to publish their announcements, blog posts, or technical documentation with HackerNoon, we are more than happy to share the details of the Referral Program with you! Here are some high-level updates since our last shareholder letter, which was . We keep this update succinct, with lots of links sprinkled throughout, as we’ve actually written a throughout the year. sent on June 19, 2023 lot of mini-updates Read the full Blog Post below for full context. 📈 Traffic & Editorial in the Age of AI 📈 HackerNoon Readership & Traffic HackerNoon readership and traffic remain stronger than ever: 2023 (especially the latter half) was a great year for traffic. With for different types of and , simpler micro-engagement mechanisms for users ( , , ), we published 18,659 stories (compared to 13k in 2022), and on-boarded 29k new writers (compared to 22k in 2022). I think this is a huge testament to our human-first (we are documenting our protocol at , which is powered by the HackerNoon CMS). In a world where content is inundated by AI, HackerNoon remains one of the few places on the internet with , , and . simpler sign-up flows users actions open commenting for all published writers polls voting & commenting history for readers easy-peezy templates for aspiring writers editorial protocol EditingProtocol.com a Second Human Rule an AI & Plagiarism Detector 2-way communications between editors & writers Even more encouragingly, we continue to ride this tailwind into 2024 as well: Here’s a list of the top-performing HackerNoon stories/pages in 2023: Niche: by Programming 14 Patterns to Ace Any Coding Interview Question Fahim ul Haq Niche: , by , translated to 7 different languages, including Spanish Cybersecurity Cómo hackear cuentas de Facebook: 5 vulnerabilidades comunes original English version Jessica Truong Niche: by Media The Tom Holland Spider-Man Movies in Order of Release Date Jose Hernandez Niche: by Futurism Apple CarPlay Not Working [SOLVED] How to Fix Common Issues Khunshan Ahmad Niche: , published by Web3 How to Implement a Merkle Tree in Solidity Daniel Shvetsov ! HackerNoon Search And here’s a list of top performing HackerNoon stories/pages YTD in 2024: Niche: 任天堂、パルワールドで沈黙を破る, by , translated into 12 languages, including Japanese Gaming original English version Player Auctions Niche: by Programming How to Read Text File in Python? Srinivas Ramakrishna Niche: , published by Machine Learning Open-Source: The Next Step in AI Revolution MinIO Niche: , published by Product Management To Focus or Not Focus: How to Find the Right Product-Market Fit Denis Pushkin Niche: , published by Tech Companies Apple Customers Return Vision Pro By The Droves Allan Grain page! Why Publish on HackerNoon We’ve continued to scale up audiences via niche newsletter growth. Notably, which is an editor-written weekly commentary on our , has now passed 100 editions and 45k+ subscribers. Additionally, the 22 niche technology newsletters (one for each new category) have been growing steadily and now total 280k+ subscribers. In total, we send well over half a million emails a day (!) The Tech Company Brief, proprietary tech company ranking data AHREFs, the top SEO software, . This is a testament to building up our internet presence over the years, publishing more quality stories day after day and year after year, and the rest of the internet’s willingness to cite and talk about HackerNoon stories. For reference, here are some similarly ranked domains that historically carry much higher valuations, many of which are also community-driven technology education destinations: , , , , , , , , , , , and . Here’s a screenshot from 2/29/24: ranks HackerNoon.com as the 2,750th most valuable domain worldwide Kaggle at 2,802 Heroku at 2,824 Google Earth at 2,861 Delaware at 2,870 NextJS at 2,880 GQ at 2,881 Brown at 2,834 Seeking Alpha at 2,844 Hotels at 2,907 Snap at 2,993 Cal Tech at 2,999 1Password at 3,011 Since we started HackerNoon, we’ve outlived many tech sites and products that we’ve (mostly) admired: , , , , , , , , , , , , , , , , , , , , , , , , , , and of course, . We don’t take joy in these (mostly) impactful businesses dying, but it is a reminder that HackerNoon keeps on blogging. Vice Artifact Protocol Future Apple EV InVision The Messenger, IRL (lol) Meta Portal Buzzfeed News Anki Google+ Microsoft’s Mixer Recur, HouseParty Essential The Outline Bodega Loon LG Phones Nuzzel Mandolin Fast Argo AI, Kite Kitty Hawk Udayy Blackberry (again), Telltale Games Revue Quibi 💰 Revenue & Business Development Net Income 📉amist & in tech & media bear markets mass layoffs Both revenue and expenses are down in 2023 YoY. We made in revenue in 2023, and spent about - a slight dip compared to 2022. Our net income remains level; however, we have some catching up to do in 2024. Our 2024 revenue projection is , and expenses project to be in 2024. We are determined to be profitable again in 2024, 2025, and beyond. redacted redacted redacted redacted Business Blogging We’ve fine-tuned our to include better returns for customers and better margins for HackerNoon. We built a , raised the prices per post and improved the performance per premium post by adding , , , and better customer service. In 2023, we onboarded 609 new businesses and published 1,624 , averaging a net income of /story (compared to 2022 net income of /story). Business Blogging self-service flow to request a business blogging trial 12 language translations multi-voice audio file creation managed paid social promotion good company stories redacted redacted Encouragingly, so far in 2024, we’ve made about half of our revenue in , surpassing both and . Not only is this good because content is at the heart of our business value prop, but also because this is a true unlimited inventory, independent of past or future traffic, we can always publish another blog post. Business Blogging Niche Ads Writing Contests Additionally, we’ve seen an increased demand to publish press releases from wire services, with customers such as , , , and . We’re building a custom technology press release solution that includes distribution across traditional press release sites in addition to business blogging’s default, social, audio, multi-lingual, email, and on-site distribution. ChainWire FinanceWire GamingWire BTCWire Business Database Scale Up with and Startups of the Year Evergreen Tech Company News Pages Startups of the Year 2023 concluded with ! The winners and nominees were excited, you can see a taste of their enthusiasm on , , and . Our evergreen news pages are up to covered (ranking S&P 500, public companies, and startups alike). Companies with a regular to an Evergreen Premium with more control over their internet presence. Our is also hosted on ( & ) and ! over 623k votes, 30k startups, and 1k+ winners Twitter/X J) LinkedIn around the web 12k+ total companies Evergreen Page can claim, edit and also upgrade their page unique dataset curating the news about these companies Hugging Face their CEO CTO commented reused by MongoDB Vertical Category Curation Diversifies Streams of Income We curated our entire library of 100k+ stories and into . This divides the library into 22 starting points, like , / , / , to name a few. Advertisers now buy entire categories to ensure across our site. We made combined in Niche Ads & Billboard ads in 2023, compared to the total in Billboard alone in 2022. That means each pageview on the page is worth 11% more! 50k tags 22 categories /ai cloud business content-relevant ad placements redacted redacted HR, Payroll Reduction, “trimming the fats” Both David & Linh have taken a payroll reduction in 2023 by 50%, and we will continue to cut our salaries significantly in 2024 until the company gets back on track. We’ve also reduced our staff by half. HackerNoon started 2023 with 40 staff members and started 2024 with only 20. Experiments with new inventories in 2023 and beyond We introduced with our European partner, . We learned in 2022 & 2023 that convert more advertisers & long-term business partners than our regular top-nav billboard ads. HackerNoon’s Job Board Jobbio targeted, niched and relevant ads We also launched the ! This is proof of concept for a docu-series on the future of the internet. It costs $2.99 and is a great way to spend 30 minutes of your time while supporting HackerNoon. HackerNoon Documentary In 2024, we are thoughtfully looking into programmatic ads to capitalize on our stable, quality traffic more efficiently. 🚀 Infrastructure Overhaul & Product Development HackerNoon 3.0 The great refactoring. As a platform that makes software completely in-house, we get to choose . Starting mid-2023, we’ve decided to migrate our backend database from Firestore/Google to Mongodb, our frontend tech from Vercel premium to a combination of Vercel/Svelkit, and our email host from Sendgrid to Elastic. Removing Firestore greatly reduces the number of reads we pay for, and removing SendGrid greatly reduces the cost per email sent.  Not only will these refactorings make HackerNoon lighter, simpler, and more efficient, but they will also help reduce our cost of production by an estimated 25-35%. which technology companies to partner with ( , ) HackerNoon Mobile App Apple Google Our mobile app officially and has gone through 9 iterations already since September 2023! We were briefly the in the US, Vietnam, Brazil, and Ukraine during launch month. (version ), users can , , , and any story to HackerNoon. And we added 12 additional languages to read our prime library of technology stories. This update is a commitment to helping technologists to not only more easily create content but also to reach and serve worldwide readers from their mobile devices. launched top 100 apps With the latest version 1.9 read write listen submit More mobile app release notes. Niche Technology Publication Network powered by the HackerNoon CMS (beta) In just a few clicks, a HackerNoon account can turn into a standalone site. This year, we are building a 500+ owned network of sites via the HackerNoon CMS with a focus on curating and distributing the world’s highest-quality open-source content. HackerNoon sites are now going live every week. Some WIP examples include: , , , , , , , , , , , , , , , , , , , , , , , and more coming soon! LearnRepo.com Memeology.tech HackerNoon.tech EditingProtocol.com Escholar.tech TextModels.tech Blog.DavidSmooke.Net HackerNoon.LinhDaoSmooke.com PublicDomain.tech LegalPDF.tech OpenDatasets.tech Roasts.tech CompanyBrief.tech StoryTemplates.tech SupportNoon.com UnknownAuthor.tech Noonion.tech HackerEvents.tech DearElon.tech Blog.Slogging.com CoinWikis.com Noonification.com HistoricalEmails.com Beautiful Landing Pages powered by the HackerNoon CMS We also started to host many pages in-house using our own page-builder as opposed to using 3rd party CMS like Squarespace, Wix, or Strikingly. Examples of some of these in-house landing pages using our own page builder Include: , , ( ,  # , # , # ), , , ( , , ), & . HackerNoon Mobile App Web 2.5 Why Publish Pages Content Startups AI Programming About Page Slogging.com Testimonial Pages Writers Customers Readers Writing Contests Technological Integration In order to make the content management system that powers HackerNoon best in class, we can’t build everything ourselves. Some of the recent notable CMS integrations include: We integrate a lot of best-in-class solutions and technologies. for all published writers. Username.HackerNoon namespaces minted on the blockchain via namespace.gg . AI-written submissions have gone through the roof, but unlike other blogging platforms, we do not blindly publish AI-created content. This cat-and-mouse game will continue to evolve! Originality.ai and other tools for AI Writing Detection (for those visitors currently logged into Google). This one is averaging about 850 new accounts per day 😀 Signup/Signin with Google for easier account creation and login and . This type of content portability increases our rate of publishing. Importing of text transcripts from Youtube Importing of full blog posts from RSS and other blogging platforms to make the site more fun. Added GIPHY to story editing and commenting New search discovery experience and renewed partnership with Algolia Yet another year of our mutually beneficial partnership (we pay them via in-kind ads!) Algolia helps beautifully index and discover our content, while we surface their Ad on & . our search page search bar Steering into the internet’s pixelated ethos and using open source design as an adoption channel are the 1,440 original icons used on HackerNoon, and now they are open sourced and available on , and as This builds on our open source release of the , which is up to Use of our icons and fonts in other sites and apps are subtle endorsements of HackerNoon’s way of publishing, and our network of owned CMS sites will scale up this usage. The Pixel Icon Library GitHub Figma (1.6k users), an NPMjs package. 2.0 version of the HackerNoon font 3k downloads on DaFont. Helping Technologists to Market Themselves HackerNoon and expertise in the technology industry. In addition to (links to your portfolio, newsletter, jobs, or wherever), , and , we now also empower users to and (shipped this week, ). validates contributions entering Call to Actions updating your social media profiles filling out your short and long-form bios flaunt their work and job history rank top writers by technology categories it has writers very excited 💁 How can you help? we recently experimented with a Business Blogging Sales Referral Program for (base value of $4,788 and $15,548 respectively). If you think you can help refer customers to publish their announcements, blog posts, or technical documentation with HackerNoon, we are more than happy to share the details of the Referral Program with you! Referral, referral, referral: a 12 or 52-credit pack Kind Regards, CEO and COO , David Smooke Linh Dao Smooke HackerNoon If seeking more regular updates from HackerNoon, I recommend subscribing to the , , and/or . P.S. #hackernoon-product tag hackernoon.tech the #hackernoon tag Here are some recent news coverage about HackerNoon around the web: P.P.S. , #2 Blogging Platform for Developers by Perplexity AI ( Meeting with Vietnamese Prime Minister Pham Minh Chinh full remarks) , Yale Entrepreneurship Mentor Series , Best AI/ML Blog for Community Engagement by Hosting Advice ( ), AI Time Journal CEO Interview with contextual links ( ), Web3 Founder Interview with contextual links , Financial Interview with Vietcetera , KingsCrowd Empowering Technologists Interview , SuperbCrew Startups Interview , HustleFund Interview about Startup Storytelling , Our Favorite Tweet/Posts on Twitter/X , #14 Crypto Media Source by StealthEx , Stratechery Sharp Tech Podcast Mention , Recommended Tech Blog for Engineers , Unchained Podcast Mention , ROIquant Conference Fireside Chat , #6 AI Blog to Follow by Analytics Insights , #7 Blog for Product Management , Professor Rymel Adding HackerNoon to Her Curriculum , Top Startup Resource by Faster Capital , Top Crypto Blog by Crypto Economy , Must Follow Tech Blog by Xpheno , #3 Programming Blog by Blogging Idol , #6 Layperson-Friendly Resources For Tech News by Forbes : , , . And Testimonials Readers Writers and Businesses

State of the Noonion 2024: HackerNoon Keeps on Blogging

নুনিয়ন 2024 এর অবস্থা: হ্যাকারনুন ব্লগিং চালিয়ে যায়

Stand der Noonion 2024: HackerNoon bloggt weiter

Estado del mediodía 2024: HackerNoon sigue blogueando

State of the Noonion 2024 : HackerNoon continue de bloguer

नूनियन 2024 की स्थिति: हैकरनून ब्लॉगिंग जारी रखता है

2024 年の正午の様子: HackerNoon はブログを書き続ける

2024년 정오 현황: HackerNoon이 계속 블로깅을 하고 있습니다.

State of the Noonion 2024: HackerNoon continua blogando

Состояние полудня 2024 года: HackerNoon продолжает вести блог

Öğlen Durumu 2024: HackerNoon Bloglamaya Devam Ediyor

Trạng thái buổi trưa 2024: HackerNoon tiếp tục viết blog

2024 年 Noonion 状态：HackerNoon 继续写博客

1P

1p.workable.com

-- employees

Since n.d.

COMPANY RANKING

1P

EVERGREEN INDEX #1232

Representing this company? Click here to claim and customize this page!

1P WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

1P