Ownwell helps property owners reduce the costs of owning real estate. Our proprietary software automatically identifies property owners that are overpaying on real estate expenses. We then manage the end-to-end process of reducing bills through tax appeals, exemptions, and corrections. Over $40 billion is overpaid in property taxes every year, and inaccurate tax assessments disproportionately affect people of color, immigrants, as well as low-income communities. We’re dedicated to making the costs of property ownership more transparent and equitable. We believe that regardless of status or level of real estate expertise, everyone should have the information, tools, and resources to manage their real estate confidently. Ownwell is a well-funded venture-backed company growing 300% year-over-year, and we are dedicated to helping change the way everyday homeowners manage their real estate across the country.

Ownwell

How to Find Out If You're Paying for Slow Internet

Mission Generation Using Classic Machine Learning and Recurrent Neural Networks in Zombie State

জম্বি রাজ্যে ক্লাসিক মেশিন লার্নিং এবং পুনরাবৃত্ত নিউরাল নেটওয়ার্ক ব্যবহার করে মিশন জেনারেশন

Missionsgenerierung mit klassischem maschinellem Lernen und rekurrierenden neuronalen Netzwerken im Zombie-Zustand

Generación de misiones utilizando aprendizaje automático clásico y redes neuronales recurrentes en estado zombie

Génération de mission à l'aide de l'apprentissage automatique classique et des réseaux de neurones récurrents dans un état zombie

ज़ोंबी स्टेट में क्लासिक मशीन लर्निंग और रीकरंट न्यूरल नेटवर्क का उपयोग करके मिशन जनरेशन

ゾンビ状態での古典的な機械学習とリカレントニューラルネットワークを使用したミッション生成

좀비 상태에서 고전적인 기계 학습과 순환 신경망을 사용한 미션 생성

Geração de missão usando aprendizado de máquina clássico e redes neurais recorrentes no estado zumbi

Генерация миссий с использованием классического машинного обучения и рекуррентных нейронных сетей в состоянии зомби

Zombie State'te Klasik Makine Öğrenimi ve Tekrarlayan Sinir Ağlarını Kullanarak Görev Oluşturma

Tạo nhiệm vụ bằng cách sử dụng mạng lưới thần kinh định kỳ và học máy cổ điển ở trạng thái Zombie

在僵尸状态下使用经典机器学习和循环神经网络生成任务

"We will migrate to TypeScript, and then..." – how often do you hear this phrase? Perhaps, if you mainly work within a single project or mostly just start new projects from scratch, this is a relatively rare expression for you to hear. For me, as someone working in an outsourcing company, who, in addition to my main project, sees dozens of various other projects every month, it is quite a common phrase from the development team or a client who would like to upgrade their project stack for easier team collaboration. Spoiler alert: it is probably not going to be as soon of a transition as you think (most likely, ). soon never While it may sound drastic, cases, this will indeed be the case. Most people who have not undergone such a transition may not be aware of the dozens of nuances that can arise during a project migration to TypeScript. For instance, are you prepared for the possibility that your project build, which took in pure JavaScript, might suddenly start taking when using TypeScript? Of course, it depends on your project's size, your pipeline configuration, etc., but these scenarios are not fabricated. You, as a developer, might be prepared for this inevitability, but what will your client think when you tell them that the budget for the server instance needs to be increased because the project build is now failing due to a heap out-of-memory error after adding TypeScript to the project? Yes, TypeScript, like any other tool, is not free. in most tens of seconds tens of minutes On the Internet, you can find a large number of articles about how leading companies successfully migrated their projects from pure to TypeScript. While they usually describe a lot of the issues they had during the transition and how they overcame them, there are still many unspoken obstacles that people can encounter, which can become critical to their migration. JavaScript Despite the awareness among most teams that adding typing to their projects through migration to TypeScript might not proceed as smoothly as depicted in various articles, they still consider TypeScript as the to address typing issues in their projects. This mindset can result in projects remaining in pure JavaScript for extended periods, and the eagerly anticipated typing remains confined to the realm of dreams. While alternative tools for introducing typing to JavaScript code do exist, TypeScript's overwhelming popularity often casts them into the shadows. This widespread acclaim, justified by the TypeScript team's active development, may, however, prove disadvantageous to developers. Developers tend to lean towards the perception that TypeScript is the solution to typing challenges in a project, neglecting other options. exclusive and definitive solution only Next, we will consider JSDoc as a tool that, when used correctly and understood in conjunction with other tools (like TypeScript), can help address the typing issue in a project . Many might think that the functionality of JSDoc pales in comparison to TypeScript, and comparing them is unfair. To some extent, that is true, but on the other hand, it depends on the perspective. Each technology has its pros and cons, counterbalancing the other. virtually for free Code examples will illustrate a kind of from TypeScript to JavaScript while maintaining typing functionality. While for some, this might appear as a form of . Again, it all depends on how you look at it… graceful degradation progressive enhancement JSDoc and Its Extensions is a specification for the comment format in JavaScript. This specification allows developers to describe the structure of their code, data types, function parameters, and much more using special comments. These comments can then be transformed into documentation using appropriate tools. JSDoc /**
 * Adds two numbers.
 * @param {number} a - The first number.
 * @param {number} b - The second number.
 * @returns {number} The sum of the two numbers.
 */
const getSum = (a, b) => {
  return a + b
} Initially, JSDoc was created with the goal of generating documentation based on comments, and this functionality remains a significant part of the tool. However, it is not the only aspect. The second substantial aspect of the tool is the description of various types within the program: variable types, object types, function parameters, and many other structures. Since the fate of was uncertain, and many developers lacked (and still lack to this day) proper typing, JSDoc started adding this much-needed typing to JavaScript. This contributed to its popularity, and as a result, many other tools began to rely on the JSDoc syntax. ECMAScript 4 An interesting fact is that while the JSDoc documentation provides a list of basic tags, the specification itself allows developers to expand the list based on their needs. Tools built on top of JSDoc leverage this flexibility to the maximum by adding their own custom tags. Therefore, encountering a JSDoc setup is a relatively rare occurrence. pure The most well-known tools that rely on JSDoc are (not to be confused with the Closure programming language) and . Both of these tools can help make your JavaScript , but they approach it differently. Closure Compiler primarily focuses on your files by adding typing through JSDoc annotations (after all, they are just ), while TypeScript is designed for files, introducing its own well-known TypeScript constructs such as , , , , and so on. Closure Compiler TypeScript typed enhancing .js comments .ts type interface enum namespace Not from its inception, but starting from , TypeScript began allowing something similar to Closure Compiler – checking type annotations in files based on the use of JSDoc syntax. With this version, and with each subsequent version, TypeScript not only added support for JSDoc but also incorporated present in the Closure Compiler. This made migration to TypeScript more straightforward. While Closure Compiler is still being updated, used by some teams, and in JavaScript (if its rules are followed), due to support for checking files and various other updates brought by the TypeScript team, . version 2.3 .js many of the core tags and constructs remains the most effective tool for code compression .js Closure Compiler eventually lost to TypeScript From the implementation perspective, incorporating an understanding of JSDoc notation into TypeScript is not a fundamental change. Whether it is TypeScript types or JSDoc types, ultimately, they both become part of the AST (Abstract Syntax Tree) of the executed program. This is convenient for us as developers because all our everyday tools, such as ESLint (including all its plugins), Prettier, and others, primarily rely on the AST. Therefore, regardless of the file extensions we use, our favorite plugins can continue to work in both and files (with some exceptions, of course). .js .ts Developer Experience When adding typing to JavaScript code using JSDoc, it is advisable to use additional tools that enhance the development experience. is a JSDoc plugin for ESLint. This plugin reports errors in case of invalid JSDoc syntax usage and helps standardize the written JSDoc. An important setting for this plugin is the option, which offers one of the following values: , (referring to Closure Compiler), or . As mentioned earlier, JSDoc can vary, and this option allows you to specify which JSDoc tags and syntax to use. The default value is (though this has not always been the case), which, given TypeScript's dominance over other tools that work with JSDoc, seems like a sensible choice. eslint-plugin-jsdoc mode typescript closure jsdoc typescript It is also important to choose a tool for analyzing the type annotations written in JSDoc, and in this case, it will be . This might sound strange because, in this article, it seems like we are discussing its replacement. However, we are not using TypeScript for its purpose – our files still have the extension. We will only use TypeScript as a type-checking linter. In most projects where TypeScript is used , there is typically a script responsible for compiling files into . In the case of using TypeScript as a linting tool, instead of a command handling compilation, you will have a command for linting your types. TypeScript primary .js fully build .ts .js build // package.json

{
  "scripts": {
	   "lint:type": "tsc --noEmit"
  }
} If, in the future, a tool emerges that TypeScript as a linting tool for project typing, we can always replace it in this script. surpasses To make this script work correctly, you need to create a file in your project or add additional parameters to this script. These parameters include and , which allow TypeScript to check code written in files. In addition to these parameters, you can enable many others. For example, to make type checking stricter, you can use , , , , and more. TypeScript will rigorously check your code even if you are using files. tsconfig.json allowJs checkJs .js strict noUncheckedIndexedAccess exactOptionalPropertyTypes noPropertyAccessFromIndexSignature .js The TypeScript team consistently enhances the functionality of TypeScript when working with JSDoc. With almost every release, they introduce both fixes and new features. The same applies to code editors. Syntax highlighting and other DX features provided by TypeScript when working with files also work when dealing with files using JSDoc. Although there are occasional instances where support for certain JSDoc features may come later, many GitHub issues labeled with JSDoc in the TypeScript backlog indicate that the TypeScript team continues to work on improving JSDoc support. .ts .js Many might mention the nuance that when using TypeScript solely for files, you are deprived of the ability to use additional constructs provided by TypeScript. For example: , , , , , and others, as their syntax are only available in files with the extension. .js Enums Namespaces Class Parameter Properties Abstract Classes and Members Experimental (!) Decorators .ts Again, for some, this may seem like a drawback, but for others, it could be considered a benefit, as most of these constructs have their drawbacks. Primarily, during TypeScript compilation to JavaScript, anything related to types . In the case of using the aforementioned constructs, all of them are into less-than-optimal JavaScript code. If this does not sound compelling enough for you to refrain from using them, you can explore the downsides of each of these constructs on your own, as there are plenty of articles on the Internet discussing these issues. simply disappears translated Overall, the use of these constructs is generally considered an anti-pattern. On most of my projects where I use TypeScript to its full extent (with all my code residing in files), I always use a custom ESLint rule: .ts // eslint.config.js

/** @type {import('eslint').Linter.FlatConfig} */
const config = {
  rules: {
    'no-restricted-syntax': [
      'error',
      {
        selector: 'TSEnumDeclaration,TSModuleDeclaration,TSParameterProperty,ClassDeclaration[abstract=true],Decorator',
        message: 'TypeScript shit is forbidden.',
      },
    ],
  },
} This rule prohibits the use of TypeScript constructs that raise concerns. When considering what remains of TypeScript when applying this ESLint rule, essentially, only the aspect remains. In this context, when using this rule, leveraging for adding typing to files is almost indistinguishable from using TypeScript with files. typing JSDoc tags and syntax provided by TypeScript .js .ts As mentioned earlier, most tools rely on AST for their operations, including TypeScript. TypeScript does not care whether you define types using TypeScript's keywords and syntax or JSDoc tags supported by TypeScript. This principle also applies to ESLint and its plugins, including the plugin. This means that we can use this plugin and its powerful rules to check typing even if the entire code is written in files (provided you enabled the ). typescript-eslint .js appropriate parser Unfortunately, a significant drawback when using these tools with files is that some parts of these tools, such as specific rules in typescript-eslint, rely on the use of specific TypeScript keywords. Examples of such rules include , , , and others that are tied explicitly to TypeScript keywords. Fortunately, there are not many such rules. Despite the fact that these rules could be rewritten to use AST, the development teams behind these rules are currently reluctant to do so due to the increased complexity of support when transitioning from using keywords to AST. .js explicit-function-return-type explicit-member-accessibility no-unsafe-return Conclusion JSDoc, when used alongside TypeScript as a linting tool, provides developers with a powerful means of typing files. Its functionality does not lag significantly behind TypeScript when used to its , keeping all the code in files. Utilizing JSDoc allows developers to introduce typing into a pure JavaScript project right now without delaying it as a distant dream of a full migration to TypeScript (which most likely will never happen). .js full potential .ts Many mistakenly spend too much time critiquing the JSDoc syntax, deeming it ugly, especially when compared to TypeScript. It is hard to argue otherwise; TypeScript's syntax does indeed look much more concise. However, what is truly a mistake is engaging in empty discussions about syntax instead of taking any action. In the end, you will probably want to achieve a similar result, as shown in the screenshot below. Performing such a migration is significantly easier and more feasible when transitioning from code that already has typing written in JSDoc. By the way, many who label the JSDoc syntax as ugly while using TypeScript as their sole primary tool, after such remarks, nonchalantly return to their files, fully embracing TS Enums, TS Parameter Properties, TS Experimental (!) Decorators and other TS constructs that might raise questions. Do they truly believe they are on the right side? .ts Most of the screenshots were taken from the migration of files to while preserving type functionality in my library (here is the ). Why did I decide to make this migration? Because I wanted to. Although this is far from my only experience with such migrations. Interestingly, the sides of migrations often change (migrations from to undoubtedly occur more frequently). Despite my affection for TypeScript and its concise syntax, after several dozen files written/rewritten using JSDoc, I stopped feeling any particular aversion to the JSDoc syntax, as it is . .ts .js form-payload PR .js .ts just syntax Summing up: JSDoc provides developers with real opportunities for gradually improving the codebase without requiring a complete transition to TypeScript from the start of migration. It is essential to remember that the key is not to pray to the TypeScript God but to start taking action. The ultimate transition to using TypeScript fully is possible, but you might also realize that JSDoc is more than sufficient for successful development, as it has its advantages. For example, here is what a "JSDoc-compiler" might look like: // bundler.js

await esbuild.build({
  entryPoints: [jsMainEntryPoint],
  minify: true, // 👌
}) Give it a try! Do not stand still; continually develop your project, and I am sure you will find many other benefits! Also published . here

TypeScript Might Not Be Your God: A Case Study of Using JSDoc for JavaScript Projects

MR. COHENLUPE LEAVES LONDON.

Phineas Redux by Anthony Trollope, is part of the HackerNoon Books Series. You can jump to any chapter in this book . THE MEAGER FAMILY. here THE MEAGER FAMILY. On the day after the committal a lady, who had got out of a cab at the corner of Northumberland Street, in the Marylebone Road, walked up that very uninviting street, and knocked at a door just opposite to the deadest part of the dead wall of the Marylebone Workhouse. Here lived Mrs. and Miss Meager,—and also on occasions Mr. Meager, who, however, was simply a trouble and annoyance in the world, going about to race-courses, and occasionally, perhaps, to worse places, and being of no slightest use to the two poor hard-worked women,—mother and daughter,—who endeavoured to get their living by letting lodgings. The task was difficult, for it is not everybody who likes to look out upon the dead wall of a workhouse, and they who do are disposed to think that their willingness that way should be considered in the rent. But Mr. Emilius, when the cruelty of his wife's friends deprived him of the short-lived luxury of his mansion in Lowndes Square, had found in Northumberland Street a congenial retreat, and had for a while trusted to Mrs. and Miss Meager for all his domestic comforts. Mr. Emilius was always a favourite with new friends, and had not as yet had his Northumberland Street gloss rubbed altogether off him when Mr. Bonteen was murdered. As it happened, on that night,—or rather early in the day, for Meager had returned to the bosom of his family after a somewhat prolonged absence in the provinces, and therefore the date had become specially remarkable in the Meager family from the double event,—Mr. Meager had declared that unless his wife could supply him with a five-pound note he must cut his throat instantly. His wife and daughter had regretted the necessity, but had declared the alternative to be out of the question. Whereupon Mr. Meager had endeavoured to force the lock of an old bureau with a carving-knife, and there had been some slight personal encounter,—after which he had had some gin and had gone to bed. Mrs. Meager remembered the day very well indeed, and Miss Meager, when the police came the next morning, had accounted for her black eye by a tragical account of a fall she had had against the bed-post in the dark. Up to that period Mr. Emilius had been everything that was sweet and good,—an excellent, eloquent clergyman, who was being ill-treated by his wife's wealthy relations, who was soft in his manners and civil in his words, and never gave more trouble than was necessary. The period, too, would have been one of comparative prosperity to the Meager ladies,—but for that inopportune return of the head of the family,—as two other lodgers had been inclined to look out upon the dead wall, or else into the cheerful back-yard; which circumstance came to have some bearing upon our story, as Mrs. Meager had been driven by the press of her increased household to let that good-natured Mr. Emilius know that if "he didn't mind it" the latch-key might be an accommodation on occasions. To give him his due, indeed, he had, when first taking the rooms, offered to give up the key when not intending to be out at night. After the murder Mr. Emilius had been arrested, and had been kept in durance for a week. Miss Meager had been sure that he was innocent; Mrs. Meager had trusted the policemen, who evidently thought that the clergyman was guilty. Of the policemen who were concerned on the occasion, it may be said in a general way that they believed that both the gentlemen had committed the murder,—so anxious were they not to be foiled in the attempts at discovery which their duty called upon them to make. Mr. Meager had left the house on the morning of the arrest, having arranged that little matter of the five-pound note by a compromise. When the policeman came for Mr. Emilius, Mr. Meager was gone. For a day or two the lodger's rooms were kept vacant for the clergyman till Mrs. Meager became quite convinced that he had committed the murder, and then all his things were packed up and placed in the passage. When he was liberated he returned to the house, and expressed unbounded anger at what had been done. He took his two boxes away in a cab, and was seen no more by the ladies of Northumberland Street. But a further gleam of prosperity fell upon them in consequence of the tragedy which had been so interesting to them. Hitherto the inquiries made at their house had had reference solely to the habits and doings of their lodger during the last few days; but now there came to them a visitor who made a more extended investigation; and this was one of their own sex. It was Madame Goesler who got out of the cab at the workhouse corner, and walked from thence to Mrs. Meager's house. This was her third appearance in Northumberland Street, and at each coming she had spoken kind words, and had left behind her liberal recompense for the trouble which she gave. She had no scruples as to paying for the evidence which she desired to obtain,—no fear of any questions which might afterwards be asked in cross-examination. She dealt out sovereigns—womanfully, and had had Mrs. and Miss Meager at her feet. Before the second visit was completed they were both certain that the Bohemian converted Jew had murdered Mr. Bonteen, and were quite willing to assist in hanging him. "Yes, Ma'am," said Mrs. Meager, "he did take the key with him. Amelia remembers we were a key short at the time he was away." The absence here alluded to was that occasioned by the journey which Mr. Emilius took to Prague, when he heard that evidence of his former marriage was being sought against him in his own country. "That he did," said Amelia, "because we were put out ever so. And he had no business, for he was not paying for the room." "You have only one key." "There is three, Ma'am. The front attic has one regular because he's on a daily paper, and of course he doesn't get to bed till morning. Meager always takes another, and we can't get it from him ever so." "And Mr. Emilius took the other away with him?" asked Madame Goesler. "That he did, Ma'am. When he came back he said it had been in a drawer,—but it wasn't in the drawer. We always knows what's in the drawers." "The drawer wasn't left locked, then?" "Yes, it was, Ma'am, and he took that key—unbeknownst to us," said Mrs. Meager. "But there is other keys that open the drawers. We are obliged in our line to know about the lodgers, Ma'am." This was certainly no time for Madame Goesler to express disapprobation of the practices which were thus divulged. She smiled, and nodded her head, and was quite sympathetic with Mrs. Meager. She had learned that Mr. Emilius had taken the latch-key with him to Bohemia, and was convinced that a dozen other latch-keys might have been made after the pattern without any apparent detection by the London police. "And now about the coat, Mrs. Meager." "Well, Ma'am?" "Mr. Meager has not been here since?" "No, Ma'am. Mr. Meager, Ma'am, isn't what he ought to be. I never do own it up, only when I'm driven. He hasn't been home." "I suppose he still has the coat." "Well, Ma'am, no. We sent a young man after him, as you said, and the young man found him at the Newmarket Spring." "Some water cure?" asked Madame Goesler. "No, Ma'am. It ain't a water cure, but the races. He hadn't got the coat. He does always manage a tidy great coat when November is coming on, because it covers everything, and is respectable, but he mostly parts with it in April. He gets short, and then he—just pawns it." "But he had it the night of the murder?" "Yes, Ma'am, he had. Amelia and I remembered it especial. When we went to bed, which we did soon after ten, it was left in this room, lying there on the sofa." They were now sitting in the little back parlour, in which Mrs. and Miss Meager were accustomed to live. "And it was there in the morning?" "Father had it on when he went out," said Amelia. "If we paid him he would get it out of the pawnshop, and bring it to us, would he not?" asked the lady. To this Mrs. Meager suggested that it was quite on the cards that Mr. Meager might have been able to do better with his coat by selling it, and if so, it certainly would have been sold, as no prudent idea of redeeming his garment for the next winter's wear would ever enter his mind. And Mrs. Meager seemed to think that such a sale would not have taken place between her husband and any old friend. "He wouldn't know where he sold it," said Mrs. Meager. "Anyways he'd tell us so," said Amelia. "But if we paid him to be more accurate?" said Madame Goesler. "They is so afraid of being took up themselves," said Mrs. Meager. There was, however, ample evidence that Mr. Meager had possessed a grey great coat, which during the night of the murder had been left in the little sitting-room, and which they had supposed to have lain there all night. To this coat Mr. Emilius might have had easy access. "But then it was a big man that was seen, and Emilius isn't no ways a big man. Meager's coat would be too long for him, ever so much." "Nevertheless we must try and get the coat," said Madame Goesler. "I'll speak to a friend about it. I suppose we can find your husband when we want him?" "I don't know, Ma'am. We never can find him; but then we never do want him,—not now. The police know him at the races, no doubt. You won't go and get him into trouble, Ma'am, worse than he is? He's always been in trouble, but I wouldn't like to be means of making it worse on him than it is." Madame Goesler, as she again paid the woman for her services, assured her that she would do no injury to Mr. Meager. All that she wanted of Mr. Meager was his grey coat, and that not with any view that could be detrimental either to his honour or to his safety, and she was willing to pay any reasonable price,—or almost any unreasonable price,—for the coat. But the coat must be made to be forthcoming if it were still in existence, and had not been as yet torn to pieces by the shoddy makers. "It ain't near come to that yet," said Amelia. "I don't know that I ever see father more respectable,—that is, in the way of a great coat." About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Anthony Trollope (2006). Phineas Redux. Urbana, Illinois: Project Gutenberg. Retrieved https://www.gutenberg.org/cache/epub/18640/pg18640-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

THE MEAGER FAMILY.

A LITTLE JOURNEY INTO THE WORLD

Directed Acyclic Graphs (DAGs) have emerged as a promising alternative to blockchain technology. Unlike blockchains, DAGs boast a unique structure where transactions are linked in a directed, non-circular manner, with new ways to reach consensus. This innovation promises faster transaction speeds and higher decentralization, making them an attractive choice for crypto enthusiasts. However, they could come with their own set of security challenges. There are bug bounty programs for a reason, after all. Cybercriminals will target the most vulnerable points, and that’s usually outside the DAG itself, but targeting its users anyway. However, so far, we can say that no DAG structure has been hacked. On the other hand, their related services, from social media and even smart contracts, are another story. We’ll delve ahead into some attacks involving DAG platforms, recounting five instances when their related services fell victim to hacking attempts. Besides, we’ll explore strategies and best practices to shield oneself from such threats. Whether you're a seasoned investor or a newcomer, understanding is essential to protect your digital assets in an increasingly complex crypto ecosystem. these challenges Nano + BitGrail In 2018, the cryptocurrency world witnessed a major security breach involving the Italian cryptocurrency exchange BitGrail and the digital currency Nano (formerly known as Raiblocks). This currency uses a ledger structured like a DAG (more accurately, block lattice), and its consensus system is quite similar to a Proof-of-Stake (PoS) blockchain. began when BitGrail reported a substantial amount of Nano tokens missing from its platform. The exchange's founder, Francesco Firano, claimed that the hack had resulted The incident in the theft of approximately 17 million Nano tokens, equivalent to roughly $170 million at the time. The aftermath of the BitGrail hack was marked by a contentious dispute between the exchange's management and the Nano development team. Firano initially suggested that Nano's code was responsible for the vulnerability, blaming the developers for the theft. He demanded a contentious fork (update) to be held by the Nano team (to erase the hack), which they refused. Indeed, the hack happened just in time to see a price rise in Nano, and Firano hid that the breaches had been happening since 2017. BitGrail and Firano received at least , and ultimately, Firano was found to be directly liable for the attack. More investigations later revealed that BitGrail's security measures and internal controls were inadequate, leading to the compromise of user funds. two class-action lawsuits In this case, the DAG wasn’t attacked, but the users trusted the wrong company. In centralized exchanges, you don’t have private keys to your funds. Instead, only an account with a password is provided, and the funds are in full custody (control) by that company. If they lose (hacks, bankruptcy, etc.), then you lose too. That’s why it’s important not to use exchanges as permanent wallets. IOTA + Moonpay IOTA is a cryptocurrency platform that utilizes Directed Acyclic Graph (DAG) technology to enable faster transactions, and it’s focused on the Internet of Things (IoT) sector. Unlike blockchains, IOTA's Tangle DAG allows users to validate transactions by confirming others, but there’s an ultimate coordinator node to achieve consensus. They intend (since 2016) to get rid of it, but in the meantime, the coordinator is controlled by the IOTA Foundation, and the network is centralized. That was vastly proved in February 2020, when the whole network was frozen by the coordinator after a major breach. The IOTA suffered a security breach due to a third-party dependency from Moonpay (a crypto payment service), which compromised users' wallet seeds by loading illicit versions of Moonpay's SDK from Moonpay's servers. Back then, hackers stole 8.5 million in IOTA's native token MIOTA directly from users —approximately $2 million at the time. Trinity wallet The cyber-criminal awaited a new Trinity version to overwrite cached files and eliminate traces. Immediate actions were taken by the IOTA Foundation, including halting the coordinator and creating an incident management plan with public status updates. The attack involved DNS interception, code modification, and API key misuse. IOTA responded by developing migration tools for affected users, enhancing analytical tools, and collaborating with security experts and law enforcement. Trinity isn’t used anymore, and MoonPay with them to fix the issue. So, again, it wasn’t a breached DAG but an external service related to it. collaborated Hedera Hashgraph Hedera Hashgraph is a distributed ledger system that utilizes Directed Acyclic Graphs (DAGs) for consensus. In Hedera's , nodes share new information with each other, gradually reaching a consensus through multiple rounds of sharing. This history of information-sharing events is represented as a hashgraph —a type of DAG. gossip protocol This system is patented, but it’s not error-free. On March 9, 2023, the Hedera Hashgraph network to a smart contract exploit, resulting in the theft of various tokens from decentralized exchanges (DEXs) such as Pangolin, SaucerSwap, and HeliSwap. Retail user accounts and Hedera wallets remained unaffected, but fell victim the attacker managed to steal tokens valued at nearly $600,000. They included DAI Stablecoin, Tether USD, USD Coin, and Wrapped HBAR. Swift action was taken to mitigate the attack. DEXs and bridges collaborated to halt the token flow over the bridge within an hour of being alerted to the breach. The Hedera team disabled proxy access to the Hedera mainnet (thanks to the network being centralized, like IOTA), preventing further access by users and the attacker. A fix was swiftly developed, tested, and implemented within 41 hours of discovering the vulnerability. Unlike previous attacks in other DAGs, this time, the native system was actually the one compromised, specifically, its smart contract layer. The team acted quickly to mitigate it. Sui Network + Discord Sui Network is a distributed ledger launched in May 2023. It splits transactions into simple ones (like sending money) and complex ones (like online auctions). Simple transactions don’t require consensus, but use Proof-of-Stake (PoS) validators and a high-throughput DAG-based consensus protocol called Bullshark. complex transactions This network has proved that prevention is important, especially when it comes to new technologies. Just before their mainnet release, the security firm CertiK found a critical bug in the system. The flaw was an infinite loop bug within Sui's code that could be triggered by a malicious smart contract. This type of attack, known as the "HamsterWheel attack," doesn't crash nodes but instead keeps them endlessly running without processing new transactions, rendering the network inoperable. Once the bug , Sui developers swiftly implemented fixes to mitigate its impact, and CertiK confirmed that these fixes were already deployed. The Sui Foundation awarded $500,000 to CertiK as a bug bounty. However, it wasn’t the only threat faced by this platform. was identified Even before the potential bug, in August 2022, The announcement was shared , where several users complained about having lost funds due to the event. The incident involved hackers sharing a link to an alleged airdrop on the server's announcement channel. Since then, they reinforced their security and verification processes in the chat. Mysten Labs’ (Sui creators) Discord server was hacked. on Twitter Avalanche + DeFi Avalanche is another crypto protocol that uses DAG structures instead of blockchains. It comprises : the Contract Chain (C-Chain) for smart contracts, the Exchange Chain (X-Chain) for fast fund transfers with low fees, and the Platform Chain (P-Chain) for staking and rewards. The X-Chain, in particular, leverages DAG technology to achieve high throughput and rapid transaction finality. different chains Several DeFi protocols based on Avalanche have faced important attacks over the years. The first high-profile hack was against the lending platform in September 2021. The attack happened because they relied on a single source for their price information (oracle), and this source didn't handle decimal points properly. This allowed the attacker to manipulate prices and execute trades on pairs that weren't supposed to be traded. Vee Finance The tokens were subsequently bridged to Ethereum and remain in the attacker's possession. Vee Finance suspended platform contracts and related functions (which demonstrated that the platform wasn’t as decentralized as the term DeFi implies), actively pursuing asset recovery efforts. However, this wasn’t all for Avalanche. More attacks would come in time. That resulted in the unauthorized withdrawal of 8804.7 ETH and 213.93 BTC (around $36 million at the time). Last February 2023, two more DeFi protocols were hacked again: the multi-chain aggregator Dexible and the DEX Platypus. , the attacker leveraged the app's selfSwap function to move over $2 million worth of crypto from users who had authorized the app to access their tokens. Dexible paused its contracts and advised users to revoke token authorizations. In the first case The hacker exploited the protocol's asset contracts using a malicious smart contract with unverified source code. Now, about the three cases, we can say that some bugs escaped from DeFi developers since the beginning, resulting in the loss of funds. In the second case, Platypus $8.5 million in a flash loan attack. lost over Protect yourself from DAG risks For average users of Directed Acyclic Graph (DAG) platforms, several key security measures and protections can be applied to mitigate risks: Before using any third-party services, such as wallets or exchanges, do your research to ensure they have a good reputation for security. Also, avoid leaving large amounts of crypto on exchanges for extended periods. Use Reputable Services: If you have wallets that give you control over your private keys, use them. This means you have direct control over your funds. Cold wallets offer an extra layer of security. Secure Your Private Keys: When dealing with any cryptocurrency-related accounts, use strong, unique passwords. Consider using a reputable password manager to keep them safe. Whenever possible, enable Two-Factor Authentication (2FA) on your accounts. Use Strong Passwords and enable 2FA: Keep up to date with the latest news and developments regarding the DAG platform you're using. Understanding potential vulnerabilities can help you take preventive action. Stay Informed: Be cautious of phishing emails, messages, or websites that aim to steal your login information or private keys. Always double-check URLs and sources. Beware of Phishing Scams: For applications or services that request permission to access your wallet or tokens, review and revoke these permissions when they're no longer needed. Regularly Review Permissions: Avoid putting all your assets into a single cryptocurrency or platform. Diversification can help spread risk. Diversify Your Investments: So far, Obyte (also a crypto-DAG platform) hasn’t suffered a high-profile hack on its system or related services. That doesn’t mean they are immune to attacks, though. is active on Immunefi, with high rewards for skilled developers. However, it’s always important to apply the on your own wallet and do your own research for each platform! A bug bounty program best security measures Featured Vector Image by Freepik

5 Security Incidents Involving DAG Networks—and How to Protect Yourself

DAG নেটওয়ার্কের সাথে জড়িত 5 নিরাপত্তা ঘটনা—এবং কীভাবে নিজেকে রক্ষা করবেন

5 Sicherheitsvorfälle im Zusammenhang mit DAG-Netzwerken – und wie Sie sich schützen können

Cinco incidentes de seguridad que involucran redes DAG y cómo protegerse

5 incidents de sécurité impliquant les réseaux DAG et comment vous protéger

डीएजी नेटवर्क से जुड़ी 5 सुरक्षा घटनाएं—और अपनी सुरक्षा कैसे करें

DAG ネットワークに関連する 5 つのセキュリティ インシデントと身を守る方法

DAG 네트워크와 관련된 5가지 보안 사고 및 자신을 보호하는 방법

5 incidentes de segurança envolvendo redes DAG – e como se proteger

5 инцидентов безопасности, связанных с сетями DAG, и как защитить себя

DAG Ağlarını İçeren 5 Güvenlik Olayı ve Kendinizi Nasıl Korursunuz

5 sự cố bảo mật liên quan đến mạng DAG—và cách tự bảo vệ mình

涉及 DAG 网络的 5 个安全事件以及如何保护自己

The Way We Live Now by Anthony Trollope is part of the HackerNoon Books Series. You can jump to any chapter in this book . MISS LONGESTAFFE'S LOVER here MISS LONGESTAFFE'S LOVER. A few days before that period in our story which we have now reached, Miss Longestaffe was seated in Lady Monogram's back drawing-room, discussing the terms on which the two tickets for Madame Melmotte's grand reception had been transferred to Lady Monogram,—the place on the cards for the names of the friends whom Madame Melmotte had the honour of inviting to meet the Emperor and the Princes, having been left blank; and the terms also on which Miss Longestaffe had been asked to spend two or three days with her dear friend Lady Monogram. Each lady was disposed to get as much and to give as little as possible,—in which desire the ladies carried out the ordinary practice of all parties to a bargain. It had of course been settled that Lady Monogram was to have the two tickets,—for herself and her husband,—such tickets at that moment standing very high in the market. In payment for these valuable considerations, Lady Monogram was to undertake to chaperon Miss Longestaffe at the entertainment, to take Miss Longestaffe as a visitor for three days, and to have one party at her own house during the time, so that it might be seen that Miss Longestaffe had other friends in London besides the Melmotte's on whom to depend for her London gaieties. At this moment Miss Longestaffe felt herself justified in treating the matter as though she were hardly receiving a fair equivalent. The Melmotte tickets were certainly ruling very high. They had just culminated. They fell a little soon afterwards, and at ten p.m. on the night of the entertainment were hardly worth anything. At the moment which we have now in hand, there was a rush for them. Lady Monogram had already secured the tickets. They were in her desk. But, as will sometimes be the case in a bargain, the seller was complaining that as she had parted with her goods too cheap, some make-weight should be added to the stipulated price. "As for that, my dear," said Miss Longestaffe, who, since the rise in Melmotte stock generally, had endeavoured to resume something of her old manners, "I don't see what you mean at all. You meet Lady Julia Goldsheiner everywhere, and her father-in-law is Mr. Brehgert's junior partner." "Lady Julia is Lady Julia, my dear, and young Mr. Goldsheiner has, in some sort of way, got himself in. He hunts, and Damask says that he is one of the best shots at Hurlingham. I never met old Mr. Goldsheiner anywhere." "I have." "Oh, yes, I dare say. Mr. Melmotte, of course, entertains all the City people. I don't think Sir Damask would like me to ask Mr. Brehgert to dine here." Lady Monogram managed everything herself with reference to her own parties; invited all her own guests, and never troubled Sir Damask,—who, again, on his side, had his own set of friends; but she was very clever in the use which she made of her husband. There were some aspirants who really were taught to think that Sir Damask was very particular as to the guests whom he welcomed to his own house. "May I speak to Sir Damask about it?" asked Miss Longestaffe, who was very urgent on the occasion. "Well, my dear, I really don't think you ought to do that. There are little things which a man and his wife must manage together without interference." "Nobody can ever say that I interfered in any family. But really, Julia, when you tell me that Sir Damask cannot receive Mr. Brehgert, it does sound odd. As for City people, you know as well as I do, that that kind of thing is all over now. City people are just as good as West-end people." "A great deal better, I dare say. I'm not arguing about that. I don't make the lines; but there they are; and one gets to know in a sort of way what they are. I don't pretend to be a bit better than my neighbours. I like to see people come here whom other people who come here will like to meet. I'm big enough to hold my own, and so is Sir Damask. But we ain't big enough to introduce new-comers. I don't suppose there's anybody in London understands it better than you do, Georgiana, and therefore it's absurd my pretending to teach you. I go pretty well everywhere, as you are aware; and I shouldn't know Mr. Brehgert if I were to see him." "You'll meet him at the Melmottes', and, in spite of all you said once, you're glad enough to go there." "Quite true, my dear. I don't think that you are just the person to throw that in my teeth; but never mind that. There's the butcher round the corner in Bond Street, or the man who comes to do my hair. I don't at all think of asking them to my house. But if they were suddenly to turn out wonderful men, and go everywhere, no doubt I should be glad to have them here. That's the way we live, and you are as well used to it as I am. Mr. Brehgert at present to me is like the butcher round the corner." Lady Monogram had the tickets safe under lock and key, or I think she would hardly have said this. "He is not a bit like a butcher," said Miss Longestaffe, blazing up in real wrath. "I did not say that he was." "Yes, you did; and it was the unkindest thing you could possibly say. It was meant to be unkind. It was monstrous. How would you like it if I said that Sir Damask was like a hair-dresser?" "You can say so if you please. Sir Damask drives four in hand, rides as though he meant to break his neck every winter, is one of the best shots going, and is supposed to understand a yacht as well as any other gentleman out. And I'm rather afraid that before he was married he used to box with all the prize-fighters, and to be a little too free behind the scenes. If that makes a man like a hair-dresser, well, there he is." "How proud you are of his vices." "He's very good-natured, my dear, and as he does not interfere with me, I don't interfere with him. I hope you'll do as well. I dare say Mr. Brehgert is good-natured." "He's an excellent man of business, and is making a very large fortune." "And has five or six grown-up children, who, no doubt, will be a comfort." "If I don't mind them, why need you? You have none at all, and you find it lonely enough." "Not at all lonely. I have everything that I desire. How hard you are trying to be ill-natured, Georgiana." "Why did you say that he was a—butcher?" "I said nothing of the kind. I didn't even say that he was like a butcher. What I did say was this,—that I don't feel inclined to risk my own reputation on the appearance of new people at my table. Of course, I go in for what you call fashion. Some people can dare to ask anybody they meet in the streets. I can't. I've my own line, and I mean to follow it. It's hard work, I can tell you; and it would be harder still if I wasn't particular. If you like Mr. Brehgert to come here on Tuesday evening, when the rooms will be full, you can ask him; but as for having him to dinner, I—won't—do—it." So the matter was at last settled. Miss Longestaffe did ask Mr. Brehgert for the Tuesday evening, and the two ladies were again friends. Perhaps Lady Monogram, when she illustrated her position by an allusion to a butcher and a hair-dresser, had been unaware that Mr. Brehgert had some resemblance to the form which men in that trade are supposed to bear. Let us at least hope that she was so. He was a fat, greasy man, good-looking in a certain degree, about fifty, with hair dyed black, and beard and moustache dyed a dark purple colour. The charm of his face consisted in a pair of very bright black eyes, which were, however, set too near together in his face for the general delight of Christians. He was stout;—fat all over rather than corpulent,—and had that look of command in his face which has become common to master-butchers, probably by long intercourse with sheep and oxen. But Mr. Brehgert was considered to be a very good man of business, and was now regarded as being, in a commercial point of view, the leading member of the great financial firm of which he was the second partner. Mr. Todd's day was nearly done. He walked about constantly between Lombard Street, the Exchange, and the Bank, and talked much to merchants; he had an opinion too of his own on particular cases; but the business had almost got beyond him, and Mr. Brehgert was now supposed to be the moving spirit of the firm. He was a widower, living in a luxurious villa at Fulham with a family, not indeed grown up, as Lady Monogram had ill-naturedly said, but which would be grown up before long, varying from an eldest son of eighteen, who had just been placed at a desk in the office, to the youngest girl of twelve, who was at school at Brighton. He was a man who always asked for what he wanted; and having made up his mind that he wanted a second wife, had asked Miss Georgiana Longestaffe to fill that situation. He had met her at the Melmottes', had entertained her, with Madame Melmotte and Marie, at Beaudesert, as he called his villa, had then proposed in the square, and two days after had received an assenting answer in Bruton Street. Poor Miss Longestaffe! Although she had acknowledged the fact to Lady Monogram in her desire to pave the way for the reception of herself into society as a married woman, she had not as yet found courage to tell her family. The man was absolutely a Jew;—not a Jew that had been, as to whom there might possibly be a doubt whether he or his father or his grandfather had been the last Jew of the family; but a Jew that was. So was Goldsheiner a Jew, whom Lady Julia Start had married,—or at any rate had been one a very short time before he ran away with that lady. She counted up ever so many instances on her fingers of "decent people" who had married Jews or Jewesses. Lord Frederic Framlinghame had married a girl of the Berrenhoffers; and Mr. Hart had married a Miss Chute. She did not know much of Miss Chute, but was certain that she was a Christian. Lord Frederic's wife and Lady Julia Goldsheiner were seen everywhere. Though she hardly knew how to explain the matter even to herself, she was sure that there was at present a general heaving-up of society on this matter, and a change in progress which would soon make it a matter of indifference whether anybody was Jew or Christian. For herself she regarded the matter not at all, except as far as it might be regarded by the world in which she wished to live. She was herself above all personal prejudices of that kind. Jew, Turk, or infidel was nothing to her. She had seen enough of the world to be aware that her happiness did not lie in that direction, and could not depend in the least on the religion of her husband. Of course she would go to church herself. She always went to church. It was the proper thing to do. As to her husband, though she did not suppose that she could ever get him to church,—nor perhaps would it be desirable,—she thought that she might induce him to go nowhere, so that she might be able to pass him off as a Christian. She knew that such was the Christianity of young Goldsheiner, of which the Starts were now boasting. Had she been alone in the world she thought that she could have looked forward to her destiny with complacency; but she was afraid of her father and mother. Lady Pomona was distressingly old-fashioned, and had so often spoken with horror even of the approach of a Jew,—and had been so loud in denouncing the iniquity of Christians who allowed such people into their houses! Unfortunately, too, Georgiana in her earlier days had re-echoed all her mother's sentiments. And then her father,—if he had ever earned for himself the right to be called a Conservative politician by holding a real opinion of his own,—it had been on that matter of admitting the Jews into parliament. When that had been done he was certain that the glory of England was sunk for ever. And since that time, whenever creditors were more than ordinarily importunate, when Slow and Bideawhile could do nothing for him, he would refer to that fatal measure as though it was the cause of every embarrassment which had harassed him. How could she tell parents such as these that she was engaged to marry a man who at the present moment went to synagogue on a Saturday and carried out every other filthy abomination common to the despised people? That Mr. Brehgert was a fat, greasy man of fifty, conspicuous for hair-dye, was in itself distressing:—but this minor distress was swallowed up in the greater. Miss Longestaffe was a girl possessing considerable discrimination, and was able to weigh her own possessions in just scales. She had begun life with very high aspirations, believing in her own beauty, in her mother's fashion, and her father's fortune. She had now been ten years at the work, and was aware that she had always flown a little too high for her mark at the time. At nineteen and twenty and twenty-one she had thought that all the world was before her. With her commanding figure, regular long features, and bright complexion, she had regarded herself as one of the beauties of the day, and had considered herself entitled to demand wealth and a coronet. At twenty-two, twenty-three, and twenty-four any young peer, or peer's eldest son, with a house in town and in the country, might have sufficed. Twenty-five and six had been the years for baronets and squires; and even a leading fashionable lawyer or two had been marked by her as sufficient since that time. But now she was aware that hitherto she had always fixed her price a little too high. On three things she was still determined,—that she would not be poor, that she would not be banished from London, and that she would not be an old maid. "Mamma," she had often said, "there's one thing certain. I shall never do to be poor." Lady Pomona had expressed full concurrence with her child. "And, mamma, to do as Sophia is doing would kill me. Fancy having to live at Toodlam all one's life with George Whitstable!" Lady Pomona had agreed to this also, though she thought that Toodlam Hall was a very nice home for her elder daughter. "And, mamma, I should drive you and papa mad if I were to stay at home always. And what would become of me when Dolly was master of everything?" Lady Pomona, looking forward as well as she was able to the time at which she should herself have departed, when her dower and dower-house would have reverted to Dolly, acknowledged that Georgiana should provide herself with a home of her own before that time. And how was this to be done? Lovers with all the glories and all the graces are supposed to be plentiful as blackberries by girls of nineteen, but have been proved to be rare hothouse fruits by girls of twenty-nine. Brehgert was rich, would live in London, and would be a husband. People did such odd things now and "lived them down," that she could see no reason why she should not do this and live this down. Courage was the one thing necessary,—that and perseverance. She must teach herself to talk about Brehgert as Lady Monogram did of Sir Damask. She had plucked up so much courage as had enabled her to declare her fate to her old friend,—remembering as she did so how in days long past she and her friend Julia Triplex had scattered their scorn upon some poor girl who had married a man with a Jewish name,—whose grandfather had possibly been a Jew. "Dear me," said Lady Monogram. "Todd, Brehgert, and Goldsheiner! Mr. Todd is—one of us, I suppose." "Yes," said Georgiana boldly, "and Mr. Brehgert is a Jew. His name is Ezekiel Brehgert, and he is a Jew. You can say what you like about it." "I don't say anything about it, my dear." "And you can think anything you like. Things are changed since you and I were younger." "Very much changed, it appears," said Lady Monogram. Sir Damask's religion had never been doubted, though except on the occasion of his marriage no acquaintance of his had probably ever seen him in church. But to tell her father and mother required a higher spirit than she had shown even in her communication to Lady Monogram, and that spirit had not as yet come to her. On the morning before she left the Melmottes in Bruton Street, her lover had been with her. The Melmottes of course knew of the engagement and quite approved of it. Madame Melmotte rather aspired to credit for having had so happy an affair arranged under her auspices. It was some set-off against Marie's unfortunate escapade. Mr. Brehgert, therefore, had been allowed to come and go as he pleased, and on that morning he had pleased to come. They were sitting alone in some back room, and Brehgert was pressing for an early day. "I don't think we need talk of that yet, Mr. Brehgert," she said. "You might as well get over the difficulty and call me Ezekiel at once," he remarked. Georgiana frowned, and made no soft little attempt at the name as ladies in such circumstances are wont to do. "Mrs. Brehgert"—he alluded of course to the mother of his children—"used to call me Ezzy." "Perhaps I shall do so some day," said Miss Longestaffe, looking at her lover, and asking herself why she should not have been able to have the house and the money and the name of the wife without the troubles appertaining. She did not think it possible that she should ever call him Ezzy. "And ven shall it be? I should say as early in August as possible." "In August!" she almost screamed. It was already July. "Vy not, my dear? Ve would have our little holiday in Germany,—at Vienna. I have business there, and know many friends." Then he pressed her hard to fix some day in the next month. It would be expedient that they should be married from the Melmottes' house, and the Melmottes would leave town some time in August. There was truth in this. Unless married from the Melmottes' house, she must go down to Caversham for the occasion,—which would be intolerable. No;—she must separate herself altogether from father and mother, and become one with the Melmottes and the Brehgerts,—till she could live it down and make a position for herself. If the spending of money could do it, it should be done. "I must at any rate ask mamma about it," said Georgiana. Mr. Brehgert, with the customary good-humour of his people, was satisfied with the answer, and went away promising that he would meet his love at the great Melmotte reception. Then she sat silent, thinking how she should declare the matter to her family. Would it not be better for her to say to them at once that there must be a division among them,—an absolute breaking off of all old ties, so that it should be tacitly acknowledged that she, Georgiana, had gone out from among the Longestaffes altogether, and had become one with the Melmottes, Brehgerts, and Goldsheiners? About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Anthony Trollope (2004). The Way We Live Now. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/cache/epub/5231/pg5231-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

MISS LONGESTAFFE'S LOVER

OWNWELL

ownwell.com

51-200 employees

Since 2020

COMPANY RANKING

OWNWELL

EVERGREEN INDEX #732

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

Ownwell WIKI

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

OWNWELL

ownwell.com

51-200 employees

Since 2020

COMPANY RANKING

OWNWELL

EVERGREEN INDEX #732

RELATED COMPANIESRANK

STORIES ABOUT OWNWELL

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

Ownwell WIKI

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