Listenis in the Enterprise Collaboration Industry

Listen

initially started as a pet project for my coding sessions. It gradually turned into something that would be useful for other developers, too, so I made it public, and I still can't believe how far it has come! DevTunes FM I am so grateful to announce that we recently hit a major milestone of 700K+ listens. I want to thank you all for being so supportive, and this means the world to me! To celebrate this, I decided to write an article where I could take you behind the scenes and share some of the most valuable lessons I've learned. Tune in here: radio.madza.dev Also, I created some visuals to illustrate the core ideas better and gave practical examples for each point. I hope you will enjoy this article! 1. Clear vision is key When it comes to the vision, having a clear goal is essential. It's the foundation of your project, so the more concise it will be, the easier it will be to build upon. Before I started to build anything, I knew my focus would be on simplicity, usability, and the design of the app. I based all my further decisions on that. 2. Planning rewards itself As A. Lincoln once said, "Give me six hours to chop down a tree and I will spend the first four sharpening the axe". The same could be applied to development. I spent quite a lot of time planning all the features. But it made the design and coding part way easier since I knew what functionality I was going for. 3. UI is thinking made visual Once you have planned everything, coming up with the UI is like displaying your thought logic so that users can interact with it. For example, I used Figma to create all of the UI components for the app. The UI is your presentation, so it should be easy to use and straightforward. 4. UX is all about the details The UX should not be underestimated since all the little things combined leave an impression on users and affect whether or not they will come back. I spent time improving UX, such as the loading screen, transitions between the background changes, implementing keyboard shortcuts, and more. 5. Passion projects boost motivation I am a strong believer that passion fuels success, therefore I feel that it is important to work on something that genuinely interests and attracts you. I've been listening to various genres of electronic subgenres for a couple of decades now, and it was a dream of mine to compile them all on this app. 6. Don't settle for less "Build it, and they will come" is a myth! Spread the word about your work wherever you can! Listen to your users and improve your project accordingly. I launched the project on Product Hunt, wrote about it on DEV, Hashnode, and Medium, and now I'm actively using Twitter and LinkedIn to announce updates. 7. Responsive design = priority With so many devices out there, your app should be adapted for various screen sizes. Use analytics like Umami to get to know your audience better. For example, I like to listen to DevTunes FM via the web version while I am coding, and I am also listening when I am running or biking via the mobile version. 8. Persistence pays off Keep learning new stuff, consume quality content, and work on new ideas. No problem is hard enough if you put enough thought into it. I've been working on DevTunes FM for about two years and learned a lot along the way. I still keep setting new goals and celebrating exciting milestones! Try it out yourself: radio.madza.dev Writing has always been my passion, and it gives me pleasure to help and inspire people. If you have any questions, feel free to reach out! Make sure to receive the best resources, tools, productivity tips, and career growth tips I discover by subscribing to ! my newsletter Also, connect with me on , , and ! Twitter LinkedIn GitHub Also, published . here

8 Valuable Lessons I Learned After My Online Dev Radio Reached 700K+ Listens🙏💖

OpenAI is groundbreaking features to ChatGPT, allowing it to break barriers by enabling the AI to see, hear, and speak. The multimodality and enhancements in user interaction are set to roll out in the next two weeks, a significant leap from the text-based interactions. Here’s what you need to know about this version: introducing 1. Voice Interaction: For the first time, ChatGPT will respond verbally to user queries, turning it into a more interactive and engaging conversational partner. This feature will be available on iOS and Android, and users can opt-in to use voice to engage in back-and-forth conversations with the AI. This places ChatGPT in direct competition with renowned voice assistants like Siri and Alexa. 2. Enhanced Multimodal Interaction: Users can now show images to ChatGPT and have live conversations about them, allowing for a more intuitive and enriched user experience. This feature is a significant step in providing more context during interactions and is available on all platforms. 3. Personalized Artificial Personas: Five neutral artificial personas including Juniper, Breeze, and Ember, will be answering verbally to user queries. Eventually, OpenAI plans to allow users to create their personalized voice, broadening user experiences. 4. Advanced Whisper Engine: The advanced Whisper engine powers the AI voices, which have received positive initial reviews for their human-like interaction, despite having a style that some may find intrusive. 5. Subscription-Based Access: The new voice and image capabilities will be exclusive to ChatGPT Plus subscribers, priced at $20 per month, focusing on providing advanced features to dedicated users. 6. Addressing Ethical Concerns: OpenAI is confident of having resolved most bugs and is focusing on addressing ideological issues, including potential voice fraud, discrimination against uncommon accents, and inadvertent attribution of social and political baggage to the AI's voice. They assure that the capability for de-anonymizing individuals through photos in ChatGPT has been blocked. 7. New Use Cases: These features provide more versatile applications, allowing users to take pictures of landmarks or their fridge contents and have real-time conversations about them, thus helping in various scenarios like travel, cooking, or learning. Want to check the tests of the new Voice feature and understand how to get started with Voice in ChatGPT? I will be testing and reviewing it in my newsletter ‘ . There you can find new instruments and use cases for the most groundbreaking AI instruments. ; it’s absolutely free! AI Hunters’ Subscribe Summary: OpenAI's ChatGPT is poised to become more interactive and user-friendly with the introduction of these new features, aligning it more closely with the needs and preferences of users and expanding its range of applications. The amalgamation of voice interaction, image recognition, personalized AI personas, and ethical considerations, all underscore OpenAI's commitment to providing innovative and responsible AI solutions. With the deployment of these enhancements, ChatGPT is not just another chatbot but is becoming a multifaceted assistant, bringing an intuitive and enriching experience to its users.

ChatGPT Now Speaks, Listens, and Understands: All You Need to Know

In this article, we will tackle a question: Does Vue.js support multiple event listeners? Our journey will take us deep into the mechanics of Vue.js, unraveling some intriguing undocumented behaviors along the way. Let's begin with a closer look at the official documentation on "Event Handling" in Vue.js. The primary method of attaching an event listener is through the syntax, which can also be simplified as . v-on:click="handler" @click="handler" In this syntax, the refers to a reference to a function. Additionally, in the "Inline Handlers" section, it's highlighted that you can employ arbitrary JavaScript code directly within the attribute. handler For instance, you can use to increment a variable. An important note is provided in the "Method vs. Inline Detection" section, which indicates that: @click="count++" The template compiler detects method handlers by checking whether the value string is a valid JavaScript identifier or a property access path. v-on So, does Vue support multiple listeners? The answer seems to lean towards no, but it's not entirely clear-cut. Let recap it with the code: <script setup>
import { ref } from 'vue';

const count = ref(0);
function inc() { count.value += 1; }
</script>

<template>
  <h3>{{ count }}</h3>
  <button @click="count++">Incremenet by count++</button>
  <button @click="inc">Incremenet by ref</button>
  <button @click="inc()">Incremenet by call</button>
  <button @click="() => inc()">Incremenet by lambda</button>
</template> Now, let's within the Vue SFC Playground to closely examine how the Vue.js compiler has compiled these listeners. take a plunge into the JS tab We will encounter the following code snippet (I've omitted the portions for the sake of readability): _cache[0] || (_cache[0] = $event => (count.value++)) _createElementVNode("h3", null, _toDisplayString(count.value), 1 /* TEXT */);

// @click="count++" will be compiled to...
_createElementVNode(
  "button",
  {
    onClick: ($event) => count.value++,
  },
  "Incremenet by count++",
);

// @click="inc" will be compiled to...
_createElementVNode("button", { onClick: inc }, "Incremenet by ref");

// @click="inc()" will be compiled to...
_createElementVNode(
  "button",
  {
    onClick: ($event) => inc(),
  },
  "Incremenet by call",
);

// @click="() => inc()" will be compiled to...
_createElementVNode(
  "button",
  {
    onClick: () => inc(),
  },
  "Incremenet by lambda",
); The behavior is indeed intriguing. When a reference to is passed, the compiler simplifies it to . However, for , and , the compiler follows a distinct route. It encapsulates the code enclosed within the template's into a lambda function and then proceeds to execute it exactly as it's written. inc { onClick: inc } count++ inc() () => inc() " This observation offers valuable insight: if the compiler wraps code within a lambda, we can leverage native JavaScript capabilities to call multiple functions within a single expression using or . Let's try it. fn1(); fn2() fn1(), fn2() We will introduce another function, , which will invoke the native function and pass into it. You can access the updated Playground . showAlert() alert() count.value here Here is the code: // @click="count++, showAlert()" will be compiled to...
_createElementVNode(
  "button",
  {
    onClick: ($event) => (count.value++, showAlert()),
  },
  "Increment by count++",
);

// How to pass multiple refs?
_createElementVNode("button", { onClick: inc }, "Increment by ref");

// @click="inc(); showAlert()" will be compiled to...
_createElementVNode(
  "button",
  {
    onClick: ($event) => {
      inc();
      showAlert();
    },
  },
  "Increment by call",
);

// @click="() => (inc(), showAlert())" will be compiled to...
_createElementVNode(
  "button",
  {
    onClick: () => (inc(), showAlert()),
  },
  "Increment by lambda",
); For , , and , everything works fine, allowing us to call multiple functions for a single event. @click="count++, showAlert()" @click="inc(); showAlert()" @click="() => (inc(), showAlert())" The issue arises when dealing with the case. How can we pass multiple into the handler? The official documentation is notably silent on the topic of passing multiple references. ref refs @click="..." It appears that this feature might not be supported, leaving us unable to achieve this behavior directly. To explore this further, let's experiment with the two initial approaches that come to mind: and , and observe how they are compiled by Vue.js. fn1, fn2 [fn1, f2] // @click="inc, showAlert" will be complied to...
_createElementVNode("button", {
  onClick: $event => (inc, showAlert)
}, "Multiple refs 1");

// @click="[inc, showAlert]" will be complied to...
_createElementVNode("button", {
  onClick: $event => ([inc, showAlert])
}, "Multiple refs 2") Unfortunately, both attempts did not yield success. Vue.js compiles these expressions in a manner that involves encapsulating the code enclosed within the template's . This approach is consistent with the behavior we previously uncovered. " Let's take a step back and examine the scenario where we simply pass a function identifier without any accompanying braces in the event handler. () // @click="inc" will be compiled to...
_createElementVNode(
  "button",
  { onClick: inc },
  "Incremenet by ref",
); Vue simply maps to . Now, let's recap the rule we extracted from the documentation. inc onClick The template compiler detects method handlers by checking whether the value string is a valid JavaScript identifier or a property access path. v-on Incorporating the insights gained from the above, we can rephrase this rule as follows: If the string within the template's or , is recognized as a valid JavaScript identifier, Vue.js compiler will directly map it to . v-on @event { onEvent: <Valid JS Identifier> } Or like this: Using only the name of a variable or a function will result in direct mapping. Our revised definition omits any reference to a "method" handler; it purely states that when a valid identifier is used, it is directly passed as is. This implies that you can even pass a numeric value like to an handler, provided you first create an identifier (in other words, a variable) that's bound to the value. 1337 onClick Passing a number as a handler clearly won't yield the desired results. However, as we recall, our aim is to pass multiple handlers as an array of refs. Given our newly established understanding, this is achievable. However, the prerequisite is to create a "valid JS Identifier (variable)" to store the reference to the array. Let's put this into action and see the results. . An interesting observation unfolds. Take a look here Firstly, using a "valid JS Identifier (variable)" named , we successfully pass an array to , and it gets mapped accordingly. multiple onClick However, TypeScript expresses its discontent. It raises an error stating: Type '(() => void)[]' is not assignable to type '(payload: MouseEvent) => void'. Type '(() => void)[]' provides no match for the signature '(payload: MouseEvent): void'.ts(2322) In essence, the types within Vue.js prevent us from passing an array of functions as a click listener. Let's set this aside for now, and simply click on the button to observe whether both listeners will be invoked. And yes, they are. We witness the counter value incrementing, followed by the appearance of the alert. But hold on, there's a puzzle to solve. Why is this functioning? What's going on behind the scenes? To comprehend this, we must delve deeper and grasp the mechanics underlying the translation of Vue's , created by the function, into a native DOM element. The key lies in exploring the source code of Vue.js itself! VNode _createElementVNode When we call the function in our main or , it triggers a chain of events that leads to the execution of the function (look for function ). createApp() app.js index.js createRenderer() createApp here This sequence results in the formation of an instance, complete with a method. This method establishes an association with the renderer (see ). This renderer's primary task is to convert our s into the native DOM elements we interact with. app mount() ensureRenderer() here VNode Here's an overview of the key steps: We compile our template, resulting in a series of calls. _createElementVNode() These calls build our Virtual DOM, generating s. VNode The renderer then traverses these nodes, converting them into native DOM elements. As the renderer transforms s into native DOM elements, it performs additional tasks using the object of a through the method. VNode props VNode patchProp Additionally, note that the function is invoked with , encompassing a "patched" . Let's delve into this for further understanding. createRenderer(rendererOptions) extended rendererOptions patchProp method export const patchProp: DOMRendererOptions['patchProp'] = (
  // Omitted params...
) => {
  if (key === 'class') {
    patchClass(el, nextValue, isSVG)
  } else if (key === 'style') {
    patchStyle(el, prevValue, nextValue)
    // Keep in mind that we provide an object containing on<EventName> keys.
    // `isOn(key)` will return true for these keys.
  } else if (isOn(key)) {
    if (!isModelListener(key)) {
      // If the listener isn't intended for `v-model`, we utilize the `patchEvent` mechanism.
      patchEvent(el, key, prevValue, nextValue, parentComponent)
    }
  } // ... We can interpret the code as follows: "If a prop is , apply special handling based on values. If a prop is , implement special handling based on values. And if a prop begins with , perform specific actions using ." class class style style on patchEvent Let's direct our attention to the . We've reached the bottom where Vue establishes native event bindings through the browser's method. However, prior to this step, there are additional operations in play. patchEvent method addEventListener() The high-level call chain is as follows: is invoked. patchEvent() It proceeds to call in order to generate an invoker function. createInvoker() Inside the , we invoke , passing a wrapped version (altered by ) of the value provided in the event handler. invoker callWithAsyncErrorHandling patchStopImmediatePropagation @click="..." Now, let's examine to uncover the answer to the question: "Why does passing multiple refs to a function work?" patchStopImmediatePropagation function patchStopImmediatePropagation(
  e: Event,
  value: EventValue
): EventValue {

  // If the value is an array, there's even more to explore! 
  // We can call $event.stopImmediatePropagation()
  // and other functions within the array won't be invoked.
  if (isArray(value)) {
    const originalStop = e.stopImmediatePropagation
    e.stopImmediatePropagation = () => {
      originalStop.call(e)
      ;(e as any)._stopped = true
    }

    // This is where the actual function calls occur.
    return value.map(fn => (e: Event) => !(e as any)._stopped && fn && fn(e))
  } else {
    return value
  }
} And here we are, fully informed. Even though the official documentation and TypeScript might not explicitly endorse it, we've found a code segment that effectively allows us to pass event listeners using an array of function references. There is the that introduced this functionality. It appears that at some point in the past, there might have been an intention to enable the capability of passing multiple listeners. However, as it stands now, this remains an undocumented feature. commit Lastly, let's address the question we initially posed: Does Vue support multiple listeners? The answer hinges on your interpretation of "supports". To summarize: We can invoke multiple functions using , and there's a for that. fn1(); fn2() test We can also invoke them using . fn1(), fn2() We can pass it through an array if stored in a variable. Alternatively, given the newfound knowledge, we can even call them like so: <template>
  <button @click="[fn1, fn2].forEach((fn) => fn($event))">
    Click!
  </button>
</template> Also published here

Unlocking the Puzzle: Investigating Multiple Event Listeners in Vue.js

Around the World in Eighty Days by Jules Verne, is part of the HackerNoon Books Series. You can jump to any chapter in this book . IN WHICH PASSEPARTOUT DOES NOT SUCCEED IN MAKING ANYBODY LISTEN TO REASON here CHAPTER XXVIII. IN WHICH PASSEPARTOUT DOES NOT SUCCEED IN MAKING ANYBODY LISTEN TO REASON The train, on leaving Great Salt Lake at Ogden, passed northward for an hour as far as Weber River, having completed nearly nine hundred miles from San Francisco. From this point it took an easterly direction towards the jagged Wahsatch Mountains. It was in the section included between this range and the Rocky Mountains that the American engineers found the most formidable difficulties in laying the road, and that the government granted a subsidy of forty-eight thousand dollars per mile, instead of sixteen thousand allowed for the work done on the plains. But the engineers, instead of violating nature, avoided its difficulties by winding around, instead of penetrating the rocks. One tunnel only, fourteen thousand feet in length, was pierced in order to arrive at the great basin. The track up to this time had reached its highest elevation at the Great Salt Lake. From this point it described a long curve, descending towards Bitter Creek Valley, to rise again to the dividing ridge of the waters between the Atlantic and the Pacific. There were many creeks in this mountainous region, and it was necessary to cross Muddy Creek, Green Creek, and others, upon culverts. Passepartout grew more and more impatient as they went on, while Fix longed to get out of this difficult region, and was more anxious than Phileas Fogg himself to be beyond the danger of delays and accidents, and set foot on English soil. At ten o’clock at night the train stopped at Fort Bridger station, and twenty minutes later entered Wyoming Territory, following the valley of Bitter Creek throughout. The next day, 7th December, they stopped for a quarter of an hour at Green River station. Snow had fallen abundantly during the night, but, being mixed with rain, it had half melted, and did not interrupt their progress. The bad weather, however, annoyed Passepartout; for the accumulation of snow, by blocking the wheels of the cars, would certainly have been fatal to Mr. Fogg’s tour. “What an idea!” he said to himself. “Why did my master make this journey in winter? Couldn’t he have waited for the good season to increase his chances?” While the worthy Frenchman was absorbed in the state of the sky and the depression of the temperature, Aouda was experiencing fears from a totally different cause. Several passengers had got off at Green River, and were walking up and down the platforms; and among these Aouda recognised Colonel Stamp Proctor, the same who had so grossly insulted Phileas Fogg at the San Francisco meeting. Not wishing to be recognised, the young woman drew back from the window, feeling much alarm at her discovery. She was attached to the man who, however coldly, gave her daily evidences of the most absolute devotion. She did not comprehend, perhaps, the depth of the sentiment with which her protector inspired her, which she called gratitude, but which, though she was unconscious of it, was really more than that. Her heart sank within her when she recognised the man whom Mr. Fogg desired, sooner or later, to call to account for his conduct. Chance alone, it was clear, had brought Colonel Proctor on this train; but there he was, and it was necessary, at all hazards, that Phileas Fogg should not perceive his adversary. Aouda seized a moment when Mr. Fogg was asleep to tell Fix and Passepartout whom she had seen. “And, besides,” added Passepartout, “I’ll take charge of him, colonel as he is.” “Mr. Fix,” resumed Aouda, “Mr. Fogg will allow no one to avenge him. He said that he would come back to America to find this man. Should he perceive Colonel Proctor, we could not prevent a collision which might have terrible results. He must not see him.” “You are right, madam,” replied Fix; “a meeting between them might ruin all. Whether he were victorious or beaten, Mr. Fogg would be delayed, and—” “And,” added Passepartout, “that would play the game of the gentlemen of the Reform Club. In four days we shall be in New York. Well, if my master does not leave this car during those four days, we may hope that chance will not bring him face to face with this confounded American. We must, if possible, prevent his stirring out of it.” The conversation dropped. Mr. Fogg had just woke up, and was looking out of the window. Soon after Passepartout, without being heard by his master or Aouda, whispered to the detective, “Would you really fight for him?” “I would do anything,” replied Fix, in a tone which betrayed determined will, “to get him back living to Europe!” Passepartout felt something like a shudder shoot through his frame, but his confidence in his master remained unbroken. Was there any means of detaining Mr. Fogg in the car, to avoid a meeting between him and the colonel? It ought not to be a difficult task, since that gentleman was naturally sedentary and little curious. The detective, at least, seemed to have found a way; for, after a few moments, he said to Mr. Fogg, “These are long and slow hours, sir, that we are passing on the railway.” “Yes,” replied Mr. Fogg; “but they pass.” “You were in the habit of playing whist,” resumed Fix, “on the steamers.” “Yes; but it would be difficult to do so here. I have neither cards nor partners.” “Oh, but we can easily buy some cards, for they are sold on all the American trains. And as for partners, if madam plays—” “Certainly, sir,” Aouda quickly replied; “I understand whist. It is part of an English education.” “I myself have some pretensions to playing a good game. Well, here are three of us, and a dummy—” “As you please, sir,” replied Phileas Fogg, heartily glad to resume his favourite pastime even on the railway. Passepartout was dispatched in search of the steward, and soon returned with two packs of cards, some pins, counters, and a shelf covered with cloth. The game commenced. Aouda understood whist sufficiently well, and even received some compliments on her playing from Mr. Fogg. As for the detective, he was simply an adept, and worthy of being matched against his present opponent. “Now,” thought Passepartout, “we’ve got him. He won’t budge.” At eleven in the morning the train had reached the dividing ridge of the waters at Bridger Pass, seven thousand five hundred and twenty-four feet above the level of the sea, one of the highest points attained by the track in crossing the Rocky Mountains. After going about two hundred miles, the travellers at last found themselves on one of those vast plains which extend to the Atlantic, and which nature has made so propitious for laying the iron road. On the declivity of the Atlantic basin the first streams, branches of the North Platte River, already appeared. The whole northern and eastern horizon was bounded by the immense semi-circular curtain which is formed by the southern portion of the Rocky Mountains, the highest being Laramie Peak. Between this and the railway extended vast plains, plentifully irrigated. On the right rose the lower spurs of the mountainous mass which extends southward to the sources of the Arkansas River, one of the great tributaries of the Missouri. At half-past twelve the travellers caught sight for an instant of Fort Halleck, which commands that section; and in a few more hours the Rocky Mountains were crossed. There was reason to hope, then, that no accident would mark the journey through this difficult country. The snow had ceased falling, and the air became crisp and cold. Large birds, frightened by the locomotive, rose and flew off in the distance. No wild beast appeared on the plain. It was a desert in its vast nakedness. After a comfortable breakfast, served in the car, Mr. Fogg and his partners had just resumed whist, when a violent whistling was heard, and the train stopped. Passepartout put his head out of the door, but saw nothing to cause the delay; no station was in view. Aouda and Fix feared that Mr. Fogg might take it into his head to get out; but that gentleman contented himself with saying to his servant, “See what is the matter.” Passepartout rushed out of the car. Thirty or forty passengers had already descended, amongst them Colonel Stamp Proctor. The train had stopped before a red signal which blocked the way. The engineer and conductor were talking excitedly with a signal-man, whom the station-master at Medicine Bow, the next stopping place, had sent on before. The passengers drew around and took part in the discussion, in which Colonel Proctor, with his insolent manner, was conspicuous. Passepartout, joining the group, heard the signal-man say, “No! you can’t pass. The bridge at Medicine Bow is shaky, and would not bear the weight of the train.” This was a suspension-bridge thrown over some rapids, about a mile from the place where they now were. According to the signal-man, it was in a ruinous condition, several of the iron wires being broken; and it was impossible to risk the passage. He did not in any way exaggerate the condition of the bridge. It may be taken for granted that, rash as the Americans usually are, when they are prudent there is good reason for it. Passepartout, not daring to apprise his master of what he heard, listened with set teeth, immovable as a statue. “Hum!” cried Colonel Proctor; “but we are not going to stay here, I imagine, and take root in the snow?” “Colonel,” replied the conductor, “we have telegraphed to Omaha for a train, but it is not likely that it will reach Medicine Bow in less than six hours.” “Six hours!” cried Passepartout. “Certainly,” returned the conductor, “besides, it will take us as long as that to reach Medicine Bow on foot.” “But it is only a mile from here,” said one of the passengers. “Yes, but it’s on the other side of the river.” “And can’t we cross that in a boat?” asked the colonel. “That’s impossible. The creek is swelled by the rains. It is a rapid, and we shall have to make a circuit of ten miles to the north to find a ford.” The colonel launched a volley of oaths, denouncing the railway company and the conductor; and Passepartout, who was furious, was not disinclined to make common cause with him. Here was an obstacle, indeed, which all his master’s banknotes could not remove. There was a general disappointment among the passengers, who, without reckoning the delay, saw themselves compelled to trudge fifteen miles over a plain covered with snow. They grumbled and protested, and would certainly have thus attracted Phileas Fogg’s attention if he had not been completely absorbed in his game. Passepartout found that he could not avoid telling his master what had occurred, and, with hanging head, he was turning towards the car, when the engineer, a true Yankee, named Forster called out, “Gentlemen, perhaps there is a way, after all, to get over.” “On the bridge?” asked a passenger. “On the bridge.” “With our train?” “With our train.” Passepartout stopped short, and eagerly listened to the engineer. “But the bridge is unsafe,” urged the conductor. “No matter,” replied Forster; “I think that by putting on the very highest speed we might have a chance of getting over.” “The devil!” muttered Passepartout. But a number of the passengers were at once attracted by the engineer’s proposal, and Colonel Proctor was especially delighted, and found the plan a very feasible one. He told stories about engineers leaping their trains over rivers without bridges, by putting on full steam; and many of those present avowed themselves of the engineer’s mind. “We have fifty chances out of a hundred of getting over,” said one. “Eighty! ninety!” Passepartout was astounded, and, though ready to attempt anything to get over Medicine Creek, thought the experiment proposed a little too American. “Besides,” thought he, “there’s a still more simple way, and it does not even occur to any of these people! Sir,” said he aloud to one of the passengers, “the engineer’s plan seems to me a little dangerous, but—” “Eighty chances!” replied the passenger, turning his back on him. “I know it,” said Passepartout, turning to another passenger, “but a simple idea—” “Ideas are no use,” returned the American, shrugging his shoulders, “as the engineer assures us that we can pass.” “Doubtless,” urged Passepartout, “we can pass, but perhaps it would be more prudent—” “What! Prudent!” cried Colonel Proctor, whom this word seemed to excite prodigiously. “At full speed, don’t you see, at full speed!” “I know—I see,” repeated Passepartout; “but it would be, if not more prudent, since that word displeases you, at least more natural—” “Who! What! What’s the matter with this fellow?” cried several. The poor fellow did not know to whom to address himself. “Are you afraid?” asked Colonel Proctor. “I afraid? Very well; I will show these people that a Frenchman can be as American as they!” “All aboard!” cried the conductor. “Yes, all aboard!” repeated Passepartout, and immediately. “But they can’t prevent me from thinking that it would be more natural for us to cross the bridge on foot, and let the train come after!” But no one heard this sage reflection, nor would anyone have acknowledged its justice. The passengers resumed their places in the cars. Passepartout took his seat without telling what had passed. The whist-players were quite absorbed in their game. The locomotive whistled vigorously; the engineer, reversing the steam, backed the train for nearly a mile—retiring, like a jumper, in order to take a longer leap. Then, with another whistle, he began to move forward; the train increased its speed, and soon its rapidity became frightful; a prolonged screech issued from the locomotive; the piston worked up and down twenty strokes to the second. They perceived that the whole train, rushing on at the rate of a hundred miles an hour, hardly bore upon the rails at all. And they passed over! It was like a flash. No one saw the bridge. The train leaped, so to speak, from one bank to the other, and the engineer could not stop it until it had gone five miles beyond the station. But scarcely had the train passed the river, when the bridge, completely ruined, fell with a crash into the rapids of Medicine Bow. 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. Jules Verne (1994). Around the World in Eighty Days. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/files/103/103-h/103-h.htm 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

IN WHICH PASSEPARTOUT DOES NOT SUCCEED IN MAKING ANYBODY LISTEN TO REASON

Kafka is widely used for building event-driven architectures, allowing services to communicate through messages. However, when working with a foreign provider that adds a " " header to messages, you may encounter serialization and deserialization issues. microservices TypeId This article will guide you through the process of configuring a custom type mapper in Spring Kafka to handle the mapping of types between the producer and consumer services. By implementing this approach, you can successfully consume messages with different package structures and types, avoiding exceptions caused by incompatible types and ensuring smooth message processing. Understanding the deserialization Exception with " " Header TypeId In scenarios where the classes used in the consumer service have a different package structure compared to the producer service's DTO classes, the serialization exception can occur due to the mismatched class paths. DTO The serialization process relies on both the producer and the consumer having access to the same class definitions. When the consumer receives a message with a " " header referencing a class that resides in a different package than the consumer's DTO classes, the deserialization process fails to locate the appropriate class definition. This results in the "ClassNotFoundException" or "IllegalArgumentException" within the serialization exception. TypeId These exceptions can disrupt the smooth consumption of messages. Understanding the root cause of this exception is key to effectively handling the situation. An example of the serialization exception is as follows: javaCopy codejava.lang.IllegalStateException: This error handler cannot process 'SerializationException's directly; please consider configuring an 'ErrorHandlingDeserializer' in the value and/or key deserializer
	at org.springframework.kafka.listener.DefaultErrorHandler.handleOtherException(DefaultErrorHandler.java:198) ~[spring-kafka-3.0.7.jar:3.0.7]
Caused by: org.apache.kafka.common.errors.RecordDeserializationException: Error deserializing key/value for partition consumer-test-18 at offset 1. If needed, please seek past the record to continue consumption.
	at org.apache.kafka.clients.consumer.internals.Fetcher.parseRecord(Fetcher.java:1438) ~[kafka-clients-3.4.0.jar:na]
Caused by: java.lang.IllegalArgumentException: The class 'org.example.dto.out.OutMessageImplTwo' is not in the trusted packages: [java.util, java.lang, org.example.dto.in, org.example.dto.in.*]. 
If you believe this class is safe to deserialize, please provide its name. If the serialization is only done by a trusted source, you can also enable trust all (*).
	at org.springframework.kafka.support.mapping.DefaultJackson2JavaTypeMapper.getClassIdType(DefaultJackson2JavaTypeMapper.java:129) ~[spring-kafka-3.0.7.jar:3.0.7] The exception message provides insights into the underlying problem. In this case, the exception occurs because the class is not present in the list of trusted packages. The trusted packages serve as a safeguard to ensure secure deserialization and prevent unauthorized classes from being deserialized. org.example.dto.out.OutMessageImplTwo When deserializing a message, the default behavior of Spring Kafka is to check if the class specified in the "TypeId" header is within the trusted packages. If it is not found, an exception is thrown. This mechanism is in place to protect against potential security risks, as deserializing untrusted classes can lead to code execution vulnerabilities. To resolve this issue, you need to ensure that the consumer can properly map the incoming message to the corresponding class, even if they have different package structures. One approach is to configure a custom type mapper that explicitly handles the type mapping between the " " header and the consumer's DTO classes. TypeId By implementing a custom type mapper, you can instruct the consumer to map the " " header to the appropriate class or even ignore this header. This enables successful deserialization and ensures that the consumer can process the message correctly. TypeId In the upcoming sections, we will delve into the details of configuring and implementing a custom type mapper in Kafka listeners, allowing seamless message processing and addressing the challenges encountered when the consumer's DTO classes differ from those of the producer. Implementation of custom-type mapper In our example, we will send an implementation of OutMessageAbstract to Kafka and will read it as an implementation of the InMessageAbstract class. These classes are absolutely identical, they differ in name and package. The figure below shows the project structure. Our KafkaListener looks like this. It implements the logic for processing each type of message from the topic. @Component
@Log
@KafkaListener(
        topics = "${spring.cloud.stream.bindings.topic-in-0.destination}",
        groupId = "${spring.cloud.stream.bindings.topic-in-0.group}",
        containerFactory = "kafkaListenerContainerFactory")
public class EventListeners {
    @KafkaHandler
    public void handleInMessageImplEvent(@Payload InMessageImpl event) {
        System.out.println(event);
    }

    @KafkaHandler
    public void handleInMessageImplTwoEvent(@Payload InMessageImplTwo event) {
        System.out.println(event);
    }
} We use the kafkaListenerContainerFactory bean to configure our listener. This factory is described in KafkaConsumerConfiguration and looks like this: @Configuration
public class KafkaConsumerConfiguration {
    private final String SERVER;
    private final String SERVER_PORT;

    public KafkaConsumerConfiguration(
            @Value("${spring.cloud.stream.kafka.binder.brokers}") String server,
            @Value("${spring.cloud.stream.kafka.binder.defaultBrokerPort}") String port
    ) {
        this.SERVER = server;
        this.SERVER_PORT = port;
    }

    private <T> ConsumerFactory<String, T> typeConsumerFactory(Class<T> clazz) {
        Map<String, Object> props = new HashMap<>();
        props.put(ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG, String.format("%s:%s", SERVER, SERVER_PORT));

        return new DefaultKafkaConsumerFactory<>(
                props,
                new StringDeserializer(),
                new JsonDeserializer<>(clazz));
    }

    private <T> ConcurrentKafkaListenerContainerFactory<String, T> initFactory(Class<T> clazz) {
        ConcurrentKafkaListenerContainerFactory<String, T> factory =
                new ConcurrentKafkaListenerContainerFactory<>();
        factory.setConsumerFactory(typeConsumerFactory(clazz));
        return factory;
    }

    @Bean
    public ConcurrentKafkaListenerContainerFactory<String, ?> kafkaListenerContainerFactory() {
        return initFactory(InMessageAbstract.class);
    }
} Because we're adding a “Typeld” header to the message, we'll get the error described above when we try to deserialize. However, we can configure the JsonDeserializer manually. To do this, we must define our implementation of TypeMapper. The following shows how you can define your own TypeMappers. class CustomTypeMapper<T> extends DefaultJackson2JavaTypeMapper {
    private final Class<T> clazz;

    public CustomTypeMapper(Class<T> clazz) {
        this.clazz = clazz;
    }

    @Override
    public JavaType toJavaType(Headers headers) {
        try {
            return TypeFactory.defaultInstance()
                    .constructType(ClassUtils.forName(clazz.getName(), getClassLoader()));
        } catch (ClassNotFoundException e) {
            throw new RuntimeException(e);
        }
    }
} If we add our TypeMapper implementation to the JsonDeserializer when we create the factory, then we can force the Json to be deserialized to the class we need, ignoring the header. The corrected method would look like this: private <T> ConsumerFactory<String, T> typeConsumerFactory(Class<T> clazz) {
    Map<String, Object> props = new HashMap<>();
    props.put(ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG, String.format("%s:%s", SERVER, SERVER_PORT));

    JsonDeserializer<T> jsonDeserializer = new JsonDeserializer<>(clazz);
    jsonDeserializer.setTypeMapper(new CustomTypeMapper<>(clazz));

    return new DefaultKafkaConsumerFactory<>(
            props,
            new StringDeserializer(),
            jsonDeserializer);
} Conclusion By utilizing a custom type mapper in Spring Kafka, you can overcome the challenges associated with consuming messages from foreign providers that include a " " header. This article has provided a step-by-step guide to configuring and implementing the custom type mapper, enabling smooth message processing and avoiding serialization and deserialization exceptions. With this knowledge, you can confidently integrate with external systems and consume Kafka messages with different package structures. TypeId The full project code is available on GitHub: https://github.com/stepanovD/kafka-templates/tree/master/consumer-custom-type-mapper

Handling Custom Type Mapping in Kafka Listeners for Messages with "TypeId" Header

Don't have time to read all the on HackerNoon? No worries; we've got you covered - introducing the HackerNoon Tech Brief Podcasts! Now you can listen to your favorite HackerNoon writers on the go. Let’s dive in! amazing stories WTF is the Tech Brief? The is a HackerNoon Daily Digest delivered straight to your inbox. They are 100% customizable based on what topics you are interested in and the frequency with which you’d like to receive them: daily, weekly, or monthly. Tech Brief Once subscribed, you will get the latest stories from that topic, including their tl:dr and feature images, in your inbox. Tech Briefs are always customizable, changing with you and your interests. To modify them, you have two options: Visit your , and add or remove the tags that best suit your preferences. interests page Visit the and choose which overall topics briefings (if any) you want and how often you’d like to receive them. tech brief settings You have complete control over what goes to your inbox with HackerNoon - have fun with it! HackerNoon, Play Tech Brief! Our daily podcasts were created to keep you up-to-date with the latest tech news and insights. You’ll find content ranging from to to to , and more: startups business gaming programming Tech Companies Podcast Feed Web3 Podcast Feed Tech Stories Podcast Feed Science Podcast Feed Futurism Podcast Feed Media Podcast Feed Life Hacking Podcast Feed Finance Podcast Feed Writing Podcast Feed Society Podcast Feed Business Podcast Feed Startups Podcast Feed Management Podcast Feed Programming Podcast Feed Machine Learning Podcast Feed Product Management Podcast Feed Remote Work Podcast Feed Gaming Podcast Feed Cybersecurity Podcast Feed Data Science Podcast Feed Simply search for or wherever you get your podcasts. "HackerNoon Tech Brief" on Spotify

Listen to Tech Brief Podcasts on Your Headphones: Stay Connected to HackerNoon Anywhere, Anytime

আপনার হেডফোনগুলিতে টেক ব্রিফ পডকাস্টগুলি শুনুন: যে কোনও জায়গায়, যে কোনও সময় হ্যাকারনুন-এর সাথে সংযুক্ত থাকুন

Hören Sie sich Tech Brief-Podcasts über Ihre Kopfhörer an: Bleiben Sie überall und jederzeit mit HackerNoon in Verbindung

Escuche los podcasts de Tech Brief en sus auriculares: manténgase conectado a HackerNoon en cualquier lugar, en cualquier momento

Écoutez les podcasts Tech Brief sur vos écouteurs : restez connecté à HackerNoon n'importe où, n'importe quand

अपने हेडफ़ोन पर टेक संक्षिप्त पॉडकास्ट सुनें: कभी भी, कहीं भी हैकरनून से जुड़े रहें

ヘッドフォンで Tech Brief Podcast を聞く: いつでもどこでも HackerNoon に接続できます

헤드폰으로 기술 개요 팟캐스트 듣기: 언제 어디서나 HackerNoon에 연결 상태를 유지하세요

Ouça podcasts de resumo técnico em seus fones de ouvido: fique conectado ao HackerNoon em qualquer lugar, a qualquer hora

Teknik Özet Podcast'lerini Kulaklığınızdan Dinleyin: HackerNoon'a Her Yerde, Her Zaman Bağlantıda Kalın

Nghe Podcast tóm tắt về công nghệ trên tai nghe của bạn: Luôn kết nối với HackerNoon mọi lúc, mọi nơi

用耳机收听 Tech Brief 播客：随时随地与 HackerNoon 保持联系

(BI) tools are often the last stop of a data processing pipeline. It is where data is visualized for analysts who then extract insights from it. From the standpoint of a SaaS BI provider, what are we looking for in a database? In my job, we are in urgent need of support for fast-join queries. Business intelligence Why JOIN Query Matters I work as an engineer that supports a human resource management system. One prominent selling point of our services is . That means we allow users to customize their own dashboards: they can choose the fields they need and relate them to form the dataset as they want. self-service BI Join query is a more efficient way to realize self-service BI. It allows people to break down their data assets into many smaller tables instead of putting them all in a flat table. This would make data updates much faster and more cost-effective because updating the whole flat table is not always the optimal choice when you have plenty of new data flowing in and old data being updated or deleted frequently, as is the case for most data input. In order to maximize the time value of data, we need data updates to be executed really quickly. For this purpose, we looked into three OLAP databases on the market. They are all fast in some way but there are some differences. Greenplum is really quick in data loading and batch DML processing, but it is not good at handling high concurrency. There is a steep decline in performance as query concurrency rises. This can be risky for a BI platform that tries to ensure a stable user experience. ClickHouse is mind-blowing in single-table queries, but it only allows batch update and batch delete, so that's less timely. Welcome to JOIN Hell JOIN, my old friend JOIN, is always a hassle. Join queries are demanding for both engineers and the database system. Firstly, engineers must have a thorough grasp of the schema of all tables. Secondly, these queries are resource-intensive, especially when they involve large tables. Some of the reports on our platform entail join queries across up to 20 tables. Just imagine the mess. We tested our candidate OLAP engines with our common join queries and our most notorious slow queries. As the number of tables joined grows, we witness a widening performance gap between and ClickHouse. In most join queries, Apache Doris was about 5 times faster than ClickHouse. In terms of slow queries, Apache Doris responded to most of them within less than 1 second, while the performance of ClickHouse fluctuated within a relatively large range. Apache Doris And just like that, we decided to upgrade our data architecture with Apache Doris. Architecture that Supports Our BI Services Data Input: Our business data flows into DBLE, a distributed middleware based on MySQL. Then the DBLE binlogs are written into Flink, getting deduplicated, merged, and then put into Kafka. Finally, Apache Doris reads data from Kafka via its Routine Load approach. We apply the "delete" configuration in Routine Load to enable real-time deletion. The combination of Apache Flink and the idempotent write mechanism of Apache Doris is how we get exactly-once guarantee. We have a data size of billions of rows per table, and this architecture is able to finish data updates in one minute. In addition, taking advantage of Apache Kafka and the Routine Load method, we are able to shave the traffic peaks and maintain cluster stability. Kafka also allows us to have multiple consumers of data and recompute intermediate data by resetting the offsets. : Data Output As a self-service BI platform, we allow users to customize their own reports by configuring the rows, columns, and filters as they need. This is supported by Apache Doris with its capabilities in join queries. In total, we have 400 data tables, of which 50 has over 100 million rows. That adds up to a data size measured in TB. We put all our data into two Doris clusters on 40 servers. No Longer Stalled by Privileged Access Queries On our BI platform, privileged queries are often much slower than non-privileged queries. Timeout is often the case and even more so for queries on large datasets. Human resource data is subject to very strict and fine-grained access control policies. The role and position of users and the confidentiality level of data determine who has access to what (the data granularity here is up to fields in a table). Occasionally, we need to separately grant a certain privilege to a particular person. On top of that, we need to ensure data isolation between the multiple tenants on our platform. How does all this add to complexity in engineering? Any user who inputs a query on our BI platform must go through multi-factor authentication, and the authenticated information will all be inserted into the SQL via and then passed on to the OLAP engine. Therefore, the more fine-grained the privilege controls are, the longer the SQL will be, and the more time the OLAP system will spend on ID filtering. That's why our users are often tortured by high latency. in So how did we fix that? We use the in Apache Doris. Bloom Filter index By adding Bloom Filter indexes to the relevant ID fields, we improve the speed of privileged queries by 30% and basically eliminate timeout errors. Tips on when you should use the Bloom Filter index: For non-prefix filtering For and filters on a particular column in = For filtering on high-cardinality columns, such as UserID. In essence, the Bloom Filter index is used to check if a certain value exists in a dataset. There is no point in using the Bloom Filter index for a low-cardinality column, like "gender", for example, because almost every data block contains all the gender values. To All BI Engineers We believe self-service BI is the future in the BI landscape, just like is the future of artificial intelligence. Fast join queries are the way towards it, and the foregoing architectural upgrade is part of our ongoing effort to empower that. May there be less painful JOINs in the BI world. Cheers. AGI

Listen to That Poor BI Engineer: We Need Fast Joins

Catching signals from others is how we started communicating as human beings. It all started, of course, with our vocal cords. Then we moved to smoke signals for long-distance communication. At some point, we discovered radio waves and are still using them for contact. This article will describe how you can tune in using and an SDR dongle. Fedora Linux My journey I got interested in radio communication as a hobby when I was a kid, while my local club, LZ2KRS, was still a thing. I was so excited to be able to listen and communicate with people worldwide. It opened a whole new world for me. I was living in a communist country back then and this was a way to escape just for a bit. It also taught me about ethics and technology. Year after year my hobby grew and now, in the Internet era with all the cool devices you can use, it’s getting even more exciting. So I want to show you how to do it with Fedora Linux and a hardware dongle. What is Ham Radio Amateur Radio (ham radio) is a popular hobby and service that brings people, electronics, and communication together. People use ham radio to talk across town, worldwide, or even into space, without the Internet or cell phones. What’s SWLing? To broadcast with your ham radio or SDR system, you need to obtain a license from a governmental body. But to intercept signals and listen to the open communication between two amateur radio stations, you don’t need one. The term SWLing comes from the abbreviation of Short Wave Listener, where you listen to stations communicating in the shortwave bands between 3 and 30 MHz. This can be used for long-distance communication using the , a layer of the Earth’s atmosphere. ionosphere To get started, you don’t need a license. Still, I recommend getting yourself an SWL sign to identify yourself in a listening contest. These are competitions for categories like who will discover the most connections in a month or who can listen to contacts from each country in the world. How to get an SWL Sign? There are two options: Contact your national radio club and ask them to issue one for you. I got my Czech one, OK1-36568, after a few weeks. Join the community and request a sign there. Short Wave Amateur Radio Listening You will get more information and help from either of these locations if you get stuck in some fashion! QSL Cards You can also use your sign to send QSL cards via post or electronically. This is a great way to communicate with people worldwide and make friends. Per Wikipedia, A QSL card is a written confirmation of either a two-way radio communication between two amateur radio or citizens band stations; a one-way reception of a signal from an AM radio, FM radio, television, or shortwave broadcasting station; or the reception of a two-way radio communication by a third party listener (in our case). A typical QSL card is the same size and made from the same material as a regular postcard; most are sent through snail mail. Replace the radio receiver with your Fedora Linux The focal point of the ham radio hobby is the radio transmitter/receiver. Most of the time, enthusiasts build their radio from scratch, but this differs from what I will write about here. SDR A software-defined radio (SDR) system is a radio communication system that uses software for the modulation and demodulation of radio signals. In other words, a piece of hardware and software replaces a radio transmitter/receiver. This helps you discover more in a way you are familiar with – a User Interface with built-in functions instead of the limited interface of a radio receiver. My explanation oversimplifies things, so if you want to go deep and read more about SDR, here is an excellent start. SDR Set Up under Fedora Linux Choosing the proper hardware If you search the Internet for an SDR dongle, you’ll find many ideas depending on your budget. In this tutorial, I’ll work with the one I have, which works well under Fedora 37. A note: The dongle covers frequencies from 25MHz to 1750MHz, which doesn’t cover the Short Wave bands. You would need an additional device to listen to them. This is included in the package I linked above. Some other hardware providers offer all-in-one products. Check if the dongle is visible Before installing anything, detect whether Fedora Linux recognizes your USB dongle. I hope you didn’t buy a fake one :-). Use the following command to list the USB devices on your system. lsusb One of the output lines (in the case of Nooelec) should be Realtek Semiconductor Corp. RTL2838 DVB-T Now proceed by installing the software you need Fedora offers a set of tools and drivers packaged as a group. Even though you would not use all the components in this package from the beginning, I recommend installing it. You’ll have more software to play with. sudo dnf group install 'Electronic Lab' I advise you to explore what’s in the group by running this command: sudo dnf group info 'Electronic Lab' Now check if you have everything set up correctly by running: rtl_test You should see something like this: Do not forget to kill this process because the device will be busy and cannot be used in the next step. A simple Ctrl + c works. Gqrx You have the dongle already in your device’s USB port and all the software you need to get started. Now it’s time to intercept your first signal. Start the program called . Don’t be alarmed by the strange interface. You’ll get used to it. Gqrx Configure the I/O Device Screen From the “Device” Dropdown, select the ‘ .’ RealtekRTL2838.. Leave the rest untouched for the moment. If you don’t see your device there, click the “ ” button at the bottom of the screen. Device Scan When your device is selected, click “OK,” and the dialogue will close. Configure the frequency screen Before you start intercepting signals, ensure there is something out there that proves everything works correctly. Since the dongle covers the FM radio band as well, do this: Locate your favorite radio station’s frequency. Mine is 105MHZ Set it in the Frequency field Select WFM (stereo) in the “Mode” dropdown. If you don’t do this, you will hear a sound. not Play And now, you need to start the reception by clicking the “play button” in your main menu. You will see the frequency visualized like this: If you hear a sound, everything will move to the next step. Check if everything is set up correctly if you don't hear anything. You may ask a question in the comments for this article; I can direct you to the proper forum to solve this. Feel free to play with some more FM broadcasts. You have the antenna for it in your pack. Let’s go Short Wave In the case of the Nooelec, you need to add one more device to the USB dongle and turn it on. Instructions on how to do that are included in the package you receive. In short, you plug the “Up Converter” into your USB dongle and make sure the switch is in the “convert” position. Some videos are available on how to do it if you get stuck. You will need an antenna and a good location Now things get trickier. If you live in an area where you don’t see an open space out your window or other buildings surrounding your building, you might have trouble catching a Short Wave radio amateur signal. Let’s try this to see if it works Try to be in the open. I usually listen from my terrace, which could be better but works under particular conditions. You would need a long wire to act as your antenna apart from the hardware. Try the antenna with the hardware initially – the telescoping one from , but it will catch only powerful signals. Nooelec Let’s go back to Gqrx Now with the converter, you need to make some changes to your device screen: Please note the – for the . This is required for the Up Converter to work. 125Mhz LNB LO field Tune your frequency to 14.100 Mhz and make sure your Mode is (standing for ) because this is this band’s main demodulation option. USB Upper sideband Then go to your screen, use the zoom slider, and set it to see about . In our case, you should have between 14.05 to 14.15 Mhz on your screen. FFT Settings 100 kHz Also, click the “ ” to see the information about the SW bands you are exploring. Enable Band Plan Then hit the play button and explore the space between 14.0 and 14.3 Mhz to get any amateur radio transmission. When intercepting a transmission, adjust your settings to improve your listening experience. It’s a journey that you have already started. Most probably, you will hear something like this: “CQ CQ CQ this is ..(followed by the radio license number spelled with the ). ham radio phonetic alphabet Listen very carefully, and by the call sign, you can determine the location of the radio amateurs’ country. You can visit the to learn more about them and even send them a QSL card confirming their connection. QRZCQ website . Keep the momentum going Now you have some tools and ideas for starting Short Wave Listening. This is the first step of an incredible and exciting journey you can have together with your Fedora Linux OS. You will discover the pleasure of , reading more about , how to be a part of a listening competition, and what mean. building your antenna for the specific band how the ionosphere helps those Q-codes This article was initially published in Fedora Magazine

LISTEN

listen.limited

-- employees

Since n.d.

COMPANY RANKING

LISTEN

EVERGREEN INDEX #6774

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

Listen WIKI

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

LISTEN

listen.limited

-- employees

Since n.d.

COMPANY RANKING

LISTEN

EVERGREEN INDEX #6774

RELATED COMPANIESRANK

STORIES ABOUT LISTEN

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

Listen WIKI

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