BARK is a fast-growing company serving dogs and the humans who love them

BARK

bark

After my latest post about how to build your own RAG and run it locally, today, we're taking it a step further by not only implementing the conversational abilities of large language models but also adding listening and speaking capabilities. The idea is straightforward: we are going to create a voice assistant reminiscent of Jarvis or Friday from the iconic Iron Man movies, which can operate offline on your computer. Since this is an introductory tutorial, I will implement it in Python and keep it simple enough for beginners. Lastly, I will provide some guidance on how to scale the application. Techstack First, you should set up a virtual Python environment. You have several options for this, including pyenv, virtualenv, poetry, and others that serve a similar purpose. Personally, I'll use Poetry for this tutorial due to my personal preferences. Here are several crucial libraries you'll need to install: : For a visually appealing console output. rich : A robust tool for speech-to-text conversion. openai-whisper : A cutting-edge library for text-to-speech synthesis, ensuring high-quality audio output. suno-bark : A straightforward library for interfacing with Large Language Models (LLMs). langchain , , and : Essential for audio recording and playback. sounddevice pyaudio speechrecognition For a detailed list of dependencies, refer to the link . here The most critical component here is the Large Language Model (LLM) backend, for which we will use Ollama. is widely recognized as a popular tool for running and serving LLMs offline. If Ollama is new to you, I recommend checking out my previous article on offline RAG: Basically, you just need to download the Ollama application, pull your preferred model, and run it. Ollama "Build Your Own RAG and Run It Locally: Langchain + Ollama + Streamlit." Architecture Okay, if everything has been set up, let's proceed to the next step. Below is the overall architecture of our application, which fundamentally comprises 3 main components: : Utilizing , we convert spoken language into text. Whisper's training on diverse datasets ensures its proficiency across various languages and dialects. Speech Recognition OpenAI's Whisper : For the conversational capabilities, we'll employ the Langchain interface for the model, which is served using Ollama. This setup promises a seamless and engaging conversational flow. Conversational Chain Llama-2 : The transformation of text to speech is achieved through , a state-of-the-art model from Suno AI, renowned for its lifelike speech production. Speech Synthesizer Bark The workflow is straightforward: record speech, transcribe to text, generate a response using an LLM, and vocalize the response using Bark. Sequence diagram for voice assistant with Whisper, Ollama, and Bark. Implementation The implementation begins with crafting a based on Bark, incorporating methods for synthesizing speech from text and handling longer text inputs seamlessly as follows: TextToSpeechService import nltk
import torch
import warnings
import numpy as np
from transformers import AutoProcessor, BarkModel

warnings.filterwarnings(
    "ignore",
    message="torch.nn.utils.weight_norm is deprecated in favor of torch.nn.utils.parametrizations.weight_norm.",
)


class TextToSpeechService:
    def __init__(self, device: str = "cuda" if torch.cuda.is_available() else "cpu"):
        """
        Initializes the TextToSpeechService class.
        Args:
            device (str, optional): The device to be used for the model, either "cuda" if a GPU is available or "cpu".
            Defaults to "cuda" if available, otherwise "cpu".
        """
        self.device = device
        self.processor = AutoProcessor.from_pretrained("suno/bark-small")
        self.model = BarkModel.from_pretrained("suno/bark-small")
        self.model.to(self.device)

    def synthesize(self, text: str, voice_preset: str = "v2/en_speaker_1"):
        """
        Synthesizes audio from the given text using the specified voice preset.
        Args:
            text (str): The input text to be synthesized.
            voice_preset (str, optional): The voice preset to be used for the synthesis. Defaults to "v2/en_speaker_1".
        Returns:
            tuple: A tuple containing the sample rate and the generated audio array.
        """
        inputs = self.processor(text, voice_preset=voice_preset, return_tensors="pt")
        inputs = {k: v.to(self.device) for k, v in inputs.items()}

        with torch.no_grad():
            audio_array = self.model.generate(**inputs, pad_token_id=10000)

        audio_array = audio_array.cpu().numpy().squeeze()
        sample_rate = self.model.generation_config.sample_rate
        return sample_rate, audio_array

    def long_form_synthesize(self, text: str, voice_preset: str = "v2/en_speaker_1"):
        """
        Synthesizes audio from the given long-form text using the specified voice preset.
        Args:
            text (str): The input text to be synthesized.
            voice_preset (str, optional): The voice preset to be used for the synthesis. Defaults to "v2/en_speaker_1".
        Returns:
            tuple: A tuple containing the sample rate and the generated audio array.
        """
        pieces = []
        sentences = nltk.sent_tokenize(text)
        silence = np.zeros(int(0.25 * self.model.generation_config.sample_rate))

        for sent in sentences:
            sample_rate, audio_array = self.synthesize(sent, voice_preset)
            pieces += [audio_array, silence.copy()]

        return self.model.generation_config.sample_rate, np.concatenate(pieces) : The class takes an optional parameter, which specifies the device to be used for the model (either if a GPU is available, or ). It loads the Bark model and the corresponding processor from the pre-trained model. You can also use the large version by specifying for the model loader. Initialization ( __init__ ) device cuda cpu suno/bark-small suno/bark : This method takes a input and a parameter, which specifies the voice to be used for the synthesis. You can check out other value . It uses the to prepare the input text and the voice preset, and then generates the audio array using the method. The generated audio array is converted to a NumPy array and the sample rate is returned along with the audio array. Synthesize ( synthesize ) text voice_preset voice_preset here processor model.generate() : This method is used for synthesizing longer text inputs. It first tokenizes the input text into sentences using the function. For each sentence, it calls the method to generate the audio array. It then concatenates the generated audio arrays, with a short silence (0.25 seconds) added between each sentence. Long-form Synthesize ( long_form_synthesize ) nltk.sent_tokenize synthesize Now that we have the set up, we need to prepare the Ollama server for the large language model (LLM) serving. To do this, you'll need to follow these steps: TextToSpeechService : Run the following command to download the latest Llama-2 model from the Ollama repository: Pull the latest Llama-2 model ollama pull llama2 . : If the server is not yet started, execute the following command to start it: . Start the Ollama server ollama serve Once you've completed these steps, your application will be able to use the Ollama server and the Llama-2 model to generate responses to user input. Next, we'll move to the main application logic. First, we need to initialize the following components: : We'll use the Rich library to create a better interactive console for the user within the terminal. Rich Console : We'll initialize a Whisper speech recognition model which is a state-of-the-art open-source speech recognition system developed by OpenAI. We'll use the base English model ( ) for transcribing user input. Whisper Speech-to-Text base.en : We'll initialize a Bark text-to-speech synthesizer instance, which was implemented above. Bark Text-to-Speech : We'll use the built-in from the Langchain library which provides a template for managing the conversational flow. We'll configure it to use the Llama-2 language model with the Ollama backend. Conversational Chain ConversationalChain import time
import threading
import numpy as np
import whisper
import sounddevice as sd
from queue import Queue
from rich.console import Console
from langchain.memory import ConversationBufferMemory
from langchain.chains import ConversationChain
from langchain.prompts import PromptTemplate
from langchain_community.llms import Ollama
from tts import TextToSpeechService

console = Console()
stt = whisper.load_model("base.en")
tts = TextToSpeechService()

template = """
You are a helpful and friendly AI assistant. You are polite, respectful, and aim to provide concise responses of less 
than 20 words.
The conversation transcript is as follows:
{history}
And here is the user's follow-up: {input}
Your response:
"""
PROMPT = PromptTemplate(input_variables=["history", "input"], template=template)
chain = ConversationChain(
    prompt=PROMPT,
    verbose=False,
    memory=ConversationBufferMemory(ai_prefix="Assistant:"),
    llm=Ollama(),
) Now, let's define the necessary functions: : This function runs in a separate thread to capture audio data from the user's microphone using the . The callback function is called whenever new audio data is available, and it puts the data into a for further processing. record_audio sounddevice.RawInputStream data_queue : This function utilizes the Whisper instance to transcribe the audio data from the into text. transcribe data_queue : This function feeds the current conversation context to the Llama-2 language model (via the Langchain ) and retrieves the generated text response. get_llm_response ConversationalChain : This function takes the audio waveform generated by the Bark text-to-speech engine and plays it back to the user using a sound playback library (e.g., ). play_audio sounddevice def record_audio(stop_event, data_queue):
    """
    Captures audio data from the user's microphone and adds it to a queue for further processing.
    Args:
        stop_event (threading.Event): An event that, when set, signals the function to stop recording.
        data_queue (queue.Queue): A queue to which the recorded audio data will be added.
    Returns:
        None
    """
    def callback(indata, frames, time, status):
        if status:
            console.print(status)
        data_queue.put(bytes(indata))

    with sd.RawInputStream(
        samplerate=16000, dtype="int16", channels=1, callback=callback
    ):
        while not stop_event.is_set():
            time.sleep(0.1)

def transcribe(audio_np: np.ndarray) -> str:
    """
    Transcribes the given audio data using the Whisper speech recognition model.
    Args:
        audio_np (numpy.ndarray): The audio data to be transcribed.
    Returns:
        str: The transcribed text.
    """
    result = stt.transcribe(audio_np, fp16=False)  # Set fp16=True if using a GPU
    text = result["text"].strip()
    return text

def get_llm_response(text: str) -> str:
    """
    Generates a response to the given text using the Llama-2 language model.
    Args:
        text (str): The input text to be processed.
    Returns:
        str: The generated response.
    """
    response = chain.predict(input=text)
    if response.startswith("Assistant:"):
        response = response[len("Assistant:") :].strip()
    return response

def play_audio(sample_rate, audio_array):
    """
    Plays the given audio data using the sounddevice library.
    Args:
        sample_rate (int): The sample rate of the audio data.
        audio_array (numpy.ndarray): The audio data to be played.
    Returns:
        None
    """
    sd.play(audio_array, sample_rate)
    sd.wait() Then, we define the main application loop. The main application loop guides the user through the conversational interaction as follows: The user is prompted to press Enter to start recording their input. Once the user presses Enter, the function is called in a separate thread to capture the user's audio input. record_audio When the user presses Enter again to stop the recording, the audio data is transcribed using the function. transcribe The transcribed text is then passed to the function, which generates a response using the Llama-2 language model. get_llm_response The generated response is printed to the console and played back to the user using the function. play_audio if __name__ == "__main__":
    console.print("[cyan]Assistant started! Press Ctrl+C to exit.")

    try:
        while True:
            console.input(
                "Press Enter to start recording, then press Enter again to stop."
            )

            data_queue = Queue()  # type: ignore[var-annotated]
            stop_event = threading.Event()
            recording_thread = threading.Thread(
                target=record_audio,
                args=(stop_event, data_queue),
            )
            recording_thread.start()

            input()
            stop_event.set()
            recording_thread.join()

            audio_data = b"".join(list(data_queue.queue))
            audio_np = (
                np.frombuffer(audio_data, dtype=np.int16).astype(np.float32) / 32768.0
            )

            if audio_np.size > 0:
                with console.status("Transcribing...", spinner="earth"):
                    text = transcribe(audio_np)
                console.print(f"[yellow]You: {text}")

                with console.status("Generating response...", spinner="earth"):
                    response = get_llm_response(text)
                    sample_rate, audio_array = tts.long_form_synthesize(response)

                console.print(f"[cyan]Assistant: {response}")
                play_audio(sample_rate, audio_array)
            else:
                console.print(
                    "[red]No audio recorded. Please ensure your microphone is working."
                )

    except KeyboardInterrupt:
        console.print("\n[red]Exiting...")

    console.print("[blue]Session ended.") Result Once everything is put down together, we can run the application as shown in the video above. The application runs quite slowly on my MacBook because the Bark model is large, even in its smaller version. Therefore, I have slightly sped up the video. For those with a CUDA-enabled computer, it might run faster. Here are the key features of our application: : Users can start and stop recording their voice input, and the assistant responds by playing back the generated audio. Voice-based interaction The assistant maintains the context of the conversation, enabling more coherent and relevant responses. The use of the Llama-2 language model allows the assistant to provide concise and focused responses. Conversational context: For those aiming to elevate this application to a production-ready status, the following enhancements are recommended: : Incorporate optimized versions of the models, such as whisper.cpp, llama.cpp, and bark.cpp, which are designed to boost performance, especially on lower-end computers. Performance Optimization : Implement a system that allows users to customize the bot's persona and prompt, enabling the creation of different types of assistants (e.g., personal, professional, or domain-specific). Customizable Bot Prompts : Develop a user-friendly GUI to enhance the overall user experience, making the application more accessible and visually appealing. Graphical User Interface (GUI) : Expand the application to support multimodal interactions, such as the ability to generate and display images, diagrams, or other visual content in addition to the voice-based responses. Multimodal Capabilities Finally, we have completed our simple voice assistant application, full code can be found at: . This combination of speech recognition, language modeling, and text-to-speech technologies demonstrates how we can build something that sounds difficult but can actually run on your computer. Let's enjoy coding, and don't forget to subscribe to so you don't miss the latest in AI and programming articles. https://github.com/vndee/local-talking-llm my blog Also published here

How to Build Your Own Voice Assistant and Run it Locally Using Whisper + Ollama + Bark

কীভাবে আপনার নিজের ভয়েস সহকারী তৈরি করবেন এবং হুইস্পার + ওল্লামা + বার্ক ব্যবহার করে স্থানীয়ভাবে এটি চালাবেন

So erstellen Sie Ihren eigenen Sprachassistenten und führen ihn lokal mit Whisper + Ollama + Bark aus

Cómo crear su propio asistente de voz y ejecutarlo localmente usando Whisper + Ollama + Bark

Comment créer votre propre assistant vocal et l'exécuter localement à l'aide de Whisper + Ollama + Bark

अपना खुद का वॉयस असिस्टेंट कैसे बनाएं और इसे व्हिस्पर + ओलामा + बार्क का उपयोग करके स्थानीय रूप से कैसे चलाएं

独自の音声アシスタントを構築し、Whisper + Ollama + Bark を使用してローカルで実行する方法

나만의 음성 어시스턴트를 구축하고 Whisper + Ollama + Bark를 사용하여 로컬에서 실행하는 방법

Como construir seu próprio assistente de voz e executá-lo localmente usando Whisper + Ollama + Bark

Как создать собственный голосовой помощник и запустить его локально с помощью Whisper + Ollama + Bark

Kendi Sesli Asistanınızı Oluşturma ve Whisper + Ollama + Bark Kullanarak Yerel Olarak Çalıştırma

Cách xây dựng trợ lý giọng nói của riêng bạn và chạy nó cục bộ bằng Whisper + Ollama + Bark

如何构建您自己的语音助手并使用 Whisper + Ollama + Bark 在本地运行

Abandoned by Jules Verne, is part of the HackerNoon Books Series. You can jump to any chapter in this book . CHAPTER II here CHAPTER II First Trial of the Canoe—A Wreck on the Coast—Towing—Flotsam Point—Inventory of the Case: Tools, Weapons, Instruments, Clothes, Books, Utensils—What Pencroft misses—The Gospel—A Verse from the Sacred Book. On the 9th of October the bark canoe was entirely finished. Pencroft had kept his promise, and a light boat, the shell of which was joined together by the flexible twigs of the crejimba, had been constructed in five days. A seat in the stern, a second seat in the middle to preserve the equilibrium, a third seat in the bows, rowlocks for the two oars, a scull to steer with, completed the little craft, which was twelve feet long, and did not weigh more than 200 pounds. The operation of launching it was extremely simple. The canoe was carried to the beach and laid on the sand before Granite House, and the rising tide floated it. Pencroft, who leapt in directly, manœuvred it with the scull and declared it to be just the thing for the purpose to which they wished to put it. "Hurrah!" cried the sailor, who did not disdain to celebrate thus his own triumph. "With this we could go round—" "The world?" asked Gideon Spilett. "No, the island. Some stones for ballast, a mast, and a sail, which the captain will make for us some day, and we shall go splendidly! Well, captain—and you, Mr. Spilett; and you, Herbert; and you, Neb—aren't you coming to try our new vessel? Come along! we must see if it will carry all five of us!" This was certainly a trial which ought to be made. Pencroft soon brought the canoe to the shore by a narrow passage among the rocks, and it was agreed that they should make a trial of the boat that day by following the shore as far as the first point at which the rocks of the south ended. As they embarked, Neb cried,— "But your boat leaks rather, Pencroft." "That's nothing, Neb," replied the sailor; "the wood will get seasoned. In two days there won't be a single leak, and our boat will have no more water in her than there is in the stomach of a drunkard. Jump in!" They were soon all seated, and Pencroft shoved off. The weather was magnificent, the sea as calm as if its waters were contained within the narrow limits of a lake. Thus the boat could proceed with as much security as if it was ascending the tranquil current of the Mercy. Neb took one of the oars, Herbert the other, and Pencroft remained in the stern in order to use the skull. The sailor first crossed the channel, and steered close to the southern point of the islet. A light breeze blew from the south. No roughness was found either in the channel or the green sea. A long swell, which the canoe scarcely felt, as it was heavily laden, rolled regularly over the surface of the water. They pulled out about half a mile distant from the shore, that they might have a good view of Mount Franklin. Pencroft afterwards returned towards the mouth of the river. The boat then skirted the shore, which, extending to the extreme point, hid all Tadorn's Fens. This point, of which the distance was increased by the irregularity of the coast, was nearly three miles from the Mercy. The settlers resolved to go to its extremity, and only go beyond it as much as was necessary to take a rapid survey of the coast as far as Claw Cape. The canoe followed the windings of the shore, avoiding the rocks which fringed it, and which the rising tide began to cover. The cliff gradually sloped away from the mouth of the river to the point. This was formed of granite rocks, capriciously distributed, very different from the cliff at Prospect Heights, and of an extremely wild aspect. It might have been said that an immense cartload of rocks had been emptied out there. There was no vegetation on this sharp promontory, which projected two miles from the forest, and it thus represented a giant's arm stretched out from a leafy sleeve. The canoe, impelled by the two oars, advanced without difficulty. Gideon Spilett, pencil in one hand and note-book in the other, sketched the coast in bold strokes. Neb, Herbert, and Pencroft chatted, whilst examining this part of their domain, which was new to them, and, in proportion as the canoe proceeded towards the south, the two Mandible Capes appeared to move, and surround Union Bay more closely. As to Cyrus Harding, he did not speak; he simply gazed, and by the mistrust which his look expressed, it appeared that he was examining some strange country. In the meanwhile, after a voyage of three quarters of an hour, the canoe reached the extremity of the point, and Pencroft was preparing to return, when Herbert, rising, pointed to a black object, saying,— "What do I see down there on the beach?" All eyes turned towards the point indicated. "Why," said the reporter, "there is something. It looks like part of a wreck half buried in the sand." "Ah!" cried Pencroft, "I see what it is!" "What?" asked Neb. "Barrels, barrels, which perhaps are full," replied the sailor. "Pull to the shore, Pencroft!" said Cyrus. A few strokes of the oar brought the canoe into a little creek, and its passengers leapt on shore. Pencroft was not mistaken. Two barrels were there, half buried in the sand, but still firmly attached to a large chest, which, sustained by them, had floated to the moment when it stranded on the beach. "There has been a wreck, then, in some part of the island," said Herbert. "Evidently," replied Spilett. "But what's in this chest?" cried Pencroft, with very natural impatience. "What's in this chest? It is shut up, and nothing to open it with! Well, perhaps a stone—" And the sailor, raising a heavy block, was about to break in one of the sides of the chest, when the engineer arrested his hand. "Pencroft," said he, "can you restrain your impatience for one hour only?" "But, captain, just think! Perhaps there is everything we want in there!" "We shall find that out, Pencroft," replied the engineer; "but trust to me, and do not break the chest, which may be useful to us. We must convey it to Granite House, where we can open it easily and without breaking it. It is quite prepared for a voyage, and, since it has floated here, it may just as well float to the mouth of the river." "You are right, captain, and I was wrong, as usual," replied the sailor. The engineer's advice was good. In fact, the canoe probably would not have been able to contain the articles possibly enclosed in the chest, which doubtless was heavy, since two empty barrels were required to buoy it up. It was, therefore, much better to tow it to the beach at Granite House. And now, whence had this chest come? That was the important question Cyrus Harding and his companions looked attentively around them, and examined the shore for several hundred steps. No other articles or pieces of wreck could be found. Herbert and Neb climbed a high rock to survey the sea, but there was nothing in sight—neither a dismasted vessel nor a ship under sail. However, there was no doubt that there had been a wreck Perhaps this incident was connected with that of the bullet? Perhaps strangers had landed on another part of the island? Perhaps they were still there? But the thought which came naturally to the settlers was, that these strangers could not be Malay pirates, for the chest was evidently of American or European make. All the party returned to the chest, which was of an unusually large size. It was made of oak wood, very carefully closed and covered with a thick hide, which was secured by copper nails. The two great barrels, hermetically sealed, but which sounded hollow and empty, were fastened to its sides by strong ropes knotted with a skill which Pencroft directly pronounced sailors alone could exhibit. It appeared to be in a perfect state of preservation, which was explained by the fact that it had stranded on a sandy beach, and not among rocks. They had no doubt whatever, on examining it carefully, that it had not been long in the water, and that its arrival on this coast was recent. The water did not appear to have penetrated to the inside, and the articles which it contained were no doubt uninjured. It was evident that this chest had been thrown overboard from some dismasted vessel driven towards the island, and that, in the hope that it would reach the land, where they might afterwards find it, the passengers had taken the precaution to buoy it up by means of this floating apparatus. "We will tow this chest to Granite House," said the engineer, "where we can make an inventory of its contents, then, if we discover any of the survivors from the supposed wreck, we can return it to those to whom it belongs. If we find no one—" "We will keep it for ourselves!" cried Pencroft "But what in the world can there be in it?" The sea was already approaching the chest, and the high tide would evidently float it. One of the ropes which fastened the barrels was partly unlashed and used as a cable to unite the floating apparatus with the canoe. Pencroft and Neb then dug away the sand with their oars, so as to facilitate the moving of the chest, towing which the boat soon began to double the point to which the name of Flotsam Point was given. The chest was heavy, and the barrels were scarcely sufficient to keep it above water. The sailor also feared every instant that it would get loose and sink to the bottom of the sea. But happily his fears were not realised, and an hour and a half after they set out—all that time had been taken up in going a distance of three miles—the boat touched the beach below Granite House. Canoe and chest were then hauled up on the sand, and as the tide was then going out, they were soon left high and dry. Neb, hurrying home, brought back some tools with which to open the chest in such a way that it might be injured as little as possible, and they proceeded to its inventory. Pencroft did not try to hide that he was greatly excited. The sailor began by detaching the two barrels, which, being in good condition, would of course be of use. Then the locks were forced with a cold chisel and hammer, and the lid thrown back. A second casing of zinc lined the interior of the chest, which had been evidently arranged that the articles which it enclosed might under any circumstances be sheltered from damp. "Oh!" cried Neb, "suppose it's jam!". "I hope not," replied the reporter. "If only there was—" said the sailor in a low voice. "What?" asked Neb, who overheard him. "Nothing!" The covering of zinc was torn off and thrown back over the sides of the chest, and by degrees numerous articles of very varied character were produced and strewn about on the sand. At each new object Pencroft uttered fresh hurrahs, Herbert clapped his hands, and Neb danced—like a nigger. There were books which made Herbert wild with joy, and cooking utensils which Neb covered with kisses! In short, the colonists had reason to be extremely satisfied, for this chest contained tools, weapons, instruments, clothes, books; and this is the exact list of them as stated in Gideon Spilett's note-book:— Tools:—3 knives with several blades, 2 woodmen's axes, 2 carpenter's hatchets, 3 planes, 2 adzes, 1 twibil or mattock, 6 chisels, 2 files, 3 hammers, 3 gimlets, 2 augers, 10 bags of nails and screws, 3 saws of different sizes, 2 boxes of needles. Weapons:—2 flint-lock guns, 2 for percussion caps, 2 breech-loader carbines, 5 boarding cutlasses, 4 sabres, 2 barrels of powder, each containing twenty-five pounds; 12 boxes of percussion caps. Instruments:—1 sextant, 1 double opera-glass, 1 telescope, 1 box of mathematical instruments, 1 mariner's compass, 1 Fahrenheit thermometer, 1 aneroid barometer, 1 box containing a photographic apparatus, object-glass, plates, chemicals, etc. Clothes:—2 dozen shirts of a peculiar material resembling wool, but evidently of a vegetable origin; 3 dozen stockings of the same material. Utensils:—1 iron pot, 6 copper saucepans, 3 iron dishes, 10 metal plates, 2 kettles, 1 portable stove, 6 table-knives. Books:—1 Bible, 1 atlas, 1 dictionary of the different Polynesian idioms, 1 dictionary of natural science, in six volumes; 3 reams of white paper, 2 books with blank pages. "It must be allowed," said the reporter, after the inventory had been made, "that the owner of this chest was a practical man! Tools, weapons, instruments, clothes, utensils, books—nothing is wanting! It might really be said that he expected to be wrecked, and had prepared for it beforehand." "Nothing is wanting, indeed," murmured Cyrus Harding thoughtfully. "And for a certainty," added Herbert, "the vessel which carried this chest and its owner was not a Malay pirate!" "Unless," said Pencroft, "the owner had been taken prisoner by pirates—" "That is not admissible," replied the reporter. "It is more probable that an American or European vessel has been driven into this quarter, and that her passengers, wishing to save necessaries at least, prepared this chest and threw it overboard." "Is that your opinion, captain?" asked Herbert. "Yes, my boy," replied the engineer, "that may have been the case. It is possible that at the moment, or in expectation of a wreck, they collected into this chest different articles of the greatest use in hopes of finding it again on the coast—" "Even the photographic box!" exclaimed the sailor incredulously. "As to that apparatus," replied Harding, "I do not quite see the use of it; and a more complete supply of clothes or more abundant ammunition would have been more valuable to us as well as to any other castaways!" "But isn't there any mark or direction on these instruments, tools, or books, which would tell us something about them?" asked Gideon Spilett. That might be ascertained. Each article was carefully examined, especially the books, instruments and weapons. Neither the weapons nor the instruments, contrary to the usual custom, bore the name of the maker; they were, besides, in a perfect state, and did not appear to have been used. The same peculiarity marked the tools and utensils; all were new, which proved that the articles had not been taken by chance and thrown into the chest, but, on the contrary, that the choice of the things had been well considered and arranged with care. This was also indicated by a second case of metal which had preserved them from damp, and which could not have been soldered in a moment of haste. As to the dictionaries of natural science and Polynesian idioms, both were English, but they neither bore the name of the publisher nor the date of publication. The same with the Bible printed in English, in quarto, remarkable in a typographical point of view, and which appeared to have been often used. The atlas was a magnificent work, comprising maps of every country in the world, and several planispheres arranged upon Mercator's projection, aid of which the nomenclature was in French—but which also bore neither date nor name of publisher. There was nothing, therefore, on these different articles by which they could be traced and nothing consequently of a nature to show the nationality of the vessel which must have recently passed these shores. But, wherever the chest might have come from, it was a treasure to the settlers on Lincoln Island. Till then, by making use of the productions of nature, they had created everything for themselves, and, thanks to their intelligence, they had managed without difficulty. But did it not appear as if Providence had wished to reward them by sending them these productions of human industry? Their thanks rose unanimously to Heaven. However, one of them was not quite satisfied: it was Pencroft. It appeared that the chest did not contain some thing which he evidently held in great esteem, for in proportion as they approached the bottom of the box, his hurrahs diminished in heartiness, and, the inventory finished, he was heard to mutter these words— "That's all very fine, but you can see that there is nothing for me in that box!" This led Neb to say,— "Why, friend Pencroft, what more do you expect?" "Half a pound of tobacco," replied Pencroft seriously, "and nothing would have been wanting to complete my happiness." No one could help laughing at this speech of the sailor's. But the result of this discovery of the chest was, that it was more than ever necessary to explore the island thoroughly. It was therefore agreed that the next morning at break of day they should set out, by ascending the Mercy so as to reach the western shore. If any castaways had landed on the coast, it was to be feared they were without resources, and it was therefore the more necessary to carry help to them without delay. During the day the different articles were carried to Granite House, where they were methodically arranged in the great hall. This day—the 29th of October—happened to be a Sunday, and, before going to bed, Herbert asked the engineer if he would not read them something from the Gospel. "Willingly," replied Cyrus Harding. He took the sacred volume, and was about to open it, when Pencroft stopped him, saying,— "Captain, I am superstitious. Open at random and read the first verse which your eye falls upon. We will see if it applies to our situation." Cyrus Harding smiled at the sailor's idea, and, yielding to his wish, he opened exactly at a place where the leaves were separated by a marker. Immediately his eyes were attracted by a cross which, made with a pencil, was placed against the eighth verse of the seventh chapter of the Gospel of St. Matthew. He read the verse, which was this:— "For every one that asketh receiveth; and he that seeketh findeth." 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 (2010). Abandoned. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/cache/epub/33516/pg33516-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

On the 9th of October the bark canoe was entirely finished

Realistic Text-to-Speech Voice Synthesis: Comparing Tortoise and Bark

Hello, loyal readers! After republishing my first Women in Information series from last fall, I’m now ready to republish my second series from this spring. These interviews have proven to be really popular, and I’m honoured to bring them to Hacker Noon. Security I will do a third series for Fall 2017. If you’re a woman or non-male who works in , or you know someone who is, cybersecurity feel free to tweet me about it! I have who help to encourage my unpaid writing. Most of my writing for corporate blogs, and my writing for Peerlyst is paid, but this isn’t. If you enjoy pieces like this, my Patreon support helps make it possible. , even for only a couple of bucks per month, and I’ll greatly appreciate it. six Patreon supporters Consider becoming a patron This was originally published on Tripwire’s State of Security blog in April. My of interviews on women (and non-males) in information security was really popular. I spoke to some amazing minds in the cybersecurity field last fall. As spring arrived, I figured that there are probably a lot more professionals in our field who also have interesting stories to tell. last series Encouraging more non-males to enter the industry will inevitably benefit cybersecurity as a whole. In resuming my series, hopefully more readers will be inspired. This time, I spoke to . She owns , for which she blogs about news and ideas regarding the human element of cybersecurity. Human beings are the greatest vulnerability, after all! Since 2013, she has run her own firm, J L Barker Ltd., and she recently co-founded Redacted Firm. She is engaged by organisations of all sizes, from multi-national firms to SMEs. She has also appeared at important security events, such as and . Dr. Jessica Barker Cyber.uk SteelCon 2016 Infosecurity Europe 2016 So you run Cyber.uk. What compelled you to start that venture? Kim Crawley: I wanted a place to write accessible articles on cybersecurity that people of any level of knowledge or understanding could hopefully engage with and get something from if they are interested in the subject. I do research from time to time, where I generally look at attitudes and behaviours online. For example, I surveyed 1,000 people in the UK about their attitudes towards biometrics replacing passwords; 1,000 people about whether they know of 2FA; and 3,000 people in the UK, US and Germany about their opinions of Edward Snowden’s actions. Dr. Jessica Barker: I think that’s a great motive. Ignorance of cybersecurity is harming laypeople, and they need knowledge. KC: I totally agree. I think there is an onus on us in the cybersecurity profession to communicate more effectively about our work, the threats online, and what people and organizations can do to better protect themselves. JB: I try to write most of my articles with technical laypeople in mind. But when my non-IT friends read my articles, they say that they’re still difficult to understand. Educating end users can be a challenge. I really appreciate how you recognize human beings as the most significant vulnerabilty. KC: We all get used to the language of our profession and can become detached from the level of understanding that most people have when it comes to the internet, security and privacy. JB: Yes, I think you’re exactly correct. A lot of laypeople don’t even know the word “malware.” KC: You’re absolutely right about malware. I was on a pretty popular radio show in the UK (the on BBC Radio 2) talking about ransomware. Even with my perspective and determination to keep in touch with what the average person knows about security, I was shocked at how low awareness of ransomware is. We all know in the industry that it’s one of the biggest threats at the moment and has been that way for a while. But most people haven’t heard of it. JB: Jeremy Vine Show That’s incredible considering that I’ve seen ransomware in Windows clients since a decade ago. I had to deal with consumers freaking out about it. KC: I think the greatest misconception laypeople have about “hacking” is that they believe how it’s depicted in Hollywood. A “hacker” typing commands into a terminal at 300 words per minute overlooks the fact that social engineering is such a major attack method. Yes, I agree. I work with organizations on social engineering awareness, and it’s interesting to see how shocked people are by what we can find out about them via some OSINT and how that could be used in an attack. Most people still think hacking is about targeting technology and are not aware of the extent to which people are targeted. JB: Very true. Now let’s shift gears a bit. I notice that you gave a talk about impostor syndrome at SteelCon last year. Do you think women get it more frequently? KC: It’s tough. A lot of people in the industry struggle with it. I’ve had to work on my own issues with imposter syndrome, so that I don’t let it hold me back. Instead, I use it as a motivator. The danger then, of course, is burnout. I think it impacts a lot of people in this industry because cybersecurity is so diverse. It’s impossible to know everything, and we can become desensitised to how much we do know about our own area of expertise. So, you meet someone else and in conversation with them think, “They know so much more than me,” all the while forgetting that they have their own area of expertise, as you have yours. JB: I also think that most people in the industry have a personality trait whereby they want to keep learning and keep challenging themselves — which is great, but it can mean people sometimes feel like there is a lot of stuff they don’t know. There are also some cultural issues, which a lot of people commented about when I did a bit of research on it. We have a tendency in this community to tear people down if they don’t know something or get something wrong. People often say that women get imposter syndrome more frequently, but I don’t agree, to be honest. Studies have implied that in the past, but I think that could be because women are more likely to talk about it than men. From my research and conversations I’ve had with friends and colleagues in the industry, men can struggle with it just as much as women. That sums up why we all need to encourage each other in the industry. As much as there can be a culture of tearing people down, there are also a lot of people who will build others up, be supportive, and be encouraging. We need more of those people. Well said! It’s clear you’ve spoken at a lot of cons. What was your first con speaking experience? How did you prepare? How did you feel? How did the opportunity arise? KC: I think the first con I spoke at was Manchester BSides four years ago. I was speaking at events before that, on panels, and at more corporate events. But I think that was my first community con. I was approached by one of the organizers, which was great and really gave me the encouragement that I needed. I gave the closing keynote and spoke about the psychology of fear and cybersecurity. To be honest, I was really nervous speaking to a technical audience about something that’s so human-focused. The response was great, and I was pleased to find that people were genuinely interested in the human side of cybersecurity. Around that same time, I spoke at SteelCon about how to communicate cybersecurity messages more effectively, and at IRISSCon about gender and age differences in cybersecurity attitudes and behaviours. JB: I start prep for all my talks in the same way, which is to create a spider diagram on paper of all the key points I want to cover. Or sometimes I use a whiteboard or Post-It notes. I then flesh out all of the points before I start on the slides. I used to script my talks and then rehearse them until I had learned them. But as I’ve gotten more experience and more confidence, I no longer do that. I now prefer to think of the talks as more of a conversation I’m having with the audience. I will know the key point I want to make on each slide and overall for the talk. But I don’t script them, and I practice to some extent but without rehearsing so much. Did speaking at cons get easier as you got more experience? KC: Cons have definitely gotten easier as I’ve gotten more experience, more confidence, and more understanding of the fact that even technical audiences are interested in the human side of cybersecurity. JB: That’s very different than what I did. For BSides Toronto, I made a PowerPoint presentation from research notes, then I discussed each slide spontaneously. It was amazing that I kept to the 20-minute time limit. I was co-presenting with my ex-husband, and he was going to go on a tangent on a totally unrelated topic. I had to stop him and redirect the presentation to the subject matter. KC: Everyone has their own style I think, and after a while, they find what works best for them, which is why giving advice to others can be tricky. JB: Definitely. Now on to another gender-related question. In previous blogs, I mentioned that I’ve found I’ve been discriminated against less often in cybersecurity than in my earlier jobs due to my gender. What has your experience been? KC: I’ve found the same, too. I definitely experienced more discrimination when I was just starting out in the industry than I do now. I don’t know if that’s because things are progressing or because we are more likely to face discrimination when we are in more junior positions and less established in the industry. Or maybe it’s because we know the industry better now and know which people, companies, and events to avoid! JB: Yeah, I agree. Sexism is less of a problem, but it’s still there. I’ve been pleased by how many women and transgender people I’ve met in our field, and articles like these help. KC: Very true. JB: I have to say, I find the topic of your talk at BSides London last year interesting. The history of the word “cyber.” I wrote an for Tripwire on the differences, similarities and origins of the concepts of information security, cybersecurity, computer security, etc. recently. I think sometimes people lose sight of the “meta” stuff, the cultural stuff. KC: article Thanks. That’s an example of a talk I’d been thinking about for a year or so before I did it. I felt like I was putting my head above the parapet with that one because a lot of people in the community obviously hate the word “cyber,” which I understand but think we need to move on from. JB: I found that when I was talking to senior executives or people in the media or the general public, they related to “cybersecurity” so much more than “information security.” And although they technically have their own distinct definitions, we often use them interchangeably. So, I wanted to look at the cultural issues around the language we use and encourage people to address the fact that cyber is the word people outside of the industry relate to. I did some research and found that most people in the community refer to what we do as “information security” but most people in the public call it “cybersecurity.” In fact, more people in the public call what we do “e-security” than “information security.” When we’re trying to raise awareness and change behaviours, the language we use really matters. E-security? I’ve never heard of that term. Is it more common in the UK? KC: Not at all! It really surprised me, too, because I have never heard anyone actually use the term. JB: Wow. That’s amazing. I would have thought information security was more common. On another note, what advantages do you believe there are to people who don’t identify as male (women, nonbinary people) being in cybersecurity? How do you think we uniquely benefit the industry? KC: For me, it comes down to talent, representation and fairness. First and foremost, talent is equally distributed among the population; it does not discriminate. So, when groups are discriminated against or not equally represented in an industry, that industry is missing out on the talent that those individuals could provide. We deal with some really complicated issues in cyber security, and we need that talent to address those problems. Having diversity also facilitates the representation of different world views and different experiences. People with different life experiences will come at problems differently. JB: Diversity also breeds diversity, so from a representation point of view, the more diversity we have the more that sends a message that “you can do it too.” From a fairness point of view, this is a really cool industry to work in, and I want people who would be interested in the field and who would contribute to it to know they are welcome regardless of their gender identity or any other factor! That’s an excellent answer. One final question… What do you think the greatest challenges will be in cybersecurity in the coming years? KC: I think we will continue to struggle with the same problems we have for decades, like patching, legacy systems, shadow IT, and of course human behaviour. But with the pace of technological change (or rather, the pace of change in how we use technology) continuing to grow so rapidly, we face the risk of still being challenged with how to keep up. With more connectivity comes more vulnerability, and so, of course, the is a big challenge that will continue to grow. Engaging with the average person, enabling them to understand the security and privacy concerns with, for example, “smart” devices in the home, is a big challenge. Responsibility for security with regards to the Internet of Things is a tricky issue. We need security built-in from the start, but in a global market with no incentive on manufacturers to do this, we are placing too much responsibility on consumers. Responsibility for cybersecurity is not a new issue, like most of the issues we deal with in cybersecurity, but as our use of the internet continues to grow, the challenges will also grow. JB: Internet of Things Excellent! It’s been a pleasure chatting with you. I’ve learned a lot. KC:

Women in Information Security: Dr. Jessica Barker

How to Use PHP Attributes to Create and Use a Custom Validator in Symfony

Seller Inventory Recommendations Enhanced by Expert Knowledge Graph with Large Language Model

Facebook. Where do I even begin with this colossal junkyard of a platform? It's like someone took the concept of social networking and doused it in a vat of incompetence. Let's talk about how Facebook has managed to mess up beyond all common sense. Firstly, their idea of content moderation seems to be more about randomly throwing darts at a board than actually using any sort of coherent logic. Legitimate posts in perfectly innocuous groups are being whisked away into the digital ether while spam proliferates like a disease. Seriously, how does a post about genuine advice or a thoughtful discussion get flagged and removed, but the umpteenth spammy post for shady sunglasses or miracle weight loss pills in totally irrelevant groups get a free pass? It's like Facebook has an algorithm that's not just broken but actively malicious. Facebook cares more about profit margins than the user experience. Instead of fostering a community where people can share meaningful ideas and connect on a genuine level, they've turned it into a virtual junkyard where the loudest, most obnoxious, spammy advertisers and paid-to-post parasites reign supreme. What happened to valuing quality over quantity? Now, it's all about how many eyeballs they can shove in front of spammy URL posts or advertisements, regardless of whether those eyeballs are seeing something worthwhile or utter garbage. It's a race to the bottom where meaningful content is drowned out by an endless barrage of clickbait. And let's not forget the privacy nightmares. Facebook has more tentacles in your personal life than an overbearing mother-in-law. They track your every move, every click, every like, and probably your wet dreams if they could. Remember when Facebook was caught red-handed with plans to sell user data and received support from Facebook’s most senior executives, including CEO Mark Zuckerberg and chief operating officer Sheryl Sandberg? Yeah, that happened, and somehow, we're all still here, feeding the beast with our personal information. According to approximately 4,000 pages of leaked internal documents obtained by NBC News, Zuckerberg allegedly supervised strategies aimed at centralizing the social network's influence and stifling competitors by using user data as leverage. This occurred despite public assurances from the company about protecting user data. The documents primarily cover the years 2011 to 2015. Facebook’s (Meta) latest spam joke Case in point: I joined a Facebook group dedicated to blogging and guest posting. Perfect, right? Wrong. I posted a meticulously crafted message with a URL, offering insightful tips on how to craft a perfect guest post. What did Facebook do? They promptly removed my post, citing some obscure community guideline violation. Meanwhile, the same group was inundated with spam posts about irrelevant topics, worthless websites, and other scammers, hawked by individuals paid to spread digital garbage like confetti at a clown convention. Facebook has lost its way. Digital Nonsense It's crystal clear that Facebook has lost its way. They seem more interested in padding their profits than ensuring a quality user experience. Maybe they're scrimping on competent programmers because their algorithms can't tell the difference between genuine content and spammy trash. There are better options out there, folks. Platforms that actually give a damn about quality and fairness. They know how to handle spam: swiftly and decisively, with bans and suspensions flying like justice from a vigilant sheriff. Meanwhile, Facebook twiddles its thumbs, letting the spammers run amok like unruly toddlers in a toy store. It's time for a change It's time for a change. Governments should consider banning this digital travesty of a platform. We deserve better. We deserve platforms that respect our time, our data, and our intelligence. Facebook had its chance. It's time to let it fade into irrelevance, like the distant memory of a regrettable haircut or Myspace. Facebook could have been a force for good - Instead, it’s a spam-loving machine The saddest part is that Facebook could have been a force for good. It could have been a platform where people from all walks of life could come together, share ideas, and foster genuine connections. Instead, it's a bloated, soulless husk of what it could have been—a place where spam rules and meaningful interaction is a rare gem buried under layers of digital detritus. Facebook is a joke Facebook is a joke—a sad, outdated relic in the age of superior social media alternatives. Let's move on, shall we? There's a whole world of digital connectivity out there, waiting for us to embrace platforms that actually value what matters. Facebook's love affair with scammers Facebook's love affair with scammers is a textbook example of corporate greed overshadowing ethical responsibility. They don't just turn a blind eye to scammers; they roll out the red carpet for them. It's like they have a special VIP section reserved for shady operators peddling everything from fake diplomas, get-rich-quick schemes, dodgy products and digital services. It's like they're saying, "Scam away, folks! Just make sure the ad revenue keeps flowing." They rake in cash hand over fist while unsuspecting users fall victim to schemes that would make even the most seasoned con artist blush. Facebook doesn't care. And the best part? Facebook doesn't care. They're too busy counting their ill-gotten gains to bother with pesky details like vetting advertisers or ensuring the legitimacy of promoted services. Who cares if someone's promoting a Ponzi scheme or selling snake oil disguised as miracle cures? Certainly not Facebook, as long as those sweet advertising dollars keep pouring in. Facebook's revenue - Willful ignorance Let's face it: a substantial chunk of Facebook's revenue likely comes from scammers. I mean, do they even bother to check? The obvious answer is no. It's the digital equivalent of renting out billboard space to a carnival barker without asking what's under the tent. They're complicit, whether through negligence or willful ignorance. So, while the rest of us navigate the internet with caution, Facebook gleefully lines its pockets with ad click money earned from the misfortune of others. It's a disgrace, a betrayal of trust, and a stark reminder that when it comes to ethics, Facebook is MIA. Facebook's laissez-faire attitude towards scammy and spammy advertisers is not just irresponsible—it's reprehensible. They owe their users better. They owe the digital community better. It’s time our governments finally put a stop to this mayhem. Hence why I have decided to start my own movement, a reporting agency that finds, responds to and reports every scam we come across. Then, provide a database every month to my national government that reflects the reported scams Meta refuses to remove after being reported. A visionary will emerge - Sooner than you think! Someday, a visionary will emerge—someone smarter, bolder, and more ethical than Zuckerberg and his cohort of profit-driven enablers. This visionary will revolutionize social media, leaving Facebook (or Meta, as they now call it) in the dust. (Watch this space) Picture this: a platform where authenticity reigns supreme. Only real people, genuine advertisers, and vetted content are allowed. No more scams, no more clickbait, no more shady dealings. It's a place where integrity is not just a buzzword but a guiding principle. This new social media titan will prioritize user safety and privacy above all else. Children will be protected, personal data will be guarded like a treasure, and transparency will be the cornerstone of every interaction. Imagine a digital space where users can connect, share, and thrive without fear of exploitation or deception. And yes, this platform will make money. But unlike Facebook, its success won't come at the expense of its users' trust. It will be a fair exchange where value is delivered without compromising principles. Advertising will be relevant and respectful, enhancing the user experience rather than detracting from it.  It’s coming, believe me. Maybe sooner than you think. Meta, beware. The winds of change are blowing, and it's only a matter of time until you become the next Myspace—a relic of a bygone era. The future belongs to those who innovate with integrity and prioritize the well-being of their community. So, brace yourself because the revolution is coming, and when it arrives, the world will finally have a social media platform worthy of its users. So, Facebook, if you're listening (which you probably are because, let's face it, you're always listening), get your act together. Clean up your act. Start valuing quality content and user experience over your bottom line driven by spam and scams. Stop treating us like commodities to be sold to the highest bidder. Until then, I'll be over here, trying to salvage what's left of my faith in social media. And maybe, just maybe, hoping for a platform that actually gives a damn about its legitimate users instead of spammers and scammers. It's time they cleaned up their act and started prioritizing integrity over profit, and governments start handing out major penalties Until then, caveat emptor: let the buyer beware, especially when it comes to anything Facebook promotes on its junkyard of depict, spam and filth. Facebook. Where do I even begin with this colossal junkyard of a platform? It's like someone took the concept of social networking and doused it in a vat of incompetence. Let's talk about how Facebook has managed to mess up beyond all common sense. Firstly, their idea of content moderation seems to be more about randomly throwing darts at a board than actually using any sort of coherent logic. Legitimate posts in perfectly innocuous groups are being whisked away into the digital ether while spam proliferates like a disease. Seriously, how does a post about genuine advice or a thoughtful discussion get flagged and removed, but the umpteenth spammy post for shady sunglasses or miracle weight loss pills in totally irrelevant groups get a free pass? It's like Facebook has an algorithm that's not just broken but actively malicious. Facebook cares more about profit margins than the user experience. Instead of fostering a community where people can share meaningful ideas and connect on a genuine level, they've turned it into a virtual junkyard where the loudest, most obnoxious, spammy advertisers and paid-to-post parasites reign supreme. What happened to valuing quality over quantity? Now, it's all about how many eyeballs they can shove in front of spammy URL posts or advertisements, regardless of whether those eyeballs are seeing something worthwhile or utter garbage. It's a race to the bottom where meaningful content is drowned out by an endless barrage of clickbait. And let's not forget the privacy nightmares. Facebook has more tentacles in your personal life than an overbearing mother-in-law. They track your every move, every click, every like, and probably your wet dreams if they could. Remember when Facebook was caught red-handed with plans to sell user data and received support from Facebook’s most senior executives, including CEO Mark Zuckerberg and chief operating officer Sheryl Sandberg? Yeah, that happened, and somehow, we're all still here, feeding the beast with our personal information. plans to sell user data According to approximately 4,000 pages of leaked internal documents obtained by NBC News, Zuckerberg allegedly supervised strategies aimed at centralizing the social network's influence and stifling competitors by using user data as leverage. This occurred despite public assurances from the company about protecting user data. The documents primarily cover the years 2011 to 2015. Facebook’s (Meta) latest spam joke Case in point: I joined a Facebook group dedicated to blogging and guest posting. Perfect, right? Wrong. I posted a meticulously crafted message with a URL, offering insightful tips on how to craft a perfect guest post . guest post What did Facebook do? What did Facebook do? They promptly removed my post, citing some obscure community guideline violation. Meanwhile, the same group was inundated with spam posts about irrelevant topics, worthless websites, and other scammers , hawked by individuals paid to spread digital garbage like confetti at a clown convention. spam posts other scammers Facebook has lost its way. Digital Nonsense It's crystal clear that Facebook has lost its way. They seem more interested in padding their profits than ensuring a quality user experience. Maybe they're scrimping on competent programmers because their algorithms can't tell the difference between genuine content and spammy trash. There are better options out there, folks. Platforms that actually give a damn about quality and fairness. They know how to handle spam: swiftly and decisively, with bans and suspensions flying like justice from a vigilant sheriff. Meanwhile, Facebook twiddles its thumbs, letting the spammers run amok like unruly toddlers in a toy store. It's time for a change It's time for a change. Governments should consider banning this digital travesty of a platform. We deserve better. We deserve platforms that respect our time, our data, and our intelligence. Facebook had its chance. It's time to let it fade into irrelevance, like the distant memory of a regrettable haircut or Myspace. Facebook could have been a force for good - Instead, it’s a spam-loving machine Facebook could have been a force for good - Instead, it’s a spam-loving machine The saddest part is that Facebook could have been a force for good. It could have been a platform where people from all walks of life could come together, share ideas, and foster genuine connections. Instead, it's a bloated, soulless husk of what it could have been—a place where spam rules and meaningful interaction is a rare gem buried under layers of digital detritus. Facebook Facebook is a joke Facebook is a joke—a sad, outdated relic in the age of superior social media alternatives. Let's move on, shall we? There's a whole world of digital connectivity out there, waiting for us to embrace platforms that actually value what matters. Facebook's love affair with scammers Facebook's love affair with scammers is a textbook example of corporate greed overshadowing ethical responsibility. They don't just turn a blind eye to scammers; they roll out the red carpet for them. It's like they have a special VIP section reserved for shady operators peddling everything from fake diplomas, get-rich-quick schemes, dodgy products and digital services. love affair with scammers shady operators fake It's like they're saying, "Scam away, folks! Just make sure the ad revenue keeps flowing." They rake in cash hand over fist while unsuspecting users fall victim to schemes that would make even the most seasoned con artist blush. Facebook doesn't care. And the best part? Facebook doesn't care. They're too busy counting their ill-gotten gains to bother with pesky details like vetting advertisers or ensuring the legitimacy of promoted services. Who cares if someone's promoting a Ponzi scheme or selling snake oil disguised as miracle cures? Certainly not Facebook, as long as those sweet advertising dollars keep pouring in. Facebook's revenue - Willful ignorance Let's face it: a substantial chunk of Facebook's revenue likely comes from scammers. I mean, do they even bother to check? The obvious answer is no. It's the digital equivalent of renting out billboard space to a carnival barker without asking what's under the tent. They're complicit, whether through negligence or willful ignorance. So, while the rest of us navigate the internet with caution, Facebook gleefully lines its pockets with ad click money earned from the misfortune of others. It's a disgrace, a betrayal of trust, and a stark reminder that when it comes to ethics, Facebook is MIA. Facebook's laissez-faire attitude towards scammy and spammy advertisers is not just irresponsible—it's reprehensible. They owe their users better. They owe the digital community better. It’s time our governments finally put a stop to this mayhem. Hence why I have decided to start my own movement, a reporting agency that finds, responds to and reports every scam we come across. Then, provide a database every month to my national government that reflects the reported scams Meta refuses to remove after being reported. the reported scams A visionary will emerge - Sooner than you think! Someday, a visionary will emerge—someone smarter, bolder, and more ethical than Zuckerberg and his cohort of profit-driven enablers. This visionary will revolutionize social media, leaving Facebook (or Meta, as they now call it) in the dust. (Watch this space) Picture this: a platform where authenticity reigns supreme. Only real people, genuine advertisers, and vetted content are allowed. No more scams, no more clickbait, no more shady dealings. It's a place where integrity is not just a buzzword but a guiding principle. authenticity content This new social media titan will prioritize user safety and privacy above all else. Children will be protected, personal data will be guarded like a treasure, and transparency will be the cornerstone of every interaction. Imagine a digital space where users can connect, share, and thrive without fear of exploitation or deception. And yes, this platform will make money. But unlike Facebook, its success won't come at the expense of its users' trust. It will be a fair exchange where value is delivered without compromising principles. Advertising will be relevant and respectful, enhancing the user experience rather than detracting from it.  It’s coming, believe me. Maybe sooner than you think. Meta, beware. The winds of change are blowing, and it's only a matter of time until you become the next Myspace—a relic of a bygone era. The future belongs to those who innovate with integrity and prioritize the well-being of their community. So, brace yourself because the revolution is coming, and when it arrives, the world will finally have a social media platform worthy of its users. So, Facebook, if you're listening (which you probably are because, let's face it, you're always listening), get your act together. Clean up your act. Start valuing quality content and user experience over your bottom line driven by spam and scams. Stop treating us like commodities to be sold to the highest bidder. Until then, I'll be over here, trying to salvage what's left of my faith in social media. And maybe, just maybe, hoping for a platform that actually gives a damn about its legitimate users instead of spammers and scammers. It's time they cleaned up their act and started prioritizing integrity over profit, and governments start handing out major penalties Until then, caveat emptor: let the buyer beware, especially when it comes to anything Facebook promotes on its junkyard of depict, spam and filth.

Facebook Has Managed To Mess Up Beyond All Common Sense. A Social Media Nightmare 

Authors:
(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org);
(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Related Work Description of LCM Attacker Model and Security Goals LCMSec: The Proposed Protocol Implementation and Evaluation Conclusion Appendix and References APPENDIX A. Two attacks on the Dutta-Barua group key agreement Zhang et al. present two attacks on the DBGKA protocol [23]. To fully understand them and this section, some understanding of the Dutta-Barua protocol [17] is required. While a full review of the protocol is out of scope for this work, for the purposes of this section, the most important thing is to understand that each KeyAgree() and Join() operation is associated with an instance id d. This instance id is incremented for each of those operations and can never be reused. Note that d can be regarded as a nonce: while it is not random, it is never reused. Another example of a protocol that uses non-random nonces is Wireguard [24]. Both attacks described by Zhang et al. are carried out by one or multiple malicious users who are part of the Dutta-Barua group, that is they have successfully participated in the DuttaBarua key agreement in the past. In this sense, the premise of the DBGKA is already violated: The DBGKA protocol provides no security against malicious insiders. Nevertheless, one should take this form of attack seriously: An honest user - representing, for instance, an IoT device - might at some point be compromised and become dishonest. Alternatively, he might have been dishonest all along, but his certificate is only revoked at a later stage. We will therefore discuss both attacks and show why they pose no threat to the LCMsec protocol. 1) First Attack: The first attack is carried out by a malicious leaving user who has been part of a previous successful DuttaBarua KeyAgreement() operation during which he has made some preparation for the attack by storing some of the protocol messages. When the Leave() operation is executed to expel this user from the group, Zhang et. al. show that the attacker can compute the new session key using the values he stored earlier. However, as we understand the DBGKA, the purpose of the Leave() operation is not to expel dishonest users, but as a way for honest users to leave. When an honest user leaves in this way, it is possible for the remaining users to efficiently agree on a new key. If an honest user, on the other hand, does not execute the Leave() operation, a new KeyAgreement() operation has to performed, which is a lot less efficient for large groups. To expel a malicious user, the remaining users instead execute the KeyAgree() operation amongst themselves – this way, the attack is bypassed entirely. Note that in the current version of LCMsec, we do not include a mechanism for certificate revocation or expelling users from the group and make no use of the Leave() operation, so this attack does not concern us. Still, the ability to add such a feature in the future is important. As we discussed, this can be done safely by using the KeyAgree() operation whenever a certificate is revoked. REFERENCES [1] P. T. Eugster, P. A. Felber, R. Guerraoui, and A.-M. Kermarrec, “The many faces of publish/subscribe,” ACM Computing Surveys, vol. 35, no. 2, pp. 114–131, Jun. 2003. [2] A. S. Huang, E. Olson, and D. C. Moore, “LCM: Lightweight Communications and Marshalling,” in 2010 IEEE/RSJ International Conference on Intelligent Robots and Systems, pp. 4057–4062. [3] R. Canetti, J. Garay, G. Itkis, D. Micciancio, M. Naor, and B. Pinkas, “Multicast security: A taxonomy and some efficient constructions,” in IEEE INFOCOM ’99. Conference on Computer Communications. Proceedings. Eighteenth Annual Joint Conference of the IEEE Computer and Communications Societies. The Future Is Now (Cat. No.99CH36320), pp. 708–716 vol.2. [4] “Message Queuing Telemetry Transport.” [Online]. Available: https: //mqtt.org/ [5] G. Pardo-Castellote, “OMG Data-Distribution Service: Architectural overview,” in 23rd International Conference on Distributed Computing Systems Workshops, 2003. Proceedings., May 2003, pp. 200–206. [6] S. E. Deering, “Host extensions for IP multicasting,” Internet Engineering Task Force, Request for Comments RFC 1112, Aug. 1989. [7] E. Onica, P. Felber, H. Mercier, and E. Riviere, “Towards Scalable ` and Dependable Privacy-Preserving Publish/Subscribe Services,” in Fast Abstract in the 46th Annual IEEE/IFIP International Conference on Dependable Systems and Networks, M. Roy, J. A. Lopez, and A. Casimiro, Eds., Toulouse, France, Jun. 2016. [8] S. Bernard, M. G. Potop-Butucaru, and S. Tixeuil, “A Framework for Secure and Private P2P Publish/Subscribe,” in Stabilization, Safety, and Security of Distributed Systems, ser. Lecture Notes in Computer Science, S. Dolev, J. Cobb, M. Fischer, and M. Yung, Eds., pp. 531–545. [9] L. Malina, G. Srivastava, P. Dzurenda, J. Hajny, and R. Fujdiak, “A Secure Publish/Subscribe Protocol for Internet of Things,” in Proceedings of the 14th International Conference on Availability, Reliability and Security, ser. ARES ’19, pp. 1–10. [10] M. Ion, G. Russello, and B. Crispo, “Supporting Publication and Subscription Confidentiality in Pub/Sub Networks,” in Security and Privacy in Communication Networks, ser. Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, S. Jajodia and J. Zhou, Eds., pp. 272–289. [11] M. Hamad, E. Regnath, J. Lauinger, V. Prevelakis, and S. Steinhorst, “SPPS: Secure Policy-based Publish/Subscribe System for V2C Communication,” in 2021 Design, Automation & Test in Europe Conference & Exhibition (DATE), Feb. 2021, pp. 529–534. [12] M. Dahlmanns, J. Pennekamp, I. B. Fink, B. Schoolmann, K. Wehrle, and M. Henze, “Transparent End-to-End Security for Publish/Subscribe Communication in Cyber-Physical Systems,” in Proceedings of the 2021 ACM Workshop on Secure and Trustworthy Cyber-Physical Systems, ser. SAT-CPS ’21, pp. 78–87. [13] iMatix Corporation, “ZeroMQ Broker vs . Brokerless Messaging - Whitepaper.” [Online]. Available: http://wiki.zeromq.org/whitepapers: brokerless [14] iMatix Corporation, “CurveZMQ - a protocol for secure messaging across the Internet,” Jan. 2023. [Online]. Available: http://rfc.zeromq. org/spec/26/ [15] Object Management Group, “DDS Security Specification,” Jun. 2018. [Online]. Available: https://www.omg.org/spec/DDS-SECURITY/1.1/ PDF [16] J. Kim, J. M. Smereka, C. Cheung, S. Nepal, and M. Grobler, “Security and Performance Considerations in ROS 2: A Balancing Act,” Sep. 2018. [Online]. Available: http://arxiv.org/abs/1809.09566 [17] R. Dutta and R. Barua, “Provably Secure Constant Round Contributory Group Key Agreement in Dynamic Setting,” IEEE Transactions on Information Theory, vol. 54, no. 5, pp. 2007–2025, May 2008. [18] D. Ongaro and J. Ousterhout, “In search of an understandable consensus algorithm,” in Proceedings of the 2014 USENIX Conference on USENIX Annual Technical Conference, ser. USENIX ATC’14, pp. 305–320. [19] M. J. Dworkin, “Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC,” NIST, Nov. 2007. [20] R. Atkinson and S. Kent, “Security Architecture for the Internet Protocol,” Internet Engineering Task Force, Request for Comments RFC 2401, Nov. 1998. [21] T. T. T. ZOU) and X. Zhang, “IPsec Anti-Replay Algorithm without Bit Shifting,” Internet Engineering Task Force, Request for Comments RFC 6479, Jan. 2012. [22] S. Boeyen, S. Santesson, T. Polk, R. Housley, S. Farrell, and D. Cooper, “Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,” Internet Engineering Task Force, Request for Comments RFC 5280, May 2008. [23] H. Zhang, C. Xu, C. Li, and A. R. Sangi, “Two Attacks on Dutta’s Dynamic Group Key Agreement Protocol,” in Wireless Communications and Applications, ser. Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, P. Senac, M. Ott, and A. Seneviratne, Eds., pp. 419–425. ´ [24] J. A. Donenfeld, “WireGuard: Next Generation Kernel Network Tunnel,” in Proceedings 2017 Network and Distributed System Security Symposium. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Authors: Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Abstract and Introduction Related Work Related Work Description of LCM Description of LCM Attacker Model and Security Goals Attacker Model and Security Goals LCMSec: The Proposed Protocol LCMSec: The Proposed Protocol Implementation and Evaluation Implementation and Evaluation Conclusion Conclusion Appendix and References Appendix and References APPENDIX A. Two attacks on the Dutta-Barua group key agreement A. Two attacks on the Dutta-Barua group key agreement Zhang et al. present two attacks on the DBGKA protocol [23]. To fully understand them and this section, some understanding of the Dutta-Barua protocol [17] is required. While a full review of the protocol is out of scope for this work, for the purposes of this section, the most important thing is to understand that each KeyAgree() and Join() operation is associated with an instance id d. This instance id is incremented for each of those operations and can never be reused. Note that d can be regarded as a nonce: while it is not random, it is never reused. Another example of a protocol that uses non-random nonces is Wireguard [24]. Both attacks described by Zhang et al. are carried out by one or multiple malicious users who are part of the Dutta-Barua group, that is they have successfully participated in the DuttaBarua key agreement in the past. In this sense, the premise of the DBGKA is already violated: The DBGKA protocol provides no security against malicious insiders. Nevertheless, one should take this form of attack seriously: An honest user - representing, for instance, an IoT device - might at some point be compromised and become dishonest. Alternatively, he might have been dishonest all along, but his certificate is only revoked at a later stage. We will therefore discuss both attacks and show why they pose no threat to the LCMsec protocol. 1) First Attack : The first attack is carried out by a malicious leaving user who has been part of a previous successful DuttaBarua KeyAgreement() operation during which he has made some preparation for the attack by storing some of the protocol messages. When the Leave() operation is executed to expel this user from the group, Zhang et. al. show that the attacker can compute the new session key using the values he stored earlier. 1) First Attack DuttaBarua KeyAgreement() Leave() However, as we understand the DBGKA, the purpose of the Leave() operation is not to expel dishonest users, but as a way for honest users to leave. When an honest user leaves in this way, it is possible for the remaining users to efficiently agree on a new key. If an honest user, on the other hand, does not execute the Leave() operation, a new KeyAgreement() operation has to performed, which is a lot less efficient for large groups. To expel a malicious user, the remaining users instead execute the KeyAgree() operation amongst themselves – this way, the attack is bypassed entirely. Leave() Leave() KeyAgreement() KeyAgree() Note that in the current version of LCMsec, we do not include a mechanism for certificate revocation or expelling users from the group and make no use of the Leave() operation, so this attack does not concern us. Still, the ability to add such a feature in the future is important. As we discussed, this can be done safely by using the KeyAgree() operation whenever a certificate is revoked. Leave() KeyAgree() REFERENCES [1] P. T. Eugster, P. A. Felber, R. Guerraoui, and A.-M. Kermarrec, “The many faces of publish/subscribe,” ACM Computing Surveys, vol. 35, no. 2, pp. 114–131, Jun. 2003. [2] A. S. Huang, E. Olson, and D. C. Moore, “LCM: Lightweight Communications and Marshalling,” in 2010 IEEE/RSJ International Conference on Intelligent Robots and Systems, pp. 4057–4062. [3] R. Canetti, J. Garay, G. Itkis, D. Micciancio, M. Naor, and B. Pinkas, “Multicast security: A taxonomy and some efficient constructions,” in IEEE INFOCOM ’99. Conference on Computer Communications. Proceedings. Eighteenth Annual Joint Conference of the IEEE Computer and Communications Societies. The Future Is Now (Cat. No.99CH36320), pp. 708–716 vol.2. [4] “Message Queuing Telemetry Transport.” [Online]. Available: https: //mqtt.org/ [5] G. Pardo-Castellote, “OMG Data-Distribution Service: Architectural overview,” in 23rd International Conference on Distributed Computing Systems Workshops, 2003. Proceedings., May 2003, pp. 200–206. [6] S. E. Deering, “Host extensions for IP multicasting,” Internet Engineering Task Force, Request for Comments RFC 1112, Aug. 1989. [7] E. Onica, P. Felber, H. Mercier, and E. Riviere, “Towards Scalable ` and Dependable Privacy-Preserving Publish/Subscribe Services,” in Fast Abstract in the 46th Annual IEEE/IFIP International Conference on Dependable Systems and Networks, M. Roy, J. A. Lopez, and A. Casimiro, Eds., Toulouse, France, Jun. 2016. [8] S. Bernard, M. G. Potop-Butucaru, and S. Tixeuil, “A Framework for Secure and Private P2P Publish/Subscribe,” in Stabilization, Safety, and Security of Distributed Systems, ser. Lecture Notes in Computer Science, S. Dolev, J. Cobb, M. Fischer, and M. Yung, Eds., pp. 531–545. [9] L. Malina, G. Srivastava, P. Dzurenda, J. Hajny, and R. Fujdiak, “A Secure Publish/Subscribe Protocol for Internet of Things,” in Proceedings of the 14th International Conference on Availability, Reliability and Security, ser. ARES ’19, pp. 1–10. [10] M. Ion, G. Russello, and B. Crispo, “Supporting Publication and Subscription Confidentiality in Pub/Sub Networks,” in Security and Privacy in Communication Networks, ser. Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, S. Jajodia and J. Zhou, Eds., pp. 272–289. [11] M. Hamad, E. Regnath, J. Lauinger, V. Prevelakis, and S. Steinhorst, “SPPS: Secure Policy-based Publish/Subscribe System for V2C Communication,” in 2021 Design, Automation & Test in Europe Conference & Exhibition (DATE), Feb. 2021, pp. 529–534. [12] M. Dahlmanns, J. Pennekamp, I. B. Fink, B. Schoolmann, K. Wehrle, and M. Henze, “Transparent End-to-End Security for Publish/Subscribe Communication in Cyber-Physical Systems,” in Proceedings of the 2021 ACM Workshop on Secure and Trustworthy Cyber-Physical Systems, ser. SAT-CPS ’21, pp. 78–87. [13] iMatix Corporation, “ZeroMQ Broker vs . Brokerless Messaging - Whitepaper.” [Online]. Available: http://wiki.zeromq.org/whitepapers: brokerless [14] iMatix Corporation, “CurveZMQ - a protocol for secure messaging across the Internet,” Jan. 2023. [Online]. Available: http://rfc.zeromq. org/spec/26/ [15] Object Management Group, “DDS Security Specification,” Jun. 2018. [Online]. Available: https://www.omg.org/spec/DDS-SECURITY/1.1/ PDF [16] J. Kim, J. M. Smereka, C. Cheung, S. Nepal, and M. Grobler, “Security and Performance Considerations in ROS 2: A Balancing Act,” Sep. 2018. [Online]. Available: http://arxiv.org/abs/1809.09566 [17] R. Dutta and R. Barua, “Provably Secure Constant Round Contributory Group Key Agreement in Dynamic Setting,” IEEE Transactions on Information Theory, vol. 54, no. 5, pp. 2007–2025, May 2008. [18] D. Ongaro and J. Ousterhout, “In search of an understandable consensus algorithm,” in Proceedings of the 2014 USENIX Conference on USENIX Annual Technical Conference, ser. USENIX ATC’14, pp. 305–320. [19] M. J. Dworkin, “Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC,” NIST, Nov. 2007. [20] R. Atkinson and S. Kent, “Security Architecture for the Internet Protocol,” Internet Engineering Task Force, Request for Comments RFC 2401, Nov. 1998. [21] T. T. T. ZOU) and X. Zhang, “IPsec Anti-Replay Algorithm without Bit Shifting,” Internet Engineering Task Force, Request for Comments RFC 6479, Jan. 2012. [22] S. Boeyen, S. Santesson, T. Polk, R. Housley, S. Farrell, and D. Cooper, “Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile,” Internet Engineering Task Force, Request for Comments RFC 5280, May 2008. [23] H. Zhang, C. Xu, C. Li, and A. R. Sangi, “Two Attacks on Dutta’s Dynamic Group Key Agreement Protocol,” in Wireless Communications and Applications, ser. Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering, P. Senac, M. Ott, and A. Seneviratne, Eds., pp. 419–425. ´ [24] J. A. Donenfeld, “WireGuard: Next Generation Kernel Network Tunnel,” in Proceedings 2017 Network and Distributed System Security Symposium. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Secure and Dynamic Publish/Subscribe: LCMsec: Appendix and References

Authors:
(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org);
(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Related Work Description of LCM Attacker Model and Security Goals LCMSec: The Proposed Protocol Implementation and Evaluation Conclusion Appendix and References VII. CONCLUSION In this work, we presented LCMsec, a new secure brokerless Publish/Subscribe protocol based on UDP multicast. We have added confidentiality, integrity and authenticity to the existing LCM protocol while minimising both overhead and computational complexity. LCMsec can be used in most environments in which LCM is currently used, e.g., IoT, automotive and robotics applications. This has been achieved by using a different threat model than previous work in the domain of multicast authentication. We make no distinction between subscribers and publishers, each subscriber is also allowed to publish messages. However, an attribute-based access control mechanism is available through the use X.509 certificates that grants access only to specific LCMdomains. LCMsec is decentralised in the sense that there is no need for a central server to broker messages, facilitate key exchanges or discover peers. A discovery mechanism is instead built-in, which facilitates ease-of-use and flexibility. Despite the shared symmetric key, it should be noted that the protocol is scalable in dynamic situations: Through use of the DuttaBarua group key agreement, the number of network interactions when a publisher or subscriber joins a topic is minimised. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Authors: Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Abstract and Introduction Related Work Related Work Description of LCM Description of LCM Attacker Model and Security Goals Attacker Model and Security Goals LCMSec: The Proposed Protocol LCMSec: The Proposed Protocol Implementation and Evaluation Implementation and Evaluation Conclusion Conclusion Appendix and References Appendix and References VII. CONCLUSION In this work, we presented LCMsec, a new secure brokerless Publish/Subscribe protocol based on UDP multicast. We have added confidentiality, integrity and authenticity to the existing LCM protocol while minimising both overhead and computational complexity. LCMsec can be used in most environments in which LCM is currently used, e.g., IoT, automotive and robotics applications. This has been achieved by using a different threat model than previous work in the domain of multicast authentication. We make no distinction between subscribers and publishers, each subscriber is also allowed to publish messages. However, an attribute-based access control mechanism is available through the use X.509 certificates that grants access only to specific LCMdomains. LCMsec is decentralised in the sense that there is no need for a central server to broker messages, facilitate key exchanges or discover peers. A discovery mechanism is instead built-in, which facilitates ease-of-use and flexibility. Despite the shared symmetric key, it should be noted that the protocol is scalable in dynamic situations: Through use of the DuttaBarua group key agreement, the number of network interactions when a publisher or subscriber joins a topic is minimised. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Secure and Dynamic Publish/Subscribe: LCMsec: Conclusion

Authors:
(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org);
(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Related Work Description of LCM Attacker Model and Security Goals LCMSec: The Proposed Protocol Implementation and Evaluation Conclusion Appendix and References VI. IMPLEMENTATION AND EVALUATION An implementation of LCMsec is publicly available[2]. It is written in C++ and uses the Botan[3] cryptography library. In the implementation of the Dutta Barua protocol, we use a modified version based on elliptic curve cryptography for performance reasons. A. Latency and Throughput Latency and throughput of the LCMsec protocol were tested using two identical servers with an Intel Xeon Gold 5317 processor and 8GB RAM running Linux 5.15. The servers were one hop apart with a 1GBit/s link between them. To test the latency of LCMsec messages, an echo test was performed: one of the servers, the source, transmitted messages of sizes ranging from 100 Bytes to 100 Kilobytes. Upon receiving one of these messages, the other server immediately re-transmitted it. Upon receiving the original message back, the latency was measured by the source. For each message size, a total of 1000 latency measurements were taken. The same was done for the original LCM library. The results are depicted in Figure 8 – as one can see, there is only a small latency overhead. Note that the jump at 3 KB is due to fragmentation of the LCM messages, which occurs at that size. To measure the throughput achieved by LCMsec, a similar echo test was performed on the same servers. Using a fixed message size, the source increased the bandwidth at which it transmitted while recording the number of messages it received back. In such a test, the percentage of lost messages can indicate the throughput capabilities of LCMsec. However, no difference between LCM and LCMsec was observed: in both cases, no messages were lost up to a bandwidth of 123MB/s. After this point, a majority of messages were dropped since the limit of the link between the servers had been reached. B. Evaluation of the Group Discovery The most expensive part of the group discovery are the JOIN Responses: They may be large since they contain the certificates of all other users. Thus, the number of JOIN Responses needed should be kept to a minimum. To evaluate the performance of the protocol, measuring the time taken to perform the group discovery protocol is not helpful, since it is bounded by timeouts. Instead, we count the number of JOINs and JOIN_Responses transmitted while a varying number of nodes execute the group discovery protocol and subsequent DBGKA twice (in order to agree on both kg and kch). This paper is available on arxiv under CC BY 4.0 DEED license. [2] https://github.com/Barkhausen-Institut/lcm-sec [3] https://botan.randombit.net/ Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Authors: Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Abstract and Introduction Related Work Related Work Description of LCM Description of LCM Attacker Model and Security Goals Attacker Model and Security Goals LCMSec: The Proposed Protocol LCMSec: The Proposed Protocol Implementation and Evaluation Implementation and Evaluation Conclusion Conclusion Appendix and References Appendix and References VI. IMPLEMENTATION AND EVALUATION An implementation of LCMsec is publicly available[2]. It is written in C++ and uses the Botan[3] cryptography library. In the implementation of the Dutta Barua protocol, we use a modified version based on elliptic curve cryptography for performance reasons. A. Latency and Throughput A. Latency and Throughput Latency and throughput of the LCMsec protocol were tested using two identical servers with an Intel Xeon Gold 5317 processor and 8GB RAM running Linux 5.15. The servers were one hop apart with a 1GBit/s link between them. To test the latency of LCMsec messages, an echo test was performed: one of the servers, the source, transmitted messages of sizes ranging from 100 Bytes to 100 Kilobytes. Upon receiving one of these messages, the other server immediately re-transmitted it. Upon receiving the original message back, the latency was measured by the source. For each message size, a total of 1000 latency measurements were taken. The same was done for the original LCM library. The results are depicted in Figure 8 – as one can see, there is only a small latency overhead. Note that the jump at 3 KB is due to fragmentation of the LCM messages, which occurs at that size. To measure the throughput achieved by LCMsec, a similar echo test was performed on the same servers. Using a fixed message size, the source increased the bandwidth at which it transmitted while recording the number of messages it received back. In such a test, the percentage of lost messages can indicate the throughput capabilities of LCMsec. However, no difference between LCM and LCMsec was observed: in both cases, no messages were lost up to a bandwidth of 123MB/s. After this point, a majority of messages were dropped since the limit of the link between the servers had been reached. B. Evaluation of the Group Discovery B. Evaluation of the Group Discovery The most expensive part of the group discovery are the JOIN Responses: They may be large since they contain the certificates of all other users. Thus, the number of JOIN Responses needed should be kept to a minimum. To evaluate the performance of the protocol, measuring the time taken to perform the group discovery protocol is not helpful, since it is bounded by timeouts. Instead, we count the number of JOINs and JOIN_Responses transmitted while a varying number of nodes execute the group discovery protocol and subsequent DBGKA twice (in order to agree on both kg and k ch ). ch This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv [2] https://github.com/Barkhausen-Institut/lcm-sec [3] https://botan.randombit.net/

Secure and Dynamic Publish/Subscribe: LCMsec: Implementation and Evaluation

Secure and Dynamic Publish/Subscribe: LCMsec: LCMSec: The Proposed Protocol

Authors:
(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org);
(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Related Work Description of LCM Attacker Model and Security Goals LCMSec: The Proposed Protocol Implementation and Evaluation Conclusion Appendix and References IV. ATTACKER MODEL AND SECURITY GOALS We consider active and modifying attackers in the system. Security is provided only against outsiders: we do not consider an attacker who has the permission to send on the multicast group in question (please refer to the discussion on permission management in Section V-B1). The attacker has considerable, but limited resources and cannot break common cryptographic primitives. Since channelnames in LCM are usually domain-specific topics, they should remain confidential. LCMsec aims to provide confidentiality and integrity of not only the messages in transit, but also the channelname associated with them. We also provide a notion of authenticity: messages are guaranteed to have originated from a trusted entity within the LCMDomain, but cannot be attributed to a specific entity. We provide a reduced form of security against an attacker, who has no permission to send on a specific channel, but can send on some other channel within the group. Against this type of attacker, the integrity and accountability guarantees remain unchanged, however, confidentiality is provided only for the contents of messages, not for the channelname (or topic) associated with messages. We elaborate on the reason for this trade-off in Section V-A. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Authors: Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Abstract and Introduction Related Work Related Work Description of LCM Description of LCM Attacker Model and Security Goals Attacker Model and Security Goals LCMSec: The Proposed Protocol LCMSec: The Proposed Protocol Implementation and Evaluation Implementation and Evaluation Conclusion Conclusion Appendix and References Appendix and References IV. ATTACKER MODEL AND SECURITY GOALS We consider active and modifying attackers in the system. Security is provided only against outsiders: we do not consider an attacker who has the permission to send on the multicast group in question (please refer to the discussion on permission management in Section V-B1). The attacker has considerable, but limited resources and cannot break common cryptographic primitives. Since channelnames in LCM are usually domain-specific topics, they should remain confidential. LCMsec aims to provide confidentiality and integrity of not only the messages in transit, but also the channelname associated with them. We also provide a notion of authenticity: messages are guaranteed to have originated from a trusted entity within the LCMDomain, but cannot be attributed to a specific entity. channelnames channelname We provide a reduced form of security against an attacker, who has no permission to send on a specific channel, but can send on some other channel within the group. Against this type of attacker, the integrity and accountability guarantees remain unchanged, however, confidentiality is provided only for the contents of messages, not for the channelname (or topic) associated with messages. We elaborate on the reason for this trade-off in Section V-A. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Secure and Dynamic Publish/Subscribe: LCMsec: Attacker Model and Security Goals

Authors:
(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org);
(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Related Work Description of LCM Attacker Model and Security Goals LCMSec: The Proposed Protocol Implementation and Evaluation Conclusion Appendix and References III. DESCRIPTION OF LCM Lightweight Communications and Marshalling [2] is a brokerless, topic-based Publish/Subscribe protocol designed for real-time systems that require high-throughput and lowlatency. Message types can be defined in the LCM type specification language, which is a language-neutral and platformneutral specification language for structured data. From this specification language, language-specific bindings for binary serialisation and encoding are generated, while maintaining interoperability. The binary-encoded LCM messages are then sent via multicast groups, which are identified by the multicast IP-address and port on which they are transmitted. Each group comprises multiple topics, which in LCM are called channels, identified by a channelname string. Messages are transmitted using UDP and routed via IP-multicast to all other nodes within the multicast group. A node can subsequently subscribe to a channel within that group by simply dropping all messages except those that match the channelname. Since the same channelname might be used in multiple multicastgroups at the same time, we can uniquely identify a only by the combination of multicastgroup and channelname. We will therefore define LCMDomain=(multicastgroup, channelname). The LCM packet format, as depicted in Figure 2, consists of a 4 byte magic number to identify the LCM protocol, a sequence number which is incremented by each sender separately, and a zero-terminated, ASCII-encoded channelname string. The channelname string is immediately followed by the payload. Large messages are fragmented into multiple smaller transportation units to achieve a maximum message size of 4 GB, in this case a slightly more complicated header is used, but omitted here. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Authors: Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Abstract and Introduction Related Work Related Work Description of LCM Description of LCM Attacker Model and Security Goals Attacker Model and Security Goals LCMSec: The Proposed Protocol LCMSec: The Proposed Protocol Implementation and Evaluation Implementation and Evaluation Conclusion Conclusion Appendix and References Appendix and References III. DESCRIPTION OF LCM Lightweight Communications and Marshalling [2] is a brokerless, topic-based Publish/Subscribe protocol designed for real-time systems that require high-throughput and lowlatency. Message types can be defined in the LCM type specification language, which is a language-neutral and platformneutral specification language for structured data. From this specification language, language-specific bindings for binary serialisation and encoding are generated, while maintaining interoperability. The binary-encoded LCM messages are then sent via multicast groups, which are identified by the multicast IP-address and port on which they are transmitted. Each group comprises multiple topics, which in LCM are called channels, identified by a channelname string. Messages are transmitted using UDP and routed via IP-multicast to all other nodes within the multicast group. A node can subsequently subscribe to a channel within that group by simply dropping all messages except those that match the channelname . Since the same channelname might be used in multiple multicastgroups at the same time, we can uniquely identify a only by the combination of multicastgroup and channelname . We will therefore define LCMDomain=(multicastgroup, channelname). channelname channelname multicastgroups multicastgroup channelname LCMDomain=(multicastgroup, channelname). The LCM packet format, as depicted in Figure 2, consists of a 4 byte magic number to identify the LCM protocol, a sequence number which is incremented by each sender separately, and a zero-terminated, ASCII-encoded channelname string. The channelname string is immediately followed by the payload. Large messages are fragmented into multiple smaller transportation units to achieve a maximum message size of 4 GB, in this case a slightly more complicated header is used, but omitted here. channelname channelname This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Secure and Dynamic Publish/Subscribe: LCMsec: Description of LCM

Authors:
(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org);
(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Related Work Description of LCM Attacker Model and Security Goals LCMSec: The Proposed Protocol Implementation and Evaluation Conclusion Appendix and References II. RELATED WORK A. Publish/Subscribe Systems Typically, a distinction is made between topic-based and content-based Publish/Subscribe systems [1]. In a topic-based system, subscribers can subscribe to one or multiple topics. Messages in such a system are associated with a specific topic, and receivers will only receive messages on topics they are interested in. In a content-based system, subscribers can instead express constraints on the contents of messages directly. Furthermore, Publish/Subscribe systems usually adopt either a brokered or brokerless architecture. Brokered systems like the widely used Message Queue Telemetry Transport (MQTT) [4] use a central message broker to transmit messages between the publishers and subscribers. This allows fine-grained control over message distribution since brokers can route messages based on the constraints of the subscribers (whether they are content- or topic-based). Brokerless Publish/Subscribe systems distribute messages directly from publishers to subscribers in a peer-to-peer fashion, which can improve latency and throughput characteristics while reducing the amount of configuration that is required to deploy entities. Additionally, the decentralised nature of such systems does not depend on a single point of failure. Examples for such systems include the Data Distribution Service (DDS) [5] and LCM, both of which can use UDP over IP multicast [6] for message delivery to achieve high-throughput and lowlatency in scalable systems. B. Security in Publish/Subscribe Systems Most work that proposes security solutions for Publish/Subscribe systems focuses on brokered Publish/Subscribe architectures. For instance, Onica et al. [7] stated a list of requirements for privacy-preserving Publish/Subscribe systems, but consider only systems which use a broker. Bernard et al. [8] proposed a general, conceptual framework for peer-to-peer data exchange that can also be used with existing Publish/Subscribe systems, although brokers are used in this scenario. Malina et al. [9] proposed a security framework for MQTT which uses brokers. Ion et al. [10] and Hamad et al. [11] described systems in which brokers are employed but not trusted. Similarly, Dahlmanns et al. propose ENTRUST [12], achieving endto-end security over any existing brokered Publish/Subscribe system without trusting those brokers. ZeroMQ [13] can be used to implement brokerless Publish/Subscribe messaging, however, there are no security extensions for it with support for this use-case. CurveZMQ [14], while similar in name, is quite different and does not actually provide security for Publish/Subscribe systems, but end-to-end security between client and server. While CurveZMQ can be used to secure Publish/Subscribe by being embedded in the transport layer, this is only possible when client and server are only one hop apart. The Data Distribution Service (DDS), however, is quite comparable to LCM with regard to their respective use-cases. DDS supports the brokerless Publish/Subscribe paradigm in a peer-to-peer fashion, that is without using a message broker, however, it works slightly differently to LCM. Instead of simply broadcasting messages to a preconfigured multicast group, DDS features a discovery protocol that allows publishers to discover the set of appropriate subscribers. Subsequently, messages are routed only to these subscribers. DDS also features a security extension [15] that provides authenticated encryption on a per-message basis. However, a handshake and key agreement is performed separately between each publisher and subscriber to a topic (as discovered by the discovery protocol) [16]. This may lead to scalability issues during the discovery phase in the case of large numbers of publishers or subscribers to the same topic. A high amount of flexibility and many ways to configure the DDS middleware can lead to misconfiguration, a problem which is also mentioned in [16]. Additionally, there are scalability issues at runtime. Authentication of messages is achieved by using a separate Message Authentication Code for each receiver [15] which, in the case of many subscribers, leads either to large overhead for each message or separate messages for each receiver, moving away from the multicast paradigm. These scalability issues are quite inherent to the problem of authenticating messages in a multicast setting in which digital signatures are not desired due to their poor performance characteristics. While a number of theoretical solutions are discussed in literature [3], we bypass this problem entirely. By defining a trusted group of legitimate publishers and subscribers that share a common symmetric, ephemeral key, we propose a protocol in which an authentic message is understood to be a message originating from any member of this group, not necessarily a specific one. In order to generate this shared key while avoiding a scenario in which a total of N ·M expensive key agreements need to be carried out (in the case of N publishers and M subscribers), we use the DuttaBarua group key agreement (DBGKA) [17], an authenticated group key agreement protocol that supports dynamic joining and leaving of users. Furthermore, we implement a discovery protocol, inspired by the Raft consensus algorithm [18], that forms consensus about the state of the trusted group in order to drive the DBGKA protocol. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Authors: Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Abstract and Introduction Related Work Related Work Description of LCM Description of LCM Attacker Model and Security Goals Attacker Model and Security Goals LCMSec: The Proposed Protocol LCMSec: The Proposed Protocol Implementation and Evaluation Implementation and Evaluation Conclusion Conclusion Appendix and References Appendix and References II. RELATED WORK A. Publish/Subscribe Systems A. Publish/Subscribe Systems Typically, a distinction is made between topic-based and content-based Publish/Subscribe systems [1]. In a topic-based system, subscribers can subscribe to one or multiple topics. Messages in such a system are associated with a specific topic, and receivers will only receive messages on topics they are interested in. In a content-based system, subscribers can instead express constraints on the contents of messages directly. Furthermore, Publish/Subscribe systems usually adopt either a brokered or brokerless architecture. Brokered systems like the widely used Message Queue Telemetry Transport (MQTT) [4] use a central message broker to transmit messages between the publishers and subscribers. This allows fine-grained control over message distribution since brokers can route messages based on the constraints of the subscribers (whether they are content- or topic-based). Brokerless Publish/Subscribe systems distribute messages directly from publishers to subscribers in a peer-to-peer fashion, which can improve latency and throughput characteristics while reducing the amount of configuration that is required to deploy entities. Additionally, the decentralised nature of such systems does not depend on a single point of failure. Examples for such systems include the Data Distribution Service (DDS) [5] and LCM, both of which can use UDP over IP multicast [6] for message delivery to achieve high-throughput and lowlatency in scalable systems. B. Security in Publish/Subscribe Systems B. Security in Publish/Subscribe Systems Most work that proposes security solutions for Publish/Subscribe systems focuses on brokered Publish/Subscribe architectures. For instance, Onica et al. [7] stated a list of requirements for privacy-preserving Publish/Subscribe systems, but consider only systems which use a broker. Bernard et al. [8] proposed a general, conceptual framework for peer-to-peer data exchange that can also be used with existing Publish/Subscribe systems, although brokers are used in this scenario. Malina et al. [9] proposed a security framework for MQTT which uses brokers. Ion et al. [10] and Hamad et al. [11] described systems in which brokers are employed but not trusted. Similarly, Dahlmanns et al. propose ENTRUST [12], achieving endto-end security over any existing brokered Publish/Subscribe system without trusting those brokers. ZeroMQ [13] can be used to implement brokerless Publish/Subscribe messaging, however, there are no security extensions for it with support for this use-case. CurveZMQ [14], while similar in name, is quite different and does not actually provide security for Publish/Subscribe systems, but end-to-end security between client and server. While CurveZMQ can be used to secure Publish/Subscribe by being embedded in the transport layer, this is only possible when client and server are only one hop apart. The Data Distribution Service (DDS), however, is quite comparable to LCM with regard to their respective use-cases. DDS supports the brokerless Publish/Subscribe paradigm in a peer-to-peer fashion, that is without using a message broker, however, it works slightly differently to LCM. Instead of simply broadcasting messages to a preconfigured multicast group, DDS features a discovery protocol that allows publishers to discover the set of appropriate subscribers. Subsequently, messages are routed only to these subscribers. DDS also features a security extension [15] that provides authenticated encryption on a per-message basis. However, a handshake and key agreement is performed separately between each publisher and subscriber to a topic (as discovered by the discovery protocol) [16]. This may lead to scalability issues during the discovery phase in the case of large numbers of publishers or subscribers to the same topic. A high amount of flexibility and many ways to configure the DDS middleware can lead to misconfiguration, a problem which is also mentioned in [16]. Additionally, there are scalability issues at runtime. Authentication of messages is achieved by using a separate Message Authentication Code for each receiver [15] which, in the case of many subscribers, leads either to large overhead for each message or separate messages for each receiver, moving away from the multicast paradigm. These scalability issues are quite inherent to the problem of authenticating messages in a multicast setting in which digital signatures are not desired due to their poor performance characteristics. While a number of theoretical solutions are discussed in literature [3], we bypass this problem entirely. By defining a trusted group of legitimate publishers and subscribers that share a common symmetric, ephemeral key, we propose a protocol in which an authentic message is understood to be a message originating from any member of this group, not necessarily a specific one. In order to generate this shared key while avoiding a scenario in which a total of N ·M expensive key agreements need to be carried out (in the case of N publishers and M subscribers), we use the DuttaBarua group key agreement (DBGKA) [17], an authenticated group key agreement protocol that supports dynamic joining and leaving of users. Furthermore, we implement a discovery protocol, inspired by the Raft consensus algorithm [18], that forms consensus about the state of the trusted group in order to drive the DBGKA protocol. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Secure and Dynamic Publish/Subscribe: LCMsec: Related Work

Authors:
(1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org);
(2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Related Work Description of LCM Attacker Model and Security Goals LCMSec: The Proposed Protocol Implementation and Evaluation Conclusion Appendix and References Abstract—We propose LCMsec, a brokerless, decentralised Publish/Subscribe protocol. It aims to provide low-latency and high-throughput message-passing for IoT and automotive applications while providing much-needed security functionalities to combat emerging cyber-attacks in that domain. LCMsec is an extension for the Lightweight Communications and Marshalling (LCM) protocol. We extend this protocol by providing not only authenticated encryption of the messages in transit, but also a group discovery protocol inspired by the Raft consensus protocol. The Dutta-Barua group key agreement is used to agree upon a shared symmetric key among subscribers and publishers on a topic. By using a shared group key, we reduce the key agreement overhead and the number of message authentication codes (MACs) per message compared to existing proposals for secure brokerless Publish/Subscribe protocols, which establish a symmetric key between each publisher and subscriber and append multiple MACs to each message. Index Terms—Publish/Subscribe security, cryptography, multicast, IoT security, secure group communication, cybersecurity I. INTRODUCTION Publish/Subscribe architectures [1] are widespread and an important building block for Internet of Things (IoT), automotive and cloud applications. They can improve scalability and flexibility of communication infrastructures by decreasing dependencies between components, since entities in such a system need not know about one another. They additionally support dynamic communication patterns in which publishers and subscribers can be added and removed without affecting the rest of the system. Some Publish/Subscribe protocols like the Lightweight Communication and Marshalling protocol (LCM) [2] are brokerless, which offers advantages in terms of latency and throughput in some situations, removes a central point of failure (the broker) and reduces the administrative overhead. However, LCM fails to offer convenient and fast possibilities of securing it. There exists no easy way to achieve security by leveraging existing transport-layer encryption mechanisms due to the multicast-based communication topology that is used in LCM: achieving security in the multicast case is generally a much harder problem than in the unicast case [3]. Thus, LCM, even when used in an isolated network, not only violates the emerging zero-trust paradigm but also the needto-know principle: messages are simply routed to all other users of the system, even those that have not subscribed to the particular topic. Nevertheless, the brokerless Publish/Subscribe communication topology offers the distinct advantages in terms of latency, throughput and simplicity mentioned above. The purpose of this work is therefore to provide an extension to LCM, which preserves the benefits in performance and ease of usability. Furthermore, it ensures confidentiality, integrity and authenticity for the messages in transit. An overview and evaluation of the existing security solutions in the Publish/Subscribe space is discussed in Section II. In Section III, we discuss the LCM protocol in detail since it forms the basis for this work. After defining an attacker model and security goals in Section IV, we present the proposed LCMsec protocol in Section V, which contains two phases: firstly, the scheme used to secure messages based on shared keying material, secondly, the scheme used to agree on that keying material. Finally, we evaluate the performance of the proposed protocol in Section VI. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Authors: Authors: (1) Moritz Jasper, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (moritz.jasperl@barkhauseninstitut.org); (2) Stefan Kopsell, Barkhausen Institut gGmbH, Wurzburger Straße 46, Dresden, Germany (stefan.koepsell@barkhauseninstitut.org). Table of Links Abstract and Introduction Abstract and Introduction Related Work Related Work Description of LCM Description of LCM Attacker Model and Security Goals Attacker Model and Security Goals LCMSec: The Proposed Protocol LCMSec: The Proposed Protocol Implementation and Evaluation Implementation and Evaluation Conclusion Conclusion Appendix and References Appendix and References Abstract—We propose LCMsec, a brokerless, decentralised Publish/Subscribe protocol. It aims to provide low-latency and high-throughput message-passing for IoT and automotive applications while providing much-needed security functionalities to combat emerging cyber-attacks in that domain. LCMsec is an extension for the Lightweight Communications and Marshalling (LCM) protocol. We extend this protocol by providing not only authenticated encryption of the messages in transit, but also a group discovery protocol inspired by the Raft consensus protocol. The Dutta-Barua group key agreement is used to agree upon a shared symmetric key among subscribers and publishers on a topic. By using a shared group key, we reduce the key agreement overhead and the number of message authentication codes (MACs) per message compared to existing proposals for secure brokerless Publish/Subscribe protocols, which establish a symmetric key between each publisher and subscriber and append multiple MACs to each message. Abstract —We propose LCMsec, a brokerless, decentralised Publish/Subscribe protocol. It aims to provide low-latency and high-throughput message-passing for IoT and automotive applications while providing much-needed security functionalities to combat emerging cyber-attacks in that domain. LCMsec is an extension for the Lightweight Communications and Marshalling (LCM) protocol. We extend this protocol by providing not only authenticated encryption of the messages in transit, but also a group discovery protocol inspired by the Raft consensus protocol. The Dutta-Barua group key agreement is used to agree upon a shared symmetric key among subscribers and publishers on a topic. By using a shared group key, we reduce the key agreement overhead and the number of message authentication codes (MACs) per message compared to existing proposals for secure brokerless Publish/Subscribe protocols, which establish a symmetric key between each publisher and subscriber and append multiple MACs to each message. Abstract Index Terms—Publish/Subscribe security, cryptography, multicast, IoT security, secure group communication, cybersecurity Index Terms —Publish/Subscribe security, cryptography, multicast, IoT security, secure group communication, cybersecurity Index Terms I. INTRODUCTION Publish/Subscribe architectures [1] are widespread and an important building block for Internet of Things (IoT), automotive and cloud applications. They can improve scalability and flexibility of communication infrastructures by decreasing dependencies between components, since entities in such a system need not know about one another. They additionally support dynamic communication patterns in which publishers and subscribers can be added and removed without affecting the rest of the system. Some Publish/Subscribe protocols like the Lightweight Communication and Marshalling protocol (LCM) [2] are brokerless, which offers advantages in terms of latency and throughput in some situations, removes a central point of failure (the broker) and reduces the administrative overhead. However, LCM fails to offer convenient and fast possibilities of securing it. There exists no easy way to achieve security by leveraging existing transport-layer encryption mechanisms due to the multicast-based communication topology that is used in LCM: achieving security in the multicast case is generally a much harder problem than in the unicast case [3]. Thus, LCM, even when used in an isolated network, not only violates the emerging zero-trust paradigm but also the needto-know principle: messages are simply routed to all other users of the system, even those that have not subscribed to the particular topic. Nevertheless, the brokerless Publish/Subscribe communication topology offers the distinct advantages in terms of latency, throughput and simplicity mentioned above. The purpose of this work is therefore to provide an extension to LCM, which preserves the benefits in performance and ease of usability. Furthermore, it ensures confidentiality, integrity and authenticity for the messages in transit. An overview and evaluation of the existing security solutions in the Publish/Subscribe space is discussed in Section II. In Section III, we discuss the LCM protocol in detail since it forms the basis for this work. After defining an attacker model and security goals in Section IV, we present the proposed LCMsec protocol in Section V, which contains two phases: firstly, the scheme used to secure messages based on shared keying material, secondly, the scheme used to agree on that keying material. Finally, we evaluate the performance of the proposed protocol in Section VI. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Secure and Dynamic Publish/Subscribe: LCMsec: Abstract and Introduction

Life in 2050 According to Jail-Broken GPT-4o 

For a beginner, it might seem daunting to start learning how to code, but with the endless advancements in technology, there are now innovative tools that can make learning how to code easy and fun. One of those tools is ChatGPT which was developed by OpenAI. Back when I started learning how to code, there was no ChatGPT, but now, it's become the number one coding assistant for many developers, myself included. I use it daily, and frankly, I think you should too. In this article, I will show you how you can use ChatGPT as a guide on your fun coding adventure using two of the most popular programming languages, Python and JavaScript. Understanding ChatGPT Before we jump into using ChatGPT as our guide and assistant, let's understand what this tool really is. ChatGPT is a language model developed by OpenAI, and it's based on the GPT-3.5 and GPT-4 architectures. It’s pre-trained on public data and data licensed from third-party providers to be able to predict the best answer for your query. It’s capable of delivering human-like text responses and can be used in various natural language processing tasks. In your case, as an interactive coding assistant. Getting Started To begin your learning journey using ChatGPT, you will need access to an environment where you can interface with the model. OpenAI does offer an API that developers can hook into but for anyone starting out in this aspect, using the official OpenAI website would be the right move. You can toy with ChatGPT on the OpenAI website in a user-friendly, as well as interactive, user interface. OpenAI keeps updating the website and keeps adding new features and customizations to the online interface. The paid version of their service has some third-party plugins you can use, and it gives you access to GPT-4, their latest releases. In my case and as a Data Engineer, I use the plugins and GPT-4 daily so I can upload and ask the model to create downloadable texts, images, and graphs which makes the boring part of my job so much easier. Choosing a Language: Python or JavaScript Python, as well as JavaScript, are some of the most popular programming languages these days with excellent features to showcase on any project. Python is popular because it has a simple syntax. On the other hand, by learning JavaScript as your first language, you have a chance to start developing full-stack web applications ASAP. Based on your programming language choice, you can always start your ChatGPT queries by specifying the language or the framework you are working with. Asking Basic Coding Questions Now that you have selected the language, you can proceed with some basic coding questions to ChatGPT. Begin with some of the easier questions on concepts such as variables, data types, and basic syntax examples. For instance: Variables:
You can ask: "How do I declare a variable in Python?"
ChatGPT might respond with: "In Python, you declare a variable using the syntax: variable_name = value." Data Types:
You can inquire: "What are the main data types in JavaScript?"
ChatGPT might provide: "JavaScript has several data types, including string, number, boolean, object, and array." Basic Syntax:
Ask: "Can you explain the if-else statement in Python?"
ChatGPT might elucidate: "In Python, the if-else statement is used for conditional execution. It follows the syntax: if condition: # code block 1 else: # code block 2." Building on Fundamentals Once the basics are clear, then start asking tougher or more complex questions. Concepts like loops, functions, and object-oriented programming can be used to explore these ideas. Eventually, you can increase the bar of questioning to ensure better ways of learning. Loops:
Ask: "How does a for loop work in JavaScript?"
ChatGPT could respond: "In JavaScript, a for loop has the syntax: for (initialization; condition; update) { // code block }." Functions:
Inquire: "What is the significance of parameters in a Python function?" ChatGPT might explain: "Parameters in a Python function allow you to pass values to the function. They are variables that store the arguments you provide when calling the function." Object-Oriented Programming (OOP):
Ask: "Can you give an example of a Python class and its methods?"
ChatGPT may provide: "Certainly! In Python, a class is defined using the class keyword. Here's an example: class Dog: def init(self, name, age): self.name = name self.age = age def bark(self): return 'Woof!' Troubleshooting and Debugging As you progress, you'll likely encounter errors or face challenges in your code. ChatGPT can also assist you in troubleshooting and debugging. Error Handling:
Ask: "How do I handle exceptions in Python?"
ChatGPT might guide you: "In Python, you can use the ‘try’, ‘except’, and optionally ‘finally’ blocks for exception handling. For example: try: # code that might raise an exceptionexcept Exception as e: # handle the exceptionfinally: # optional cleanup code```" Debugging Tips:
Inquire: "What are some common ways to debug JavaScript code?"
ChatGPT may suggest: "For JavaScript, you can use console.log() statements, browser developer tools, and tools like VSCode with breakpoints to debug your code effectively." Practical Projects and Real-world Applications To solidify your coding skills, consider working on practical projects. ChatGPT can provide guidance on project ideas, implementation details, and best practices. Project Ideas:
Ask: "Can you suggest a beginner-friendly Python project?"
ChatGPT might propose: "Certainly! How about creating a simple to-do list application using a Python web framework like Flask or Django?" Implementation Guidance:
Inquire: "What are the steps to build a basic website using HTML, CSS, and JavaScript?"
ChatGPT could guide you: "First, create an HTML file for the structure, then add styles using CSS. Use JavaScript for interactivity, handling user input, and updating the DOM dynamically." Best Practices:
Ask: "What are some best practices for writing efficient Python code?"
ChatGPT may advise: "Consider using meaningful variable names, following PEP 8 style guide, and optimizing algorithms for better performance." Conclusion Learning how to code with ChatGPT makes the process more exciting and interactive which, in turn, could transform learning complex concepts into something that is easy and fun. Starting with the basics, continuing to advanced topics, moving to error handling, and finishing with implementation into practical projects, ChatGPT can be your complete guide to building your coding foundation in Python or JavaScript languages. Remember, ChatGPT is a learning aid only, so be sure to practice coding regularly, and don't hesitate to find more resources or join programming communities. With dedication and the right resources, you might find yourself immersed in the wonderful world of coding. For a beginner, it might seem daunting to start learning how to code, but with the endless advancements in technology, there are now innovative tools that can make learning how to code easy and fun. One of those tools is ChatGPT which was developed by OpenAI. Back when I started learning how to code, there was no ChatGPT, but now, it's become the number one coding assistant for many developers, myself included. For a beginner, it might seem daunting to start learning how to code, but with the endless advancements in technology, there are now innovative tools that can make learning how to code easy and fun. One of those tools is ChatGPT which was developed by OpenAI. Back when I started learning how to code, there was no ChatGPT, but now, it's become the number one coding assistant for many developers, myself included. I use it daily, and frankly, I think you should too. I use it daily, and frankly, I think you should too. In this article, I will show you how you can use ChatGPT as a guide on your fun coding adventure using two of the most popular programming languages, Python and JavaScript. In this article, I will show you how you can use ChatGPT as a guide on your fun coding adventure using two of the most popular programming languages, Python and JavaScript. Understanding ChatGPT Before we jump into using ChatGPT as our guide and assistant, let's understand what this tool really is. ChatGPT is a language model developed by OpenAI, and it's based on the GPT-3.5 and GPT-4 architectures. It’s pre-trained on public data and data licensed from third-party providers to be able to predict the best answer for your query. It’s capable of delivering human-like text responses and can be used in various natural language processing tasks. In your case, as an interactive coding assistant. Getting Started To begin your learning journey using ChatGPT, you will need access to an environment where you can interface with the model. OpenAI does offer an API that developers can hook into but for anyone starting out in this aspect, using the official OpenAI website would be the right move. You can toy with ChatGPT on the OpenAI website in a user-friendly, as well as interactive, user interface. OpenAI keeps updating the website and keeps adding new features and customizations to the online interface. The paid version of their service has some third-party plugins you can use, and it gives you access to GPT-4, their latest releases. In my case and as a Data Engineer, I use the plugins and GPT-4 daily so I can upload and ask the model to create downloadable texts, images, and graphs which makes the boring part of my job so much easier. Choosing a Language: Python or JavaScript Python, as well as JavaScript, are some of the most popular programming languages these days with excellent features to showcase on any project. Python is popular because it has a simple syntax. On the other hand, by learning JavaScript as your first language, you have a chance to start developing full-stack web applications ASAP. Based on your programming language choice, you can always start your ChatGPT queries by specifying the language or the framework you are working with. Asking Basic Coding Questions Now that you have selected the language, you can proceed with some basic coding questions to ChatGPT. Begin with some of the easier questions on concepts such as variables, data types, and basic syntax examples. For instance: Variables: You can ask: "How do I declare a variable in Python?" ChatGPT might respond with: "In Python, you declare a variable using the syntax: variable_name = value." Variables: You can ask: "How do I declare a variable in Python?" ChatGPT might respond with: "In Python, you declare a variable using the syntax: variable_name = value." Data Types: You can inquire: "What are the main data types in JavaScript?" ChatGPT might provide: "JavaScript has several data types, including string, number, boolean, object, and array." Data Types: You can inquire: "What are the main data types in JavaScript?" ChatGPT might provide: "JavaScript has several data types, including string, number, boolean, object, and array." Basic Syntax: Ask: "Can you explain the if-else statement in Python?" ChatGPT might elucidate: "In Python, the if-else statement is used for conditional execution. It follows the syntax: if condition: # code block 1 else: # code block 2." Basic Syntax: Ask: "Can you explain the if-else statement in Python?" ChatGPT might elucidate: "In Python, the if-else statement is used for conditional execution. It follows the syntax: if condition: # code block 1 else: # code block 2." Building on Fundamentals Once the basics are clear, then start asking tougher or more complex questions. Concepts like loops, functions, and object-oriented programming can be used to explore these ideas. Eventually, you can increase the bar of questioning to ensure better ways of learning. Loops: Ask: "How does a for loop work in JavaScript?" ChatGPT could respond: "In JavaScript, a for loop has the syntax: for (initialization; condition; update) { // code block }." Loops: Ask: "How does a for loop work in JavaScript?" ChatGPT could respond: "In JavaScript, a for loop has the syntax: for (initialization; condition; update) { // code block }." Functions: Inquire: "What is the significance of parameters in a Python function?" Functions: Inquire: "What is the significance of parameters in a Python function?" ChatGPT might explain: "Parameters in a Python function allow you to pass values to the function. They are variables that store the arguments you provide when calling the function." Object-Oriented Programming (OOP): Ask: "Can you give an example of a Python class and its methods?" ChatGPT may provide: "Certainly! In Python, a class is defined using the class keyword. Here's an example: Object-Oriented Programming (OOP): Ask: "Can you give an example of a Python class and its methods?" ChatGPT may provide: "Certainly! In Python, a class is defined using the class keyword. Here's an example: class Dog: def init(self, name, age): self.name = name self.age = age def bark(self): return 'Woof!' Troubleshooting and Debugging As you progress, you'll likely encounter errors or face challenges in your code. ChatGPT can also assist you in troubleshooting and debugging. Error Handling: Ask: "How do I handle exceptions in Python?" ChatGPT might guide you: "In Python, you can use the ‘try’, ‘except’, and optionally ‘finally’ blocks for exception handling. For example: Error Handling: Ask: "How do I handle exceptions in Python?" ChatGPT might guide you: "In Python, you can use the ‘try’, ‘except’, and optionally ‘finally’ blocks for exception handling. For example: try: # code that might raise an exceptionexcept Exception as e: # handle the exceptionfinally: # optional cleanup code```" Debugging Tips: Inquire: "What are some common ways to debug JavaScript code?" ChatGPT may suggest: "For JavaScript, you can use console.log() statements, browser developer tools, and tools like VSCode with breakpoints to debug your code effectively." Debugging Tips: Inquire: "What are some common ways to debug JavaScript code?" ChatGPT may suggest: "For JavaScript, you can use console.log() statements, browser developer tools, and tools like VSCode with breakpoints to debug your code effectively." Practical Projects and Real-world Applications To solidify your coding skills, consider working on practical projects. ChatGPT can provide guidance on project ideas, implementation details, and best practices. Project Ideas: Ask: "Can you suggest a beginner-friendly Python project?" ChatGPT might propose: "Certainly! How about creating a simple to-do list application using a Python web framework like Flask or Django?" Project Ideas: Ask: "Can you suggest a beginner-friendly Python project?" ChatGPT might propose: "Certainly! How about creating a simple to-do list application using a Python web framework like Flask or Django?" Implementation Guidance: Inquire: "What are the steps to build a basic website using HTML, CSS, and JavaScript?" ChatGPT could guide you: "First, create an HTML file for the structure, then add styles using CSS. Use JavaScript for interactivity, handling user input, and updating the DOM dynamically." Implementation Guidance: Inquire: "What are the steps to build a basic website using HTML, CSS, and JavaScript?" ChatGPT could guide you: "First, create an HTML file for the structure, then add styles using CSS. Use JavaScript for interactivity, handling user input, and updating the DOM dynamically." Best Practices: Ask: "What are some best practices for writing efficient Python code?" ChatGPT may advise: "Consider using meaningful variable names, following PEP 8 style guide, and optimizing algorithms for better performance." Best Practices: Ask: "What are some best practices for writing efficient Python code?" ChatGPT may advise: "Consider using meaningful variable names, following PEP 8 style guide, and optimizing algorithms for better performance." Conclusion Learning how to code with ChatGPT makes the process more exciting and interactive which, in turn, could transform learning complex concepts into something that is easy and fun. Starting with the basics, continuing to advanced topics, moving to error handling, and finishing with implementation into practical projects, ChatGPT can be your complete guide to building your coding foundation in Python or JavaScript languages. Remember, ChatGPT is a learning aid only, so be sure to practice coding regularly, and don't hesitate to find more resources or join programming communities. With dedication and the right resources, you might find yourself immersed in the wonderful world of coding.

Unlocking Code Mastery: A Vibrant Guide to Learning Python, JavaScript, and Beyond With ChatGPT

Ever feel like you're just...off? Like your brain's become a bad wifi connection, dropping random ads for stuff you never even searched for?  Yeah, me too. That nagging feeling you can't quite place?  It's not just you. Our brains are under siege, man. Capitalism's got us hooked on that dopamine drip of "buy, buy, buy," influencers are turning us into mindless lemmings chasing the latest trends, and social media's got us scrolling like zombies, all the while feeding us who-knows-what kinda data. Think about it, dude. Politicians spin narratives that make us fight with our own families, employers use sneaky tactics to keep us working overtime and don't even get me started on black markets whispering sweet nothings in our darkest internet searches. We're walking targets, my friend, and the worst part? Most people haven't even noticed the takeover. This ain't some cheesy sci-fi flick – this is real life, and the battleground is our minds. But hey, don't freak out just yet. There's still hope. We can fight back.  We can hack our own brains before someone else does. Buckle up, because we're about to dive deep into the mind control matrix and learn how to take back control. Real-Life Proof of Brain Hijacking Remember that Facebook experiment a while back? The one where they messed with people's news feeds to see how it affected their emotions? Yeah, creepy, right? Turns out that influencing our thoughts and feelings through social media isn't just some dystopian fantasy. It's happening right now. That's just one example, and trust me, there's more where that came from. It's a wild world out there, my friend, and if we're not careful, our brains could end up being hijacked by all sorts of sinister forces. So let's take control before it's too late. It's time to hack our own brains and reclaim our thoughts, our actions, and our lives. Dethrone the Dopamine Dictators Remember that constant urge to check your phone, even though you know there's probably nothing new?  Blame the dopamine hijack!  Social media, games, and even those endless news feeds are like slot machines, triggering a dopamine rush every time you refresh, like a mental "Yay, you did a thing!" party.  This keeps you hooked and coming back for more, even if that "thing" is mindlessly scrolling through pictures of someone else's avocado toast. Go on a dopamine detox. It's like a juice cleanse, but for your brain!  Delete those addictive apps for a week (or a month, if you're feeling bold). Replace the mindless scrolling with a real-world adventure. Take a walk, shoot some hoops, and have a conversation with a human being who isn't filtered through a screen. You might be surprised at how good "unplugged" feels. Sleep? More Like Supercharge! Think of sleep as the ultimate brain gym.  When you're sleep-deprived, your brain turns into a sluggish mess, making it vulnerable to manipulation.  Those late-night conspiracy theory rabbit holes?  Easier to fall when you're running on fumes. Make sleep a priority, not an afterthought. Establish a regular sleep schedule, even on weekends. Create a relaxing bedtime routine (ditch the phone in the bedroom, it's not your lullaby buddy).  A well-rested brain is a hacking machine, ready to filter out the BS and focus on what truly matters. Become Your Own Content Curator Remember that feeling of outrage after reading a super-biased news article?  Yeah, you're being fed a narrative, friend. Social media algorithms and news outlets are like those sketchy carnival barkers, hawking whatever gets the most clicks (and makes them the most money). Diversify your news sources! Don't just stick to the same echo chamber.  Seek out reputable outlets with different perspectives.  Read books, listen to podcasts by experts, and engage in civil discussions (gasp, with people who might have different viewpoints!). The more well-rounded your information diet, the harder it is for someone to spin you a yarn. Stay tuned, comrade! We've got more brain hacking tips coming your way,  ways to turn your mind into an impenetrable fortress against the forces of manipulation. Remember, knowledge is power, and a hacked brain is a powerless brain. Let's fight back and take control! Ever feel like you're just...off? Like your brain's become a bad wifi connection, dropping random ads for stuff you never even searched for?  Yeah, me too. That nagging feeling you can't quite place?  It's not just you. Our brains are under siege, man. Our brains are under siege, man. Capitalism's got us hooked on that dopamine drip of "buy, buy, buy," influencers are turning us into mindless lemmings chasing the latest trends, and social media's got us scrolling like zombies, all the while feeding us who-knows-what kinda data. Think about it, dude. Think about it, dude. Politicians spin narratives that make us fight with our own families, employers use sneaky tactics to keep us working overtime and don't even get me started on black markets whispering sweet nothings in our darkest internet searches. We're walking targets, my friend, and the worst part? Most people haven't even noticed the takeover. This ain't some cheesy sci-fi flick – this is real life, and the battleground is our minds. But hey, don't freak out just yet. There's still hope. We can fight back. We can hack our own brains before someone else does. Buckle up, because we're about to dive deep into the mind control matrix and learn how to take back control. There's still hope. We can fight back. Real-Life Proof of Brain Hijacking Real-Life Proof of Brain Hijacking Remember that Facebook experiment a while back? The one where they messed with people's news feeds to see how it affected their emotions? Facebook Yeah, creepy, right? Yeah, creepy, right? Turns out that influencing our thoughts and feelings through social media isn't just some dystopian fantasy. It's happening right now. That's just one example, and trust me, there's more where that came from. It's a wild world out there, my friend, and if we're not careful, our brains could end up being hijacked by all sorts of sinister forces. So let's take control before it's too late. It's time to hack our own brains and reclaim our thoughts, our actions, and our lives. Dethrone the Dopamine Dictators Remember that constant urge to check your phone, even though you know there's probably nothing new?  Blame the dopamine hijack!  Social media, games, and even those endless news feeds are like slot machines, triggering a dopamine rush every time you refresh, like a mental "Yay, you did a thing!" party.  This keeps you hooked and coming back for more, even if that "thing" is mindlessly scrolling through pictures of someone else's avocado toast. Go on a dopamine detox. It's like a juice cleanse, but for your brain!  Delete those addictive apps for a week (or a month, if you're feeling bold). Replace the mindless scrolling with a real-world adventure. Take a walk, shoot some hoops, and have a conversation with a human being who isn't filtered through a screen. You might be surprised at how good "unplugged" feels. Sleep? More Like Supercharge! Think of sleep as the ultimate brain gym.  When you're sleep-deprived, your brain turns into a sluggish mess, making it vulnerable to manipulation.  Those late-night conspiracy theory rabbit holes?  Easier to fall when you're running on fumes. Make sleep a priority, not an afterthought. Establish a regular sleep schedule, even on weekends. Create a relaxing bedtime routine (ditch the phone in the bedroom, it's not your lullaby buddy).  A well-rested brain is a hacking machine, ready to filter out the BS and focus on what truly matters. Become Your Own Content Curator Remember that feeling of outrage after reading a super-biased news article?  Yeah, you're being fed a narrative, friend. Social media algorithms and news outlets are like those sketchy carnival barkers, hawking whatever gets the most clicks (and makes them the most money). Diversify your news sources! Don't just stick to the same echo chamber.  Seek out reputable outlets with different perspectives.  Read books, listen to podcasts by experts, and engage in civil discussions (gasp, with people who might have different viewpoints!). The more well-rounded your information diet, the harder it is for someone to spin you a yarn. Stay tuned, comrade! We've got more brain hacking tips coming your way,  ways to turn your mind into an impenetrable fortress against the forces of manipulation. Remember, knowledge is power, and a hacked brain is a powerless brain. Let's fight back and take control! Stay tuned, comrade! We've got more brain hacking tips coming your way,  ways to turn your mind into an impenetrable fortress against the forces of manipulation. Remember, knowledge is power, and a hacked brain is a powerless brain. Let's fight back and take control! Stay tuned, comrade! We've got more brain hacking tips coming your way,  ways to turn your mind into an impenetrable fortress against the forces of manipulation. Remember, knowledge is power, and a hacked brain is a powerless brain. Let's fight back and take control!

Stories, News & Mentions about BARK

Bark’s Stories on HackerNoon