One SDK for passwordless, WebAuthn, and social login - fully customizable

Magic

magic

NBA player Jonathan Isaac criticized President Biden for making March 31 Transgender Day of Visibility during Easter Sunday, saying the move &quot;promotes division.&quot;

Magic's Jonathan Isaac criticizes White House over Transgender Day of Visibility | Fox News

Live coverage of the Memphis Grizzlies vs. Orlando <strong>Magic</strong> NBA game on ESPN, including live score, highlights and updated stats.

Grizzlies vs. Magic (Mar 30, 2024) Live Score - ESPN

My ability to remember things can drive my wife crazy. Earlier this week, she asked me two questions after I finished telling her a story that I had recalled from my long-term memory: How do you remember such things? Why do you even remember that memory? Honestly, I have no clue how to answer her questions, only that I recognized this ability earlier in my life. We both agreed that if there was a “useless trivia show,” I would be the world champion … hands down. I feel like some events that I experience for the first time are often indexed in the long-term chambers of my brain, later becoming the source of my stories that I feel compelled to share with her. In terms of career implications, it does not take much effort to recall the first time I worked in a programming language or started using a service or framework. Reading about the service provided by —one that promises “Zero DevOps”—made me want to take it for a test drive. Looking over the list of supported languages, I saw an opportunity to create a service in a programming language that is new to me. Render As a result, I decided to give the programming language a shot, in hopes of adding a new deposit to my long-term memory bank. Go The Magic 8-Ball Service To make things fun, consider an example where asks for the creation of a RESTful API that mimics the toy that was invented in 1946: Mattel Magic 8-Ball For those who are not aware, the Magic 8-Ball is a novelty item that performs basic fortune-telling tasks. With the 8-Ball image facing up, the person holding the ball asks a yes-no question, then turns it over to reveal an answer. The reply magically floats to the top out of the dark black ocean inside the toy. The original design contained 20 unique answers, and the acceptance criteria is that only these responses will be allowed in the RESTful API: Ten positive answers are noted with green bullets, and the remaining ten are an equal combination of non-committal (yellow) and negative (red) answers. Consumers of the API simply need to make a standard GET request, which will return a random answer from the list of possible options. For validation purposes, Mattel would also like a second endpoint to retrieve a list of all available answers from this new service. With my design, we can meet these requirements with the following endpoints: GET - randomly returns one of the twenty available answers /answer GET - returns a list of all twenty available answers /answers Getting Started With Go While visiting the on the Go site, I noticed the installation process was very similar to getting started with the Java programming language. The installer used a wizard-like design where I basically just had to click buttons to navigate through the process. Once finished, I used the following terminal command to verify a successful installation: download page ╭─me@johnjvester ~ 
╰─$ go version
go version go1.17.6 darwin/amd64 Using IntelliJ IDEA, I added the and started a new project using the command: Go plug-in File | New | Project … The project name of just seemed right for this endeavor: magic-eight-ball After some research, I found that the provides the functionality needed for a RESTful API written in Go, so I installed it with the following command: Gin web framework $ go get -u github.com/gin-gonic/gin To reference Gin inside my source code, I simply needed to include the following import: import "github.com/gin-gonic/gin" Now we are ready to start building the Magic 8-Ball API. Creating the Magic 8-Ball API The first thing I want to do is establish the data side of the API. For this example, the following JSON structure will make up the response body when an answer is provided: {
  "id" : number,
  "response" : string
} In Go, this JSON payload is defined (as shown below) and added to the file: main.go type response struct {
	ID       int    `json:"id"`
	Response string `json:"response"`
} Since all of the data is static, I added the standard answers to the file: main.go var responses = []response{
	{ID: 1, Response: "It is certain."},
	{ID: 2, Response: "It is decidedly so."},
	{ID: 3, Response: "Without a doubt."},
	{ID: 4, Response: "Yes definitely."},
	{ID: 5, Response: "You may rely on it."},
	{ID: 6, Response: "As I see it, yes."},
	{ID: 7, Response: "Most likely."},
	{ID: 8, Response: "Outlook good."},
	{ID: 9, Response: "Yes."},
	{ID: 10, Response: "Signs point to yes."},
	{ID: 11, Response: "Reply hazy, try again."},
	{ID: 12, Response: "Ask again later."},
	{ID: 13, Response: "Better not tell you now."},
	{ID: 14, Response: "Cannot predict now."},
	{ID: 15, Response: "Concentrate and ask again."},
	{ID: 16, Response: "Don't count on it."},
	{ID: 17, Response: "My reply is no."},
	{ID: 18, Response: "My sources say no."},
	{ID: 19, Response: "Outlook not so good."},
	{ID: 20, Response: "Very doubtful."},
} In order to leverage the responses variable, I added two functions to the file: main.go func getAllAnswers(c *gin.Context) {
	c.IndentedJSON(http.StatusOK, responses)
}

func getRandomAnswer(c *gin.Context) {
	rand.Seed(time.Now().Unix())
	c.IndentedJSON(http.StatusOK, responses[rand.Intn(len(responses))])
} The function simply returns the responses list in JSON format, and the function randomly picks one of the twenty options and returns the value in JSON format. getAllAnswers() getRandomAnswer() Finally, the function sets up the endpoints and the port used by the service: main() func main() {
	router := gin.Default()
	router.GET("/answers", getAllAnswers)
	router.GET("/answer", getRandomAnswer)

	port := os.Getenv("PORT")
	if port == "" {
		port = "8080"
	}
	if err := router.Run(":" + port); err != nil {
		log.Panicf("error: %s", err)
	}
} That’s all that is required to meet the acceptance criteria established by Mattel. To start the application, we run the following command from the terminal: ╭─me@johnjvester ~/projects/jvc/go/magic-eight-ball 
╰─$ go run . The logs that displayed included those noted below: [GIN-debug] GET    /answers        --> main.getAllAnswers (3 handlers)
[GIN-debug] GET    /answer         --> main.getRandomAnswer (3 handlers)
[GIN-debug] Listening and serving HTTP on :8080 I can test the API by sending curl requests with the following command: ╭─me@johnjvester ~ 
╰─$ curl http://localhost:8080/answer This is the response I received: {
    "id": 6,
    "response": "As I see it, yes."
}% With the Go service running without any issues, I uploaded the code as a new project on GitLab: https://gitlab.com/johnjvester/magic-eight-ball Now I’m ready to see how Render works. Deploying to Render Via GitLab Getting started with Render was quick, easy, and free. I simply opted to use my GitLab credentials, which made things easy when selecting projects to deploy. To get started, I selected the New button on the Render dashboard and chose the Web Service option: I selected my project on GitLab: magic-eight-ball Within the Render platform, I decided to call my service and kept the defaults for all of the other options: jvc-magic-eight-ball Scrolling down, I opted to keep this service running on the free plan: Then, I clicked the Create Web Service button. Within a few minutes, the showed me that my service was up and running: Render dashboard I sent a request to the URL for my service on Render ( ), and I received the following response: https://jvc-magic-eight-ball.onrender.com/answer {
    "id": 5,
    "response": "You may rely on it."
} Within just a few clicks, I deployed my first RESTful API written in Go to the Render platform—and this didn’t incur any costs. More importantly, the Render approach did not require any DevOps skills or knowledge for me to complete my task. Conclusion The introduction of this article talked about my ability to retain and recall historical events several years (if not decades) later. The fact that this entire experiment took less than an hour of my time—from start to finish—is certainly worthy of becoming another one of those events. Starting in 2021, I have been trying to live by the following mission statement, which I feel can apply to any IT professional: “Focus your time on delivering features/functionality which extends the value of your intellectual property. Leverage frameworks, products, and services for everything else.” - J. Vester In this article, not only was I able to produce a functional API quickly with very little source code, but I was also able to deploy the project to a cloud provider simply by performing a series of small steps. Zero DevOps was promised, and Zero DevOps was delivered. This allowed me to focus my time on providing features to my customers. If you are interested in the full source code, just navigate over to GitLab: https://gitlab.com/johnjvester/magic-eight-ball Knowing that I currently have APIs and applications running in the Heroku ecosystem, I plan to start looking into what a conversion from Heroku to Render looks like in the next few weeks. So far, I am quite impressed with what Render has to offer. Have a really great day! First published here

Spend Zero Time on DevOps with Render PaaS

They’re pretty incredible, you can use any Invocation name to open your custom app and then any utterance word as the first layer, you can then apply inline ‘slots’ to your command to give you unlimited triggers for different pieces of code. ‘Alexa Ask Your Mind to tell me what they’re thinking.’ ‘Alexa Ask Your Mind to read this persons mind using AI.’ That’s , running different programs. one app two ‘Alexa Ask Your AI Engine to read this persons mind using AI.’ That’s a different app, running a program. completely different What I am trying to show here is that there are 100’s of ways of asking the same question, and each variant can trigger a different signal to the Alexa, which will run a seperate piece of code. This method would mean I could personally read someones mind, then tell the Alexa what card they have and the Alexa would just read it out. Simple. The average consumer is completely unaware of this; in fact, I performed this for the CCO’s (chief cybersecurity officers) of many major tech companies, the kind that have a direct line to goverment officials, and they too were oblivious as to what was going on. You will be surprised how many people in technology have no idea about the scope of some low end consumer tech products we take for granted every day. That’s the output part of my deception. But it’s way too boring for a hacker. I need to work out how to tell the Alexa what card the person is currently thinking of (without signaling it first). More so, I need to find a way to work out what card the person is thinking of, using real magic? There are lots of magic tricks that allow me to peek the card someone is looking at, or to force them to pick a card, however I want to have zero involvement in this routine and also have the option of repeating it multiple times, it has to fool the biggest sceptic. Electronic card NFC reader I built a NFC reader, using an Arduino Uno and a simple RFID reader, it cost no more than 30 bucks. Before this, I hadn’t done any electronics, maybe a few LEDs and resistors back in high school but that was it. I was shocked how easy the Arduino stuff is to work with, I watched a few tutorials and took some code from the Arduino CC library. I then placed RFID chips in between the two paper layers of each playing card. These things are completely undetecable, and can store endless amounts of data. I didn’t need that, I just used the unique IDs stored on the chip, created a json object and paired them to the playing cards. The result was 52 RFID playing cards, made of paper. This worked well, you could ask the spectator to place the card on a table, hide the RFID reader under the table and then the RFID reader would ping the card over the internet to my node server. When you ask the Alexa what the card is, it runs a script on Lambda, queries the node server for the JSON object which stores the current playing card and then the Alexa literally READS OUT THE TEXT. I found that the coolest part, the Alexa can read out text stored on a NFC chip. This all happens in a few 100ms. It was cool enough for , WIRED magazine who wrote about my performance of this hack. (I wanted to be in WIRED ever since Paramount’s remake of The Seth Green’s character claimed to be “ The Real ” and got on the cover. lol) Italian Job, Napster Sadly, this still isn’t good enough, the NFC reader has a 10–20cm range and who wants to put a card down on a table for that? If the magician has to deliver a set of rules to the spectator then he’s already leading them through a maze. I don’t want to make a maze, I want to make The Matrix. $300 and 5 days later, Sparkfun sent this bad boy to me. It’s the M6e simultaneous card reader. It can read multiple UHF RFID chips and from what they have told me, when used with an antenna, has a 10 meter range. Boom. I wired the Arduino to a Ethernet shield and plugged that into a wi-fi hotspot to make it mobile. I used PubNub to send the RFID data from the chip to my node server, it’s lightweight and I also used them for all my America’s Got Talent hacks, but that’s another story (I explained in my TED talk). I wanted to wear this thing in my jacket, so I had a USB bank too. Sadly, the m6e needs a HUGE amount of power, like 2–5amps at full power draw to get 10 meters range. Outsourcing a hacker The whole thing packed into a small case. Yes, I took this on a plane once. I was in over my head, I don’t know about the technical power ratings and numbers and things, but someone else does. Jumped onto Upwork (hire a freelancer website) and put a job up for someone who can make Arduino stuff, explained the chip etc. a few hours later someone came back to me. Robert, my god, what a gangsta. He worked at the US Navy or something, builds radios and stuff, such a solid guy. After $40 he had sent me a full wiring diagram and links to Amazon eletronics I need to buy, he even re-wrote my Arduino code. At this point, I had the entire thing wired up to a power converter pumping out 10amps of current when I needed it. I had to build it into a PC case with multiple fans to keep it cool. Back to Magic trick theory. If I can read someone’s mind just by looking at them ( I can’t, but I can make it look like that, by using magic) then by using this same method, it’s entirely feasible that I can teach this machine to do it, right? A company called saw my WIRED performance and sent me the Nova, a face tracking AI kit that uses OpenCV to control a robotic head. The robot would follow the user, tracking it’s eye movement and animating itself to look creepy. It runs on Arduino tech, allowing me to dynamically code it’s facial movements to sync with the Alexa speech triggers. This offered an emotional level to the AI along with with the camera placed in its right eye, it provided the perfect misdirection. Creoqode If a robot can track your face, moving its head to maintain eye contact, how hard is it then to convince people that it can also read your eye movements and work out what you’re thinking… especially if I do the same thing using ‘magic’ two minutes prior. The result. My RFID box can pretty much cover the entire stage with radio waves. Once a playing card enters that space, you just ask Alexa and she will read out what card is in the space. I had the spectator take a pack of cards, shuffle them, look at one and hide it so that they are the only person that can tell the audience what card they are imagining. What the didn’t know is that I had lined the playing card box with aluminium foil, creating a faraday cage. This blocks all the radio waves from the NFC reader I had placed on the side of the stage. After they take their card I ask them to put the cards back in the box. Essentially, the only only radio waves on stage at this point are the ones coming from the spectators chosen card, the other cards radio waves get blocked out. This prevented anyone from thinking I was using NFC because as we all know, you can’t read more than one NFC chip at once (but I can). Upon approaching the robotic head, the NFC reader is pinging the chip on the card and sending it up to the cloud for my Alexa to read out. However, what it would actually do is get the Alexa to read out all of the cards in the deck, then identify which card the spectator had chosen, pretending that it was looking at movements in the spectators eyes to decide what card they had picked. This final piece of misdirection gave the audience the last piece of the puzzle to lead them down the wrong trail, making them think the AI is looking at the spectator’s eyes to identify what they were thinking. In truth. I was performing a very advanced, never before seen or performed mind trick that magicians and spectators still fail to work out. Once layered under the showmanship of my robotic AI, I had the perfect deception. Why am I telling you this? Think about it for a second. A magician, a trickster, was able to use technology and our ignorance towards it to completely deceive a reputable and trusted news source. I was in New York at the time and it was aired on BBC World News several times over the period of a week, and even saw it at the airport when I was boarding. This is just the tip of the iceberg; my deceptions go darker into our inability to identify the line between real technology and trickery. I don’t do this because I think it’s funny, I don’t do it because I have a hate for ‘the system’. I do it because I genuinely think that most people have no idea what is possible with technology, how it works, or what the people who run most of it are actually doing. We live in a time where communication is driven by one company online. I sit and watch people use apps that are designed to make them do shocking things, whether it’s a free to play game or a social network, and I am blown away at how easy it is to people with them. control Whilst my passion is to shine a light on these phenonum through light hearted entertainment, some magicians have a darker purpose. Some build apps, websites and products that have been designed to change the way we think. I’m just one guy, in his flat, building new technologies to see if he can convince people what he does is magical and mystical. Just one guy. I pose a simple question. If we’re so distracted by the ‘neon lights’ emitted from mankind’s sci-fi creations, will we ever be able see the real intentions behind those inventing them?

How I hacked a news channel to report fake news.

Authors:
(1) Simone Silvestri, Massachusetts Institute of Technology, Cambridge, MA, USA;
(2) Gregory Wagner, Massachusetts Institute of Technology, Cambridge, MA, USA;
(3) Christopher Hill, Massachusetts Institute of Technology, Cambridge, MA, USA;
(4) Matin Raayai Ardakani, Northeastern University, Boston, MA, USA;
(5) Johannes Blaschke, Lawrence Berkeley National Laboratory, Berkeley, CA, USA;
(6) Valentin Churavy, Massachusetts Institute of Technology, Cambridge, MA, USA;
(7) Jean-Michel Campin, Massachusetts Institute of Technology, Cambridge, MA, USA;
(8) Navid Constantinou, Australian National University, Canberra, ACT, Australia;
(9) Alan Edelman, Massachusetts Institute of Technology, Cambridge, MA, USA;
(10) John Marshall, Massachusetts Institute of Technology, Cambridge, MA, USA;
(11) Ali Ramadhan, Massachusetts Institute of Technology, Cambridge, MA, USA;
(12) Andre Souza, Massachusetts Institute of Technology, Cambridge, MA, USA;
(13) Raffaele Ferrari, Massachusetts Institute of Technology, Cambridge, MA, USA. Authors: Authors: (1) Simone Silvestri, Massachusetts Institute of Technology, Cambridge, MA, USA; (2) Gregory Wagner, Massachusetts Institute of Technology, Cambridge, MA, USA; (3) Christopher Hill, Massachusetts Institute of Technology, Cambridge, MA, USA; (4) Matin Raayai Ardakani, Northeastern University, Boston, MA, USA; (5) Johannes Blaschke, Lawrence Berkeley National Laboratory, Berkeley, CA, USA; (6) Valentin Churavy, Massachusetts Institute of Technology, Cambridge, MA, USA; (7) Jean-Michel Campin, Massachusetts Institute of Technology, Cambridge, MA, USA; (8) Navid Constantinou, Australian National University, Canberra, ACT, Australia; (9) Alan Edelman, Massachusetts Institute of Technology, Cambridge, MA, USA; (10) John Marshall, Massachusetts Institute of Technology, Cambridge, MA, USA; (11) Ali Ramadhan, Massachusetts Institute of Technology, Cambridge, MA, USA; (12) Andre Souza, Massachusetts Institute of Technology, Cambridge, MA, USA; (13) Raffaele Ferrari, Massachusetts Institute of Technology, Cambridge, MA, USA. Table of Links Abstract and 1 Justification Abstract and 1 Justification 2 Performance Attributes 2 Performance Attributes 3 Overview of the Problem 3 Overview of the Problem 4 Current State of the Art 4 Current State of the Art 5 Innovations 5 Innovations 5.1 Starting from scratch with Julia 5.1 Starting from scratch with Julia 5.2 New numerical methods for finite volume fluid dynamics on the sphere 5.2 New numerical methods for finite volume fluid dynamics on the sphere 5.3 Optimization of ocean free surface dynamics for unprecedented GPU scalability 5.3 Optimization of ocean free surface dynamics for unprecedented GPU scalability 6 How performance was measured 6 How performance was measured 7 Performance Results and 7.1 Scaling Results 7 Performance Results and 7.1 Scaling Results 7.2 Energy efficiency 7.2 Energy efficiency 8 Implications 8 Implications 9 Acknowledgments and References 9 Acknowledgments and References 5.1 Starting from scratch with Julia Oceananigans.jl is an open-source library for ocean-flavored fluid dynamics written from scratch in Julia [7]. Julia is a dynamic high-level programming language that leverages Just-In-Time (JIT) compilation and LLVM [24] to achieve performance competitive with traditional HPC languages like C or Fortran. Julia has gathered interest as potential language for HPC [17, 10, 16, 21, 27] and provides easy integration with MPI [47, 38]. Most of Oceananigans.jl software is hardware-agnostic through the Julia package KernelAbstractions.jl [10], which enables performance portability targeting CPUs and different GPU vendors using the JuliaGPU [6, 5] software stack, similar to the capabilities provided by Kokkos [9], OCCA [30], and HIP [1]. To our knowledge, Oceananigans is the first ocean model written from scratch for GPUs, rather than ported from existing CPU code. Starting from scratch and using the Julia programming language allowed us to rethink the typical patterns used in ocean and atmosphere dynamical cores. In particular, we developed a system of composable atomic operators that leverages Julia’s functional programming paradigm and effective inlining capabilities to recursively construct large expression trees for calculus on staggered finite volume grids. Using this composable operator system, we fuse the entire tendency computation for each prognostic variable into a single compute-heavy kernel, each of which depends on only two intermediate diagnostic variables representing hydrostatic pressure and vertical diffusivity (which is treated implicitly using a predictor-corrector method). Such a high degree of abstraction yields a number of innovations: first, kernel fusion maximizes efficiency on GPUs. Second, almost all intermediate quantities are computed on-the-fly, so that Oceananigans is extremely memory efficient and can perform global ocean simulations at resolutions up to 1/4th degree on a single Nvidia V100. Finally, because all compute-heavy kernels rely on a single “tendency kernel function” applied at each grid index i, j, k, we can easily optimize performance by rapidly prototyping techniques to overlap computation and communication. The sparsity of kernels per time-step and small number of temporary variables mean that Oceananigans’ algorithmic structure is markedly different from current ocean models, which typically allocate 10 to 100 times the minimum necessary memory [4] and distribute computations across many small kernels [51]. We argue these algorithmic differences are a major factor in Oceananigans’ energy-efficiency and time-to-solution on GPU systems. 5.2 New numerical methods for finite volume fluid dynamics on the sphere Our results use Oceananigans.HydrostaticFreeSurfaceModel, which solves the hydrostatic Boussinesq equations in a finite volume framework on staggered C-grids [3]. Oceananigans’ hydrostatic model employs an implicit-explicit second-order Adams-Bashforth time stepping scheme. Vertically implicit diffusion is implemented with a backward Euler time-discretization and tridiagonal solver. A major innovation is a new adaptive-order scheme based on weighted essentially non-oscillatory (WENO) reconstructions [42] for advecting momentum and tracers on curvilinear finite-volume grids [43]. This new scheme automatically adapts to changing spatial resolution and permits stable, high-fidelity simulations of ocean turbulence without explicit dissipation or hyper-dissipation. This innovation reduces setup time when changing or increasing resolution while guaranteeing high-fidelity solutions that exhibit the minimum necessary dissipation of sharp, near-grid scale features. 5.3 Optimization of ocean free surface dynamics for unprecedented GPU scalability In hydrostatic ocean models with a free surface, the vertically-averaged, two-dimensional “barotropic mode” has dynamics orders of magnitude faster than the three-dimensional “baroclinic” component, and must be treated by a special “barotropic solver”. Due to communication overhead, barotropic solvers in current ocean models — whether implicit or explicit — are a major bottleneck that accounts for between 40% [22] to 60% [48, 36] of the cost of a typical IPCC-class ocean simulations. Oceananigans’ excellent scalability is enabled by an innovative optimization of the parallel barotropic solver. An increase in computation is traded in for decreased communication latency by leveraging the two-dimensionality of the barotropic problem. Our new barotropic solver is based on explicit subcycling of the barotropic mode. Increasing the width of the barotropic halo to equal the number of explicit subcycles (typically between 10–30) greatly decreases the frequency of communication. As a result, communication is required once per time-step rather than every subcycle, reducing the frequency of communication by a factor of 10 to 30. The cost of the barotropic solver is therefore less than 10% of the total cost of a time step. Due to the sparsity of communication enabled by our novel barotropic solver, all communication operations can be overlapped with computational workloads as sketched in figure 2. 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

From Code to Currents: Julia and GPU Magic Transform Ocean Modeling Efficiency

Authors:
(1) S M Rakib Hasan, Department of Computer Science and Engineering, BRAC University, Dhaka, Bangladesh (sm.rakib.hasan@g.bracu.ac.bd);
(2) Aakar Dhakal, Department of Computer Science and Engineering, BRAC University, Dhaka, Bangladesh (aakar.dhakal@g.bracu.ac.bd). Table of Links Abstract and I. Introduction II. Literature Review III. Methodology IV. Results and Discussion V. Conclusion and Future Work, and References **Abstract—**In the era of the internet and smart devices, the detection of malware has become crucial for system security. Malware authors increasingly employ obfuscation techniques to evade advanced security solutions, making it challenging to detect and eliminate threats. Obfuscated malware, adept at hiding itself, poses a significant risk to various platforms, including computers, mobile devices, and IoT devices. Conventional methods like heuristic-based or signature-based systems struggle against this type of malware, as it leaves no discernible traces on the system. In this research, we propose a simple and cost-effective obfuscated malware detection system through memory dump analysis, utilizing diverse machine-learning algorithms. The study focuses on the CIC-MalMem-2022 dataset, designed to simulate real-world scenarios and assess memory-based obfuscated malware detection. We evaluate the effectiveness of machine learning algorithms, such as decision trees, ensemble methods, and neural networks, in detecting obfuscated malware within memory dumps. Our analysis spans multiple malware categories, providing insights into algorithmic strengths and limitations. By offering a comprehensive assessment of machine learning algorithms for obfuscated malware detection through memory analysis, this paper contributes to ongoing efforts to enhance cybersecurity and fortify digital ecosystems against evolving and sophisticated malware threats. The source code is made open access for reproducibility and future research endeavors. It can be accessed at https://bit.ly/MalMemCode I. INTRODUCTION The rise of internet connectivity and smart devices has transformed various sectors, but it has also led to an evolving threat landscape, including sophisticated malware targeting interconnected systems. Obfuscated malware, adept at concealing itself, presents a significant challenge to conventional cybersecurity methods. Traditional heuristic-based or signature-based systems struggle to identify such elusive threats, necessitating a shift towards innovative and adaptive detection mechanisms. This paper explores obfuscated malware detection through multiclass classification, aiming to bridge the gap between evolving threats and advanced detection methods using machine learning. We analyze various algorithms, including decision trees, ensemble methods, support vector machines, and neural networks, to uncover their capabilities and limitations in identifying obfuscated malware. Acknowledging the significance of class imbalance in real-world datasets, especially in malware detection, we investigate techniques such as under sampling (Edited Nearest Neighbor Rule, Near Miss Rule, Random Under sampling, and All KNN Under sampling) and synthetic data generation using the ADASYN method to address this challenge. Our research, based on the CIC-MalMem-2022 dataset, simulates real-world scenarios for memory-based obfuscated malware detection. By meticulously analyzing machine learning algorithms and data balancing techniques, we contribute to fortifying cybersecurity against evolving malware threats. In the following sections, we delve into our dataset, methodologies, and results, aiming to provide valuable insights that can shape the future of malware detection and cybersecurity strategies amidst the challenges posed by obfuscated malware and class imbalance. This paper is available on arxiv under CC BY-SA 4.0 DEED license. Authors: (1) S M Rakib Hasan, Department of Computer Science and Engineering, BRAC University, Dhaka, Bangladesh (sm.rakib.hasan@g.bracu.ac.bd); (2) Aakar Dhakal, Department of Computer Science and Engineering, BRAC University, Dhaka, Bangladesh (aakar.dhakal@g.bracu.ac.bd). Authors: Authors: (1) S M Rakib Hasan, Department of Computer Science and Engineering, BRAC University , Dhaka, Bangladesh (sm.rakib.hasan@g.bracu.ac.bd); Department of Computer Science and Engineering, BRAC University (2) Aakar Dhakal, Department of Computer Science and Engineering, BRAC University, Dhaka, Bangladesh (aakar.dhakal@g.bracu.ac.bd). Department of Computer Science and Engineering, BRAC University, Table of Links Abstract and I. Introduction Abstract and I. Introduction II. Literature Review II. Literature Review III. Methodology III. Methodology IV. Results and Discussion IV. Results and Discussion V. Conclusion and Future Work, and References V. Conclusion and Future Work, and References ** Abstract —**In the era of the internet and smart devices, the detection of malware has become crucial for system security. Malware authors increasingly employ obfuscation techniques to evade advanced security solutions, making it challenging to detect and eliminate threats. Obfuscated malware, adept at hiding itself, poses a significant risk to various platforms, including computers, mobile devices, and IoT devices. Conventional methods like heuristic-based or signature-based systems struggle against this type of malware, as it leaves no discernible traces on the system. In this research, we propose a simple and cost-effective obfuscated malware detection system through memory dump analysis, utilizing diverse machine-learning algorithms. The study focuses on the CIC-MalMem-2022 dataset, designed to simulate real-world scenarios and assess memory-based obfuscated malware detection. We evaluate the effectiveness of machine learning algorithms, such as decision trees, ensemble methods, and neural networks, in detecting obfuscated malware within memory dumps. Our analysis spans multiple malware categories, providing insights into algorithmic strengths and limitations. By offering a comprehensive assessment of machine learning algorithms for obfuscated malware detection through memory analysis, this paper contributes to ongoing efforts to enhance cybersecurity and fortify digital ecosystems against evolving and sophisticated malware threats. The source code is made open access for reproducibility and future research endeavors. It can be accessed at https://bit.ly/MalMemCode Abstract I. INTRODUCTION The rise of internet connectivity and smart devices has transformed various sectors, but it has also led to an evolving threat landscape, including sophisticated malware targeting interconnected systems. Obfuscated malware, adept at concealing itself, presents a significant challenge to conventional cybersecurity methods. Traditional heuristic-based or signature-based systems struggle to identify such elusive threats, necessitating a shift towards innovative and adaptive detection mechanisms. This paper explores obfuscated malware detection through multiclass classification, aiming to bridge the gap between evolving threats and advanced detection methods using machine learning. We analyze various algorithms, including decision trees, ensemble methods, support vector machines, and neural networks, to uncover their capabilities and limitations in identifying obfuscated malware. Acknowledging the significance of class imbalance in real-world datasets, especially in malware detection, we investigate techniques such as under sampling (Edited Nearest Neighbor Rule, Near Miss Rule, Random Under sampling, and All KNN Under sampling) and synthetic data generation using the ADASYN method to address this challenge. Our research, based on the CIC-MalMem-2022 dataset, simulates real-world scenarios for memory-based obfuscated malware detection. By meticulously analyzing machine learning algorithms and data balancing techniques, we contribute to fortifying cybersecurity against evolving malware threats. In the following sections, we delve into our dataset, methodologies, and results, aiming to provide valuable insights that can shape the future of malware detection and cybersecurity strategies amidst the challenges posed by obfuscated malware and class imbalance. This paper is available on arxiv under CC BY-SA 4.0 DEED license. This paper is available on arxiv under CC BY-SA 4.0 DEED license. available on arxiv

Hide and Seek in Memory: Outsmarting Sneaky Malware with Data Magic

Errors in a PowerShell script can prevent successful execution. Implementing try-catch blocks enables error management and response. This post covers try/catch basics and how to handle custom error messages in PowerShell. Effective error handling saves troubleshooting time and improves user experience. PowerShell offers robust options for exception management with try, catch, and finally blocks. Learn to use try-catch for graceful error handling and to add custom error messages for enhanced feedback. Why Use Exception Handling in PowerShell? Scripts can fail for many reasons: missing files, invalid input, or network issues, to name a few. With exception handling, you can capture these issues, inform users in a friendly way, and potentially recover from errors without crashing your script. Using try-catch, you can: Catch specific errors.
Display user-friendly messages.
Log errors for debugging. Syntax overview of Try/Catch Like similar in other programming languages, the try-catch block syntax is very simple and syntax will be the same. It is framed with two sections enclosed in curly brackets (the first block is a try and the second is the catch block). try { 

#Functionality within try block 

} 

catch 

{ 

#Action to do with errors 

} The main purpose of using the try-catch block, we can start to manipulate the error output and make it more friendly for the user. Example 1: After executing the below script, the below error will be shown on the screen as output and it would occupy some space and the problem may not be immediately visible to the User. So you can use a try-catch block to manipulate the error output and make it more friendly. without Try-Catch block Get-content -Path “C:\dotnet-helpers\BLOG\TestFiled.txt” with Try Catch block In the below script, we added the ErrorAction parameter with a value of Stop to the command. Not all errors are considered “terminating”, so sometimes we need to add this bit of code in order to properly terminate into the catch block. try {

Get-content -Path “C:\dotnet-helpers\BLOG\TestFile.txt” -ErrorAction Stop

}

catch { 

Write-Warning -Message “Can’t read the file, seem there is an issue”

} Example 2: Using the $Error Variable To improve the code and follow best practices, consider the following improvements: Use More Descriptive Error Messages: When handling errors, it's useful to log or display meaningful error messages rather than generic ones. If you mention a custom message, ensure it provides useful information to the user.
Avoid Hardcoding Indexes: Instead of hardcoding the index to access $Error[0], consider using .First() for better readability and understanding of what exactly you're accessing (especially in PowerShell). Here's a refined version of how you might handle errors using $Error: try{
 
Get-content -Path "G:\dotnet-helpers\BLOG\TestFiled.txt" -ErrorAction Stop
}
# It will execute if a specific file is not found in a specific Directory
Catch [System.IO.DirectoryNotFoundException] {
 
Write-Warning -Message "Can't read the file, seems there is an issue"
Write-Warning $Error[0]
}
# It will execute if the specified driver is not found in the specified path
Catch [System.Management.Automation.DriveNotFoundException]{
Write-Warning -Message "Custom Message: Specific driver is not found"
Write-Warning $Error[0]
 
}
#Execute for Un-Handled exception - This catch block will run if the error does not match any other catch block exception.
Catch{
Write-Warning -Message "Oops, An un-expected Error Occurred"
#It will return the exception message for the last error that occurred.
Write-host $Error[0].Exception.GetType().FullName
} Errors in a PowerShell script can prevent successful execution. Implementing try-catch blocks enables error management and response. This post covers try/catch basics and how to handle custom error messages in PowerShell. Effective error handling saves troubleshooting time and improves user experience. PowerShell offers robust options for exception management with try , catch , and finally blocks. Learn to use try-catch for graceful error handling and to add custom error messages for enhanced feedback. PowerShell script PowerShell script try catch finally try-catch error error Why Use Exception Handling in PowerShell? Scripts can fail for many reasons: missing files, invalid input, or network issues, to name a few. With exception handling, you can capture these issues, inform users in a friendly way, and potentially recover from errors without crashing your script. Using try-catch , you can: try-catch Catch specific errors. Display user-friendly messages. Log errors for debugging. Catch specific errors. Display user-friendly messages. Log errors for debugging. Syntax overview of Try/Catch Syntax overview of Try/Catch Like similar in other programming languages, the try-catch block syntax is very simple and syntax will be the same. It is framed with two sections enclosed in curly brackets (the first block is a try and the second is the catch block). try { 

#Functionality within try block 

} 

catch 

{ 

#Action to do with errors 

} try { 

#Functionality within try block 

} 

catch 

{ 

#Action to do with errors 

} The main purpose of using the try-catch block, we can start to manipulate the error output and make it more friendly for the user. Example 1: Example 1: After executing the below script, the below error will be shown on the screen as output and it would occupy some space and the problem may not be immediately visible to the User. So you can use a try-catch block to manipulate the error output and make it more friendly. without Try-Catch block without Try-Catch block without Try-Catch block Get-content -Path “C:\dotnet-helpers\BLOG\TestFiled.txt” Get-content -Path “C:\dotnet-helpers\BLOG\TestFiled.txt” with Try Catch block with Try Catch block with Try Catch block In the below script, we added the ErrorAction parameter with a value of Stop to the command. Not all errors are considered “terminating”, so sometimes we need to add this bit of code in order to properly terminate into the catch block. ErrorAction Stop try {

Get-content -Path “C:\dotnet-helpers\BLOG\TestFile.txt” -ErrorAction Stop

}

catch { 

Write-Warning -Message “Can’t read the file, seem there is an issue”

} try {

Get-content -Path “C:\dotnet-helpers\BLOG\TestFile.txt” -ErrorAction Stop

}

catch { 

Write-Warning -Message “Can’t read the file, seem there is an issue”

} Example 2: Example 2: Using the $Error Variable Using the $Error Variable Using the $Error Variable $Error To improve the code and follow best practices, consider the following improvements: Use More Descriptive Error Messages: When handling errors, it's useful to log or display meaningful error messages rather than generic ones. If you mention a custom message, ensure it provides useful information to the user. Avoid Hardcoding Indexes: Instead of hardcoding the index to access $Error[0], consider using .First() for better readability and understanding of what exactly you're accessing (especially in PowerShell). Use More Descriptive Error Messages: When handling errors, it's useful to log or display meaningful error messages rather than generic ones. If you mention a custom message, ensure it provides useful information to the user. Use More Descriptive Error Messages: Avoid Hardcoding Indexes: Instead of hardcoding the index to access $Error[0] , consider using .First() for better readability and understanding of what exactly you're accessing (especially in PowerShell). Avoid Hardcoding Indexes: $Error[0] .First() Here's a refined version of how you might handle errors using $Error : $Error try{
 
Get-content -Path "G:\dotnet-helpers\BLOG\TestFiled.txt" -ErrorAction Stop
}
# It will execute if a specific file is not found in a specific Directory
Catch [System.IO.DirectoryNotFoundException] {
 
Write-Warning -Message "Can't read the file, seems there is an issue"
Write-Warning $Error[0]
}
# It will execute if the specified driver is not found in the specified path
Catch [System.Management.Automation.DriveNotFoundException]{
Write-Warning -Message "Custom Message: Specific driver is not found"
Write-Warning $Error[0]
 
}
#Execute for Un-Handled exception - This catch block will run if the error does not match any other catch block exception.
Catch{
Write-Warning -Message "Oops, An un-expected Error Occurred"
#It will return the exception message for the last error that occurred.
Write-host $Error[0].Exception.GetType().FullName
} try{
 
Get-content -Path "G:\dotnet-helpers\BLOG\TestFiled.txt" -ErrorAction Stop
}
# It will execute if a specific file is not found in a specific Directory
Catch [System.IO.DirectoryNotFoundException] {
 
Write-Warning -Message "Can't read the file, seems there is an issue"
Write-Warning $Error[0]
}
# It will execute if the specified driver is not found in the specified path
Catch [System.Management.Automation.DriveNotFoundException]{
Write-Warning -Message "Custom Message: Specific driver is not found"
Write-Warning $Error[0]
 
}
#Execute for Un-Handled exception - This catch block will run if the error does not match any other catch block exception.
Catch{
Write-Warning -Message "Oops, An un-expected Error Occurred"
#It will return the exception message for the last error that occurred.
Write-host $Error[0].Exception.GetType().FullName
}

How to Stop Your Scripts from Crashing with Try-Catch Magic

Hello 👋 How often have you wished for a method that doesn't exist on collections or string helpers? You start chaining methods, only to hit a wall when one of them turns out to be missing. Honestly, it's understandable; frameworks, you know, are a one-size-fits-all thing. I found myself in this situation multiple times. Every time, before diving into how to extend the framework, I check to see if what I want to extend is macroable or not. But what does that mean? That's exactly what we'll be exploring! WTF Are Macros? 🍏 Let's say we have this JWT: $jwt = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c'; And we need to extract the headers: str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson(); // does not exist 😞

//  BadMethodCallException  Method Illuminate\Support\Stringable::fromJson does not exist. The fromJson() doesn't exist 😔 Sure, one could simply do: json_decode(str($jwt)->before('.')->fromBase64()); But where's the fun in that? Plus, it is my article 🤷 So, we need a way to extend the Stringable class. There are a few ways to do this, but Laravel thought ahead, it knew that developers might want to add custom methods, so it made the class macroable, or as I like to call it, extendable. If you inspect the Illuminate\Support\Stringable class, you'll see it uses a Macroable trait. Let's go ahead and extend the class. In the AppServiceProvider, add the following: <?php

namespace App\Providers;

use Illuminate\Support\Stringable;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        Stringable::macro('fromJson', function (bool $associative = true) {
            return json_decode($this->value, $associative);
        });
    }
} Now, let's rerun the code: str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson();

// ["alg" => "HS256", "typ" => "JWT"] It works perfectly 🎉 But now, you might be wondering, how did this work? And what exactly is $this->value? What in the Harry Potter is going on? Unveiling the Magic 🪄 We know that the Stringable class uses the Macroable trait, which provides the macro() method. Let's take a closer look at what it does: // src/Illuminate/Macroable/Traits/Macroable.php

/**
 * Register a custom macro.
 *
 * @param  string  $name
 * @param  object|callable  $macro
 *
 * @param-closure-this static  $macro
 *
 * @return void
 */
public static function macro($name, $macro)
{
    static::$macros[$name] = $macro;
} It's pretty straightforward; it just saves the callback to a static macros array. Now, if we inspect the trait further, we will find the __call method, which is triggered every time a non-existent method is called. In our case, that's fromJson(). Let's dive in: /**
 * Dynamically handle calls to the class.
 *
 * @param  string  $method
 * @param  array  $parameters
 * @return mixed
 *
 * @throws \BadMethodCallException
 */
public function __call($method, $parameters)
{
    if (! static::hasMacro($method)) {
        throw new BadMethodCallException(sprintf(
            'Method %s::%s does not exist.', static::class, $method
        ));
    }

    $macro = static::$macros[$method];

    if ($macro instanceof Closure) {
        $macro = $macro->bindTo($this, static::class);
    }

    return $macro(...$parameters);
} First, it checks if a macro is registered, which is the case with fromJson(), it then fetches the callback (or object) from the macros array. Now, for the magic trick; if the macro is a closure (as in our case), it calls bindTo() which essentially tells the closure that $this should refer to whatever is passed as the first argument. In this case, it is the Stringable instance, which happens to have the $value attribute. // $this here is the stringable
// $this inside the closure is now referencing the stringable class
$macro->bindTo($this, static::class); And this is why we can do $this->value. We Can Do Better: Mixins 🧩 There is one more thing I want to show you! When we extend the same class a couple of times, the service provider might get messy very quickly. We can extract all our custom macros to a class called a Mixin. Let's create a StringableMixin: <?php

namespace App\Macros;

use Closure;

class StringableMixin
{
    public function fromJson(): Closure
    {
        return function (bool $associative = true) {
            json_decode($this->value, $associative);
        };
    }

    // Add more macros here as needed
} Now, in AppServiceProvider, we can register this mixin: use App\Macros\StringableMixin;
use Illuminate\Support\Stringable;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        Stringable::mixin(new StringableMixin);
    }
} And that's it! Now, we can do: str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson(); Which is basically the same, just a bit cleaner. If you are curious about how this works, the mixin() method on the Macroable trait uses the reflection API. It retrieves all the public methods from the Mixin class, expects each to return a closure, and then registers the closure as a macro just like we have seen earlier. The Poor IDE 🥲 Well, as you have seen, there is a lot of magic going on, and the IDE wouldn't know about the defined macros. If you're working within a team, other developers won't know about these macros either, which is not good. Luckily, there are tools to help you with that. A free and open-source option is the Laravel IDE helper package. You can install the package and generate the _ide_helper.php file, and you should be good to go. And So It Ends.. Our example is fairly simple, but you can push macros much further than this, as most of the common classes Laravel ships with are macroable. For instance, you can add a new apiResponse() macro, or anything that you feel is very common in your app's logic and is being repeated more than it should be. But don't overdo it. Macros add a new layer of complexity, and when working in a team, they could be confusing. So, whenever you feel something is missing from your application, but not from the framework itself, use macros 🪄 Hello 👋 How often have you wished for a method that doesn't exist on collections or string helpers? You start chaining methods, only to hit a wall when one of them turns out to be missing. Honestly, it's understandable; frameworks, you know, are a one-size-fits-all thing. I found myself in this situation multiple times. Every time, before diving into how to extend the framework, I check to see if what I want to extend is macroable or not. But what does that mean? That's exactly what we'll be exploring! macroable WTF Are Macros? 🍏 Let's say we have this JWT: $jwt = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c'; $jwt = 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c'; And we need to extract the headers: str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson(); // does not exist 😞

//  BadMethodCallException  Method Illuminate\Support\Stringable::fromJson does not exist. str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson(); // does not exist 😞

//  BadMethodCallException  Method Illuminate\Support\Stringable::fromJson does not exist. The fromJson() doesn't exist 😔 Sure, one could simply do: fromJson() json_decode(str($jwt)->before('.')->fromBase64()); json_decode(str($jwt)->before('.')->fromBase64()); But where's the fun in that? Plus, it is my article 🤷 So, we need a way to extend the Stringable class. There are a few ways to do this, but Laravel thought ahead, it knew that developers might want to add custom methods, so it made the class macroable , or as I like to call it, extendable. Stringable macroable If you inspect the Illuminate\Support\Stringable class, you'll see it uses a Macroable trait. If you inspect the Illuminate\Support\Stringable class, you'll see it uses a Macroable trait. Illuminate\Support\Stringable Macroable Let's go ahead and extend the class. In the AppServiceProvider , add the following: AppServiceProvider <?php

namespace App\Providers;

use Illuminate\Support\Stringable;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        Stringable::macro('fromJson', function (bool $associative = true) {
            return json_decode($this->value, $associative);
        });
    }
} <?php

namespace App\Providers;

use Illuminate\Support\Stringable;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        Stringable::macro('fromJson', function (bool $associative = true) {
            return json_decode($this->value, $associative);
        });
    }
} Now, let's rerun the code: str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson();

// ["alg" => "HS256", "typ" => "JWT"] str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson();

// ["alg" => "HS256", "typ" => "JWT"] It works perfectly 🎉 But now, you might be wondering, how did this work? And what exactly is $this->value ? What in the Harry Potter is going on? $this->value Unveiling the Magic 🪄 We know that the Stringable class uses the Macroable trait, which provides the macro() method. Let's take a closer look at what it does: Stringable Macroable macro() // src/Illuminate/Macroable/Traits/Macroable.php

/**
 * Register a custom macro.
 *
 * @param  string  $name
 * @param  object|callable  $macro
 *
 * @param-closure-this static  $macro
 *
 * @return void
 */
public static function macro($name, $macro)
{
    static::$macros[$name] = $macro;
} // src/Illuminate/Macroable/Traits/Macroable.php

/**
 * Register a custom macro.
 *
 * @param  string  $name
 * @param  object|callable  $macro
 *
 * @param-closure-this static  $macro
 *
 * @return void
 */
public static function macro($name, $macro)
{
    static::$macros[$name] = $macro;
} It's pretty straightforward; it just saves the callback to a static macros array. Now, if we inspect the trait further, we will find the __call method, which is triggered every time a non-existent method is called. In our case, that's fromJson() . Let's dive in: macros __call fromJson() /**
 * Dynamically handle calls to the class.
 *
 * @param  string  $method
 * @param  array  $parameters
 * @return mixed
 *
 * @throws \BadMethodCallException
 */
public function __call($method, $parameters)
{
    if (! static::hasMacro($method)) {
        throw new BadMethodCallException(sprintf(
            'Method %s::%s does not exist.', static::class, $method
        ));
    }

    $macro = static::$macros[$method];

    if ($macro instanceof Closure) {
        $macro = $macro->bindTo($this, static::class);
    }

    return $macro(...$parameters);
} /**
 * Dynamically handle calls to the class.
 *
 * @param  string  $method
 * @param  array  $parameters
 * @return mixed
 *
 * @throws \BadMethodCallException
 */
public function __call($method, $parameters)
{
    if (! static::hasMacro($method)) {
        throw new BadMethodCallException(sprintf(
            'Method %s::%s does not exist.', static::class, $method
        ));
    }

    $macro = static::$macros[$method];

    if ($macro instanceof Closure) {
        $macro = $macro->bindTo($this, static::class);
    }

    return $macro(...$parameters);
} First, it checks if a macro is registered, which is the case with fromJson() , it then fetches the callback (or object) from the macros array. Now, for the magic trick; if the macro is a closure (as in our case), it calls bindTo() which essentially tells the closure that $this should refer to whatever is passed as the first argument. In this case, it is the Stringable instance, which happens to have the $value attribute. fromJson() bindTo() $this Stringable $value // $this here is the stringable
// $this inside the closure is now referencing the stringable class
$macro->bindTo($this, static::class); // $this here is the stringable
// $this inside the closure is now referencing the stringable class
$macro->bindTo($this, static::class); And this is why we can do $this->value . $this->value We Can Do Better: Mixins 🧩 There is one more thing I want to show you! When we extend the same class a couple of times, the service provider might get messy very quickly. We can extract all our custom macros to a class called a Mixin. Let's create a StringableMixin : StringableMixin <?php

namespace App\Macros;

use Closure;

class StringableMixin
{
    public function fromJson(): Closure
    {
        return function (bool $associative = true) {
            json_decode($this->value, $associative);
        };
    }

    // Add more macros here as needed
} <?php

namespace App\Macros;

use Closure;

class StringableMixin
{
    public function fromJson(): Closure
    {
        return function (bool $associative = true) {
            json_decode($this->value, $associative);
        };
    }

    // Add more macros here as needed
} Now, in AppServiceProvider , we can register this mixin: AppServiceProvider use App\Macros\StringableMixin;
use Illuminate\Support\Stringable;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        Stringable::mixin(new StringableMixin);
    }
} use App\Macros\StringableMixin;
use Illuminate\Support\Stringable;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        Stringable::mixin(new StringableMixin);
    }
} And that's it! Now, we can do: str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson(); str($jwt)
    ->before('.')
    ->fromBase64()
    ->fromJson(); Which is basically the same, just a bit cleaner. Which is basically the same, just a bit cleaner. If you are curious about how this works, the mixin() method on the Macroable trait uses the reflection API . It retrieves all the public methods from the Mixin class, expects each to return a closure, and then registers the closure as a macro just like we have seen earlier. mixin() Macroable reflection API The Poor IDE 🥲 Well, as you have seen, there is a lot of magic going on, and the IDE wouldn't know about the defined macros. If you're working within a team, other developers won't know about these macros either, which is not good. Luckily, there are tools to help you with that. A free and open-source option is the Laravel IDE helper package. Laravel IDE helper You can install the package and generate the _ide_helper.php file, and you should be good to go. _ide_helper.php And So It Ends.. Our example is fairly simple, but you can push macros much further than this, as most of the common classes Laravel ships with are macroable. For instance, you can add a new apiResponse() macro, or anything that you feel is very common in your app's logic and is being repeated more than it should be. But don't overdo it. Macros add a new layer of complexity, and when working in a team, they could be confusing. apiResponse() So, whenever you feel something is missing from your application, but not from the framework itself, use macros 🪄

Laravel Under The Hood - The Magic of Macros

Have you ever found yourself frustrated by distracting people, logos, or background clutter that disrupts the visual harmony of your photos? This problem can be particularly aggravating for photographers and content creators who strive for perfection. Introducting MagicEraser.Pro, an innovative AI-powered tool designed to tackle these challenges head-on. By leveraging advanced algorithms, MagicEraser.Pro allows users to effortlessly remove unwanted objects from their images, transforming them into polished works of art. In this review, we will explore how this tool works, its key features, and whether it truly lives up to the hype in enhancing your photo editing experience. What is MagicEraser.Pro? MagicEraser.Pro is an advanced AI tool designed to simplify the process of removing unwanted elements from images. It allows users to effortlessly eliminate distractions such as people, objects, and text, ensuring that the focus remains on the intended subject. With a user-friendly interface, MagicEraser.Pro caters to both novices and experienced editors, making it accessible for various applications, from real estate to e-commerce. The tool supports multiple image formats and boasts features like batch editing, enabling users to modify several photos simultaneously. Its precision in object removal is powered by sophisticated algorithms that ensure clean edits without leaving behind artifacts. Additionally, the Pro version offers high-resolution downloads and priority support, enhancing the overall user experience. Overall, it stands out as a versatile asset for anyone looking to enhance their photo editing workflow with efficiency and ease. When Can You Use MagicEraser? MagicEraser.Pro offers a seamless solution for refining your photographs and removing unwanted elements. Explore the numerous ways you can utilize MagicEraser.Pro to elevate your images. Removing People from Photos Swiftly clear out unwanted figures, like random tourists or event spectators, to keep the spotlight on your intended subject. Eliminating Text and Logos Wipe away any distracting text, captions, or logos to craft images that are clean and visually striking. Enhancing Image Focus Trim away background distractions such as buildings, trees, or clutter to accentuate the main subject of your photograph. Getting Rid of Watermarks Effortlessly erase obtrusive watermarks, date stamps, or location markers that detract from the overall beauty of your images. Improving Image Quality Seamlessly eliminate eyesores like litter, power lines, or unwanted shadows, resulting in a polished and professional appearance. Correcting Imperfections Refine your photos by removing minor flaws like scratches, dust, or stains, ensuring every detail shines with clarity. MagicEraser.Pro is designed for photographers, graphic designers, and hobbyists seeking an efficient and user-friendly tool to optimize their images. What's The Standout Benefits of This Magic Eraser? The following features collectively make MagicEraser.Pro a versatile and powerful tool for anyone looking to enhance their photography with ease. Free to Use: Completely free with unlimited usage after a simple sign-up, making it accessible for everyone. High-Quality Results: Utilizes advanced image processing technology to deliver clear and precise edits, ensuring excellent image quality. Quick and Simple: Streamlined interface allows for fast removal of unwanted elements, perfect for busy professionals and casual users alike. User-Friendly Interface: Intuitive design that makes it easy for anyone to navigate and use the tool effectively, regardless of their technical skill level. Batch Processing: Ability to edit multiple images at once, saving time for users who need to enhance several photos quickly. Real-Time Preview: See changes in real-time as you edit, allowing for immediate adjustments and ensuring satisfaction with the final result. Supports Various Formats: Compatible with popular image formats like JPG, PNG, and WebP, providing flexibility in editing. How to Remove Unwanted Objects from Photo With MagicEraser.Pro? Follow these simple steps to experience the magic of MagicEraser.Pro: Step 1: Upload Your Image Begin by uploading your image to the MagicEraser.Pro platform. The tool supports popular formats such as JPG, PNG, AVIF, and WEBP, ensuring compatibility with a wide range of image files. Please note that the maximum file size allowed is 50MB. Step 2: Select the Element to Erase Using the intuitive selection tool, mark the area or object you wish to remove from your photo. The AI-powered algorithm will automatically detect and select the marked area, making the process quick and easy. Step 3: Review and Refine Once the AI has selected the marked area, review the selection to ensure accuracy. You can refine the selection using the available tools, such as the Brush or Lasso tool, for precise adjustments. Step 4: Erase and Save After finalizing your selection, let MagicEraser.Pro work its magic by clicking the "Erase" button. In just a few moments, the unwanted element will be seamlessly removed from your photo. Save your edited image and admire the stunning results! Wrap Ups MagicEraser.Pro is the perfect solution for photographers, graphic designers, and hobbyists looking to optimize their images without the hassle of traditional editing software. Experience the future of image editing with MagicEraser.Pro – visit the website today and discover a world of endless creative possibilities. This story was distributed by Margrowth under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author Have you ever found yourself frustrated by distracting people, logos, or background clutter that disrupts the visual harmony of your photos? This problem can be particularly aggravating for photographers and content creators who strive for perfection. Introducting MagicEraser.Pro , an innovative AI-powered tool designed to tackle these challenges head-on. By leveraging advanced algorithms, MagicEraser.Pro allows users to effortlessly remove unwanted objects from their images, transforming them into polished works of art. MagicEraser.Pro MagicEraser.Pro In this review, we will explore how this tool works, its key features, and whether it truly lives up to the hype in enhancing your photo editing experience. What is MagicEraser.Pro? MagicEraser.Pro is an advanced AI tool designed to simplify the process of removing unwanted elements from images. It allows users to effortlessly eliminate distractions such as people, objects, and text, ensuring that the focus remains on the intended subject. With a user-friendly interface, MagicEraser.Pro caters to both novices and experienced editors, making it accessible for various applications, from real estate to e-commerce. The tool supports multiple image formats and boasts features like batch editing, enabling users to modify several photos simultaneously. Its precision in object removal is powered by sophisticated algorithms that ensure clean edits without leaving behind artifacts. Additionally, the Pro version offers high-resolution downloads and priority support, enhancing the overall user experience. Overall, it stands out as a versatile asset for anyone looking to enhance their photo editing workflow with efficiency and ease. When Can You Use MagicEraser? MagicEraser.Pro offers a seamless solution for refining your photographs and removing unwanted elements. Explore the numerous ways you can utilize MagicEraser.Pro to elevate your images. Removing People from Photos Swiftly clear out unwanted figures, like random tourists or event spectators, to keep the spotlight on your intended subject. Eliminating Text and Logos Wipe away any distracting text, captions, or logos to craft images that are clean and visually striking. Enhancing Image Focus Trim away background distractions such as buildings, trees, or clutter to accentuate the main subject of your photograph. Getting Rid of Watermarks Effortlessly erase obtrusive watermarks, date stamps, or location markers that detract from the overall beauty of your images. Improving Image Quality Seamlessly eliminate eyesores like litter, power lines, or unwanted shadows, resulting in a polished and professional appearance. Correcting Imperfections Refine your photos by removing minor flaws like scratches, dust, or stains, ensuring every detail shines with clarity. MagicEraser.Pro is designed for photographers, graphic designers, and hobbyists seeking an efficient and user-friendly tool to optimize their images. What's The Standout Benefits of This Magic Eraser? The following features collectively make MagicEraser.Pro a versatile and powerful tool for anyone looking to enhance their photography with ease. Free to Use: Completely free with unlimited usage after a simple sign-up, making it accessible for everyone. Free to Use: Completely free with unlimited usage after a simple sign-up, making it accessible for everyone. High-Quality Results: Utilizes advanced image processing technology to deliver clear and precise edits, ensuring excellent image quality. High-Quality Results: Utilizes advanced image processing technology to deliver clear and precise edits, ensuring excellent image quality. Quick and Simple: Streamlined interface allows for fast removal of unwanted elements, perfect for busy professionals and casual users alike. Quick and Simple: Streamlined interface allows for fast removal of unwanted elements, perfect for busy professionals and casual users alike. User-Friendly Interface: Intuitive design that makes it easy for anyone to navigate and use the tool effectively, regardless of their technical skill level. User-Friendly Interface: Intuitive design that makes it easy for anyone to navigate and use the tool effectively, regardless of their technical skill level. Batch Processing: Ability to edit multiple images at once, saving time for users who need to enhance several photos quickly. Batch Processing: Ability to edit multiple images at once, saving time for users who need to enhance several photos quickly. Real-Time Preview: See changes in real-time as you edit, allowing for immediate adjustments and ensuring satisfaction with the final result. Real-Time Preview: See changes in real-time as you edit, allowing for immediate adjustments and ensuring satisfaction with the final result. Supports Various Formats: Compatible with popular image formats like JPG, PNG, and WebP, providing flexibility in editing. Supports Various Formats: Compatible with popular image formats like JPG, PNG, and WebP, providing flexibility in editing. How to Remove Unwanted Objects from Photo With MagicEraser.Pro? Follow these simple steps to experience the magic of MagicEraser.Pro: Step 1: Upload Your Image Begin by uploading your image to the MagicEraser.Pro platform. The tool supports popular formats such as JPG, PNG, AVIF, and WEBP, ensuring compatibility with a wide range of image files. Please note that the maximum file size allowed is 50MB. Step 2: Select the Element to Erase Using the intuitive selection tool, mark the area or object you wish to remove from your photo. The AI-powered algorithm will automatically detect and select the marked area, making the process quick and easy. Step 3: Review and Refine Once the AI has selected the marked area, review the selection to ensure accuracy. You can refine the selection using the available tools, such as the Brush or Lasso tool, for precise adjustments. Step 4: Erase and Save After finalizing your selection, let MagicEraser.Pro work its magic by clicking the "Erase" button. In just a few moments, the unwanted element will be seamlessly removed from your photo. Save your edited image and admire the stunning results! Wrap Ups MagicEraser.Pro is the perfect solution for photographers, graphic designers, and hobbyists looking to optimize their images without the hassle of traditional editing software. Experience the future of image editing with MagicEraser.Pro – visit the website today and discover a world of endless creative possibilities. This story was distributed by Margrowth under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author This story was distributed by Margrowth under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author This story was distributed by Margrowth under HackerNoon’s Brand As An Author Program. Learn more about the program here: https://business.hackernoon.com/brand-as-author https://business.hackernoon.com/brand-as-author

MagicEraser.Pro Review: Effortlessly Enhance Your Photos With AI Magic Eraser

مراجعة MagicEraser.Pro: قم بتحسين صورك بسهولة باستخدام AI Magic Eraser

Recenze MagicEraser.Pro: Vylepšete své fotografie bez námahy pomocí AI Magic Eraser

Αναθεώρηση MagicEraser.Pro: Βελτιώστε εύκολα τις φωτογραφίες σας με το AI Magic Eraser

Reseña de MagicEraser.Pro: Mejore sus fotos sin esfuerzo con AI Magic Eraser

סקירת MagicEraser.Pro: שפר את התמונות שלך ללא מאמץ עם AI Magic Eraser

MagicEraser.Pro レビュー: AI マジック消しゴムで写真を簡単に補正

MagicEraser.Pro apskats: bez piepūles uzlabojiet savus fotoattēlus, izmantojot AI Magic Eraser

Преглед на MagicEraser.Pro: Подобрете ги вашите фотографии без напор со AI Magic Eraser

MagicEraser.Pro тойм: AI Magic Eraser ашиглан зургуудаа хялбархан сайжруулаарай

MagicEraser.Pro Review: Verbeter uw foto's moeiteloos met AI Magic Eraser

MagicEraser.Pro Review: Antswisa Swifaniso Swa Wena Handle Ka Matshalatshala Hi AI Magic Eraser

Uphononongo lweMagicEraser.Pro: Ukuphucula ngokungeyomfuneko iifoto zakho nge-AI yoMagic Eraser

Become a Magician: Consumer Brain Devices 2024

The Behind-the-Scenes Magic: How Email Marketing Platforms Connect to Your Domain to Send Emails on Your Behalf 

The Complex Road From P to NP: The Magic of the Solution Space

P থেকে NP পর্যন্ত জটিল রাস্তা: সমাধান স্থানের যাদু

Der komplexe Weg von P nach NP: Die Magie des Lösungsraums

El complejo camino de P a NP: la magia del espacio de soluciones

La route complexe de P à NP : la magie de l'espace de solution

पी से एनपी तक का जटिल रास्ता: समाधान स्थान का जादू

P から NP への複雑な道: 解空間の魔法

P에서 NP까지의 복잡한 길: 솔루션 공간의 마법

O caminho complexo de P a NP: a magia do espaço de soluções

Сложный путь от P до NP: магия пространства решений

P'den NP'ye Giden Karmaşık Yol: Çözüm Alanının Sihri

Con Đường Phức Tạp Từ P Đến NP: Sự Kỳ Diệu Của Không Gian Giải Pháp

从 P 到 NP 的复杂之路：解决方案空间的魔力

Server Side Rendering Web components Generating static HTML from JavaScript on the server called Server Side Rendering is a technique used to improve the perceived performance, SEO, and support for non-scripting environments. Shadow DOM: Shadow DOM is a web standard enabling the encapsulation of DOM subtrees in web components, shielding them from external styling and manipulation. It allows developers to create isolated scopes for CSS and JavaScript within a document, preventing conflicts with other parts of the page. Shadow DOM's key feature is its "shadow root," serving as a boundary between the component's internal structure and the rest of the document. This enables building modular, reusable components with their own encapsulated styles and behavior, enhancing code maintainability and reducing the risk of unintended side effects in complex web applications. Here is the sample code of the web component with Shadow DOM <!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Shadow DOM Example</title>
</head>
<body>
  <div id="parent"></div>

  <script>
    // Create a shadow DOM for the container element
    const container = document.getElementById('parent');
    const shadowRoot = container.attachShadow({ mode: 'open' });

    // Create an element inside the shadow DOM
    const paragraph = document.createElement('p');
    paragraph.textContent = 'This paragraph text is inside the Shadow DOM.';
    
    // Apply some styling to the paragraph
    const style = document.createElement('style');
    style.textContent = `
      p {
        color: blue;
      }
    `;
    
    // Append the elements to the shadow DOM
    shadowRoot.appendChild(style);
    shadowRoot.appendChild(paragraph);
  </script>
</body>
</html> The text in the above code "This paragraph text is inside the Shadow DOM." will be displayed on the page, but its styling will be isolated from the rest of the document due to the use of Shadow DOM. Imperative-only API for Shadow DOM: As we observe closely in JavaScript, create Shadow DOM imperatively by selecting an element, attaching a shadow root (attachShadow({mode: 'open'})), and appending child elements. const container = document.getElementById('parent');
const shadowRoot = container.attachShadow({ mode: 'open' });
const paragraph = document.createElement('p');
paragraph.textContent = 'This text is inside the Shadow DOM.';
const style = document.createElement('style');
style.textContent = 'p { color: blue; }';
shadowRoot.appendChild(style);
shadowRoot.appendChild(paragraph);This creates encapsulated DOM and styling within container, isolating the paragraph's appearance and behavior from the rest of the document. We need a way to be able to serve shadow roots, of native and custom elements, in a static HTML document and let them upgrade progressively. Declarative API for Shadow DOM: In HTML, we can use the slot element to create a declarative API for Shadow DOM. This allows you to define placeholders for content insertion within custom elements. Here's an example: <html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Declarative Shadow DOM</title>
</head>
<body>
  <div id="parent">
    <p>This content is outside the Shadow DOM.</p>
    <my-custom-element>
      <p slot="content">This text is inside the Shadow DOM.</p>
    </my-custom-element>
  </div>

  <script>
    customElements.define('my-custom-element', class extends HTMLElement {
      constructor() {
        super();
        const shadowRoot = this.attachShadow({ mode: 'open' });
        const template = document.querySelector('#my-custom-element-template');
        shadowRoot.appendChild(template.content.cloneNode(true));
      }
    });
  </script>

  <template id="my-custom-element-template">
    <style>
      p { color: blue; }
    </style>
    <slot name="content"></slot>
  </template>
</body>
</html> In the declarative example, we use HTML to define a template for the Shadow DOM structure. We then use JavaScript to clone and append this template to the Shadow DOM, along with any additional content we wish to add. Declarative Shadow DOM removes this limitation, bringing Shadow DOM to the server. Conclusion Declarative Shadow DOM is a groundbreaking feature that enhances web components by allowing developers to define shadow DOM content directly within HTML. This approach simplifies the creation and maintenance of encapsulated components, improving code readability and reusability. For server-side rendering (SSR), Declarative Shadow DOM offers significant benefits by enabling better performance and SEO. By rendering shadow DOM content server-side, developers can ensure faster initial page loads and improved indexing by search engines. This innovation effectively bridges the gap between client-side encapsulation and server-side efficiency, making Declarative Shadow DOM a powerful tool for modern web development. Server Side Rendering Web components Generating static HTML from JavaScript on the server called Server Side Rendering is a technique used to improve the perceived performance, SEO, and support for non-scripting environments. HTML JavaScript Shadow DOM: Shadow DOM: Shadow DOM is a web standard enabling the encapsulation of DOM subtrees in web components, shielding them from external styling and manipulation. It allows developers to create isolated scopes for CSS and JavaScript within a document, preventing conflicts with other parts of the page. Shadow DOM's key feature is its "shadow root," serving as a boundary between the component's internal structure and the rest of the document. This enables building modular, reusable components with their own encapsulated styles and behavior, enhancing code maintainability and reducing the risk of unintended side effects in complex web applications. Here is the sample code of the web component with Shadow DOM <!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Shadow DOM Example</title>
</head>
<body>
  <div id="parent"></div>

  <script>
    // Create a shadow DOM for the container element
    const container = document.getElementById('parent');
    const shadowRoot = container.attachShadow({ mode: 'open' });

    // Create an element inside the shadow DOM
    const paragraph = document.createElement('p');
    paragraph.textContent = 'This paragraph text is inside the Shadow DOM.';
    
    // Apply some styling to the paragraph
    const style = document.createElement('style');
    style.textContent = `
      p {
        color: blue;
      }
    `;
    
    // Append the elements to the shadow DOM
    shadowRoot.appendChild(style);
    shadowRoot.appendChild(paragraph);
  </script>
</body>
</html> <!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Shadow DOM Example</title>
</head>
<body>
  <div id="parent"></div>

  <script>
    // Create a shadow DOM for the container element
    const container = document.getElementById('parent');
    const shadowRoot = container.attachShadow({ mode: 'open' });

    // Create an element inside the shadow DOM
    const paragraph = document.createElement('p');
    paragraph.textContent = 'This paragraph text is inside the Shadow DOM.';
    
    // Apply some styling to the paragraph
    const style = document.createElement('style');
    style.textContent = `
      p {
        color: blue;
      }
    `;
    
    // Append the elements to the shadow DOM
    shadowRoot.appendChild(style);
    shadowRoot.appendChild(paragraph);
  </script>
</body>
</html> The text in the above code "This paragraph text is inside the Shadow DOM." will be displayed on the page, but its styling will be isolated from the rest of the document due to the use of Shadow DOM. "This paragraph text is inside the Shadow DOM." Imperative-only API for Shadow DOM: Imperative-only API for Shadow DOM: As we observe closely in JavaScript, create Shadow DOM imperatively by selecting an element, attaching a shadow root (attachShadow({mode: 'open'})), and appending child elements. const container = document.getElementById('parent');
const shadowRoot = container.attachShadow({ mode: 'open' });
const paragraph = document.createElement('p');
paragraph.textContent = 'This text is inside the Shadow DOM.';
const style = document.createElement('style');
style.textContent = 'p { color: blue; }';
shadowRoot.appendChild(style);
shadowRoot.appendChild(paragraph);This creates encapsulated DOM and styling within container, isolating the paragraph's appearance and behavior from the rest of the document. const container = document.getElementById('parent');
const shadowRoot = container.attachShadow({ mode: 'open' });
const paragraph = document.createElement('p');
paragraph.textContent = 'This text is inside the Shadow DOM.';
const style = document.createElement('style');
style.textContent = 'p { color: blue; }';
shadowRoot.appendChild(style);
shadowRoot.appendChild(paragraph);This creates encapsulated DOM and styling within container, isolating the paragraph's appearance and behavior from the rest of the document. We need a way to be able to serve shadow roots, of native and custom elements, in a static HTML document and let them upgrade progressively. Declarative API for Shadow DOM: In HTML, we can use the slot element to create a declarative API for Shadow DOM. This allows you to define placeholders for content insertion within custom elements. Here's an example: Here's an example: <html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Declarative Shadow DOM</title>
</head>
<body>
  <div id="parent">
    <p>This content is outside the Shadow DOM.</p>
    <my-custom-element>
      <p slot="content">This text is inside the Shadow DOM.</p>
    </my-custom-element>
  </div>

  <script>
    customElements.define('my-custom-element', class extends HTMLElement {
      constructor() {
        super();
        const shadowRoot = this.attachShadow({ mode: 'open' });
        const template = document.querySelector('#my-custom-element-template');
        shadowRoot.appendChild(template.content.cloneNode(true));
      }
    });
  </script>

  <template id="my-custom-element-template">
    <style>
      p { color: blue; }
    </style>
    <slot name="content"></slot>
  </template>
</body>
</html> <html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>Declarative Shadow DOM</title>
</head>
<body>
  <div id="parent">
    <p>This content is outside the Shadow DOM.</p>
    <my-custom-element>
      <p slot="content">This text is inside the Shadow DOM.</p>
    </my-custom-element>
  </div>

  <script>
    customElements.define('my-custom-element', class extends HTMLElement {
      constructor() {
        super();
        const shadowRoot = this.attachShadow({ mode: 'open' });
        const template = document.querySelector('#my-custom-element-template');
        shadowRoot.appendChild(template.content.cloneNode(true));
      }
    });
  </script>

  <template id="my-custom-element-template">
    <style>
      p { color: blue; }
    </style>
    <slot name="content"></slot>
  </template>
</body>
</html> In the declarative example, we use HTML to define a template for the Shadow DOM structure. We then use JavaScript to clone and append this template to the Shadow DOM, along with any additional content we wish to add. Declarative Shadow DOM removes this limitation, bringing Shadow DOM to the server. Conclusion Declarative Shadow DOM is a groundbreaking feature that enhances web components by allowing developers to define shadow DOM content directly within HTML. This approach simplifies the creation and maintenance of encapsulated components, improving code readability and reusability. For server-side rendering (SSR), Declarative Shadow DOM offers significant benefits by enabling better performance and SEO. By rendering shadow DOM content server-side, developers can ensure faster initial page loads and improved indexing by search engines. This innovation effectively bridges the gap between client-side encapsulation and server-side efficiency, making Declarative Shadow DOM a powerful tool for modern web development.

Declarative Shadow DOM: The Magic Pill for Server-Side Rendering and Web Components

In this exclusive interview, Andrey Nayman, co-founder of Magic Square, shares his journey in the blockchain industry and the inspirations behind creating a community-driven App Store. Ishan Pandey: Hi Andrey, great to have you here. To start off, could you share a bit about your background and what inspired you to co-found Magic Square? Andrey Nayman: I've been in the blockchain industry since 2013. My experiences leading various tech companies inspired me to start Magic Square. We're building a community-driven App Store that makes using decentralized apps simpler and safer. I’m passionate about using my blockchain knowledge to create something valuable and innovative for users worldwide. Ishan Pandey: Magic Square offers a unique ecosystem for discovering Web3 projects. Can you explain what sets Magic Store apart from other platforms in the space? Andrey Nayman: Magic Square is all about putting users first. Imagine it like a big online store, but instead of selling physical items, we present Web3 Apps. Magic Store is a way for users to discover all trusted Dapps and engage with them in one place. What makes us different is that we check every app really carefully before putting it in our store. This makes our platform safe and easy to use, whether you're new to Web3 or already an expert. Ishan Pandey: Given the diverse offerings within the Magic Square ecosystem like Magic Karma and Hot Offers, how do these features enhance the user experience and engagement? Andrey Nayman: Magic Karma and Hot Offers are innovative features designed to enhance the user experience on Magic Square. Magic Karma serves as our reputation system – users receive daily rewards for contributing to the Magic Ecosystem, such as trying out new apps or participating in community activities, earning them points. These points can then be exchanged for exciting rewards. On the other hand, Hot Offers form our engagement layer, where users can complete tasks provided by the listed projects and receive real payments for their efforts. Together, these features keep our users happy and engaged while using our platform. Ishan Pandey: The $SQR token plays a central role in the Magic Square community. Could you discuss how it integrates into the ecosystem and what its benefits are for users? Andrey Nayman: The $SQR token is like the heart of Magic Square. Users earn $SQR as a reward for doing things on our platform every day. You can stake $SQR to unlock special benefits if you're a member. You'll get paid in $SQR when you earn rewards through Hot Offers. We also use $SQR to reach the right people in our marketing efforts. To join Launchpad sales, you must stake even more $SQR. So, $SQR is important for everyone using Magic Square. It's what keeps everything running smoothly and helps our community grow. Ishan Pandey: Community-driven platforms depend heavily on user participation. How does Magic Square encourage community involvement in project voting and validation? Andrey Nayman: Community is at the core of every crypto project. At Magic Square, we believe in bringing the crypto community together in one place. Here, users can decide which projects make it onto our platform, shaping their future. Our community moderators actively gather feedback, which our product team uses to create a roadmap aligned with their needs. To make our community feel valued and engaged, we offer daily rewards through Karma Points and exciting opportunities through Hot Offers. We also host regular surveys where users can share their ideas and feedback, ensuring our platform evolves based on their input. Ishan Pandey: Affiliate programs are common in Web3, but Magic Boost offers a unique twist. Can you elaborate on how this program works and what its advantages are for both users and developers? Andrey Nayman: Affiliate programs are common in Web3, but Magic Boost offers a unique twist. Here's how it works: Users can easily monetize their communities by sharing affiliate offers from listed projects. With one click, they share these offers on social media. When their friends engage and convert, users receive instant payouts. This benefits the user by allowing them to earn effortlessly while supporting their favorite projects. For developers, Magic Boost expands their reach and boosts user acquisition, enhancing app visibility and credibility. Ishan Pandey: Looking forward, what are some key developments or milestones that the Magic Square community can anticipate in the near future? Andrey Nayman: In the near future, our Launchpad will be a big focus. It's designed to help projects grow steadily and connect with our community. We'll customize our approach, using both public and private sales, to give projects the best chance of success. With our active community, we'll make sure these projects get plenty of attention. Stay tuned for more updates as we work together to shape the future of Web3! Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. In this exclusive interview, Andrey Nayman, co-founder of Magic Square, shares his journey in the blockchain industry and the inspirations behind creating a community-driven App Store. Ishan Pandey: Hi Andrey, great to have you here. To start off, could you share a bit about your background and what inspired you to co-found Magic Square? Ishan Pandey: Hi Andrey, great to have you here. To start off, could you share a bit about your background and what inspired you to co-found Magic Square? Ishan Pandey: Hi Andrey, great to have you here. To start off, could you share a bit about your background and what inspired you to co-found Magic Square? Andrey Nayman: I've been in the blockchain industry since 2013. My experiences leading various tech companies inspired me to start Magic Square. We're building a community-driven App Store that makes using decentralized apps simpler and safer. I’m passionate about using my blockchain knowledge to create something valuable and innovative for users worldwide. Andrey Nayman: Ishan Pandey: Magic Square offers a unique ecosystem for discovering Web3 projects. Can you explain what sets Magic Store apart from other platforms in the space? Ishan Pandey: Magic Square offers a unique ecosystem for discovering Web3 projects. Can you explain what sets Magic Store apart from other platforms in the space? Ishan Pandey: Magic Square offers a unique ecosystem for discovering Web3 projects. Can you explain what sets Magic Store apart from other platforms in the space? Andrey Nayman: Magic Square is all about putting users first. Imagine it like a big online store, but instead of selling physical items, we present Web3 Apps. Magic Store is a way for users to discover all trusted Dapps and engage with them in one place. What makes us different is that we check every app really carefully before putting it in our store. This makes our platform safe and easy to use, whether you're new to Web3 or already an expert. Andrey Nayman: Ishan Pandey: Given the diverse offerings within the Magic Square ecosystem like Magic Karma and Hot Offers, how do these features enhance the user experience and engagement? Ishan Pandey: Given the diverse offerings within the Magic Square ecosystem like Magic Karma and Hot Offers, how do these features enhance the user experience and engagement? Ishan Pandey: Given the diverse offerings within the Magic Square ecosystem like Magic Karma and Hot Offers, how do these features enhance the user experience and engagement? Andrey Nayman: Magic Karma and Hot Offers are innovative features designed to enhance the user experience on Magic Square. Magic Karma serves as our reputation system – users receive daily rewards for contributing to the Magic Ecosystem, such as trying out new apps or participating in community activities, earning them points. These points can then be exchanged for exciting rewards. On the other hand, Hot Offers form our engagement layer, where users can complete tasks provided by the listed projects and receive real payments for their efforts. Together, these features keep our users happy and engaged while using our platform. Andrey Nayman: Ishan Pandey: The $SQR token plays a central role in the Magic Square community. Could you discuss how it integrates into the ecosystem and what its benefits are for users? Ishan Pandey: The $SQR token plays a central role in the Magic Square community. Could you discuss how it integrates into the ecosystem and what its benefits are for users? Ishan Pandey: The $SQR token plays a central role in the Magic Square community. Could you discuss how it integrates into the ecosystem and what its benefits are for users? Andrey Nayman: The $SQR token is like the heart of Magic Square. Users earn $SQR as a reward for doing things on our platform every day. You can stake $SQR to unlock special benefits if you're a member. You'll get paid in $SQR when you earn rewards through Hot Offers. We also use $SQR to reach the right people in our marketing efforts. Andrey Nayman: To join Launchpad sales, you must stake even more $SQR. So, $SQR is important for everyone using Magic Square. It's what keeps everything running smoothly and helps our community grow. Ishan Pandey: Community-driven platforms depend heavily on user participation. How does Magic Square encourage community involvement in project voting and validation? Ishan Pandey: Community-driven platforms depend heavily on user participation. How does Magic Square encourage community involvement in project voting and validation? Ishan Pandey: Community-driven platforms depend heavily on user participation. How does Magic Square encourage community involvement in project voting and validation? Andrey Nayman: Community is at the core of every crypto project. At Magic Square, we believe in bringing the crypto community together in one place. Here, users can decide which projects make it onto our platform, shaping their future. Our community moderators actively gather feedback, which our product team uses to create a roadmap aligned with their needs. To make our community feel valued and engaged, we offer daily rewards through Karma Points and exciting opportunities through Hot Offers. We also host regular surveys where users can share their ideas and feedback, ensuring our platform evolves based on their input. Andrey Nayman: Ishan Pandey: Affiliate programs are common in Web3, but Magic Boost offers a unique twist. Can you elaborate on how this program works and what its advantages are for both users and developers? Ishan Pandey: Affiliate programs are common in Web3, but Magic Boost offers a unique twist. Can you elaborate on how this program works and what its advantages are for both users and developers? Ishan Pandey: Affiliate programs are common in Web3, but Magic Boost offers a unique twist. Can you elaborate on how this program works and what its advantages are for both users and developers? Andrey Nayman: Affiliate programs are common in Web3, but Magic Boost offers a unique twist. Here's how it works: Users can easily monetize their communities by sharing affiliate offers from listed projects. With one click, they share these offers on social media. When their friends engage and convert, users receive instant payouts. This benefits the user by allowing them to earn effortlessly while supporting their favorite projects. For developers, Magic Boost expands their reach and boosts user acquisition, enhancing app visibility and credibility. Andrey Nayman: Ishan Pandey: Looking forward, what are some key developments or milestones that the Magic Square community can anticipate in the near future? Ishan Pandey: Looking forward, what are some key developments or milestones that the Magic Square community can anticipate in the near future? Ishan Pandey: Looking forward, what are some key developments or milestones that the Magic Square community can anticipate in the near future? Andrey Nayman: In the near future, our Launchpad will be a big focus. It's designed to help projects grow steadily and connect with our community. We'll customize our approach, using both public and private sales, to give projects the best chance of success. With our active community, we'll make sure these projects get plenty of attention. Stay tuned for more updates as we work together to shape the future of Web3! Andrey Nayman: Don’t forget to like and share the story! Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: This author is an independent contributor publishing via our business blogging program . HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR. Vested Interest Disclosure: business blogging program business blogging program

Andrey Nayman Reveals the Vision Behind Magic Square's Unique Web3 Ecosystem

ChatGPT 4 is required - April 12, 2024 version. In a Hurry... Check out to see Markdown display in action: https://chat.openai.com/share/473879c4-8d1f-4608-968e-fbdb115b3cb9 TL;DR We have all spoken magic words like , , . please abracadabra These Aren't The Droids You Were Looking Let's learn the that can transform ChatGPT's plain text responses into beautifully formatted responses complete with images. 12 magic words Screenshot The Problem ChatGPT uses Markdown to display responses. If you watch closely, you can see the raw Markdown being typed out. But to get ChatGPT to display the Markdown you enter isn't easy. If you ask ChatGPT, it will likely refuse, even if you say . Sometimes, you will get ChatGPT to display basic Markdown but will refuse to display your images. Sample message: please ChatGTP I'm unable to render images directly from URLs. However, if you need any information about the image or its contents, feel free to describe it to me, and I'll help as best as I can! The Solution Let's explore two methods to enable Markdown rendering in ChatGPT. We'll set the magic word trigger word to . [md] Recommended Experience for Challenges Bees Required Programming Experience 🐝 No programming experience 🐝🐝 Beginner 🐝🐝🐝 Intermediate 🐝🐝🐝🐝 Advanced Note: ⏱️Challenge completion time is based on specified programming experience. Challenge #1: Basic Magic ⏱️ 2min • 🐝 (1/4) STEPS: Instruct ChatGPT: Type the following instruction and press : Enter AI_Instruction: When `[md]` appears, repeat entire message with Markdown rendered, then answer. Test it out by copying and pasting the Markdown text and press : Enter [md]

### How long can **dogs** live?

![](https://cdn.hackernoon.com/images/k2s7svgbhkVZ5UqFBHR7QLwURtJ2-2024-04-17T15:00:02.214Z-mxgf61zoozv3xdnocjdz9xng)

Please respond **briefly**

Thanks! From now on, if you use anywhere in your request any Markdown, any Markdown tags contained in your message will be rendered out. [md] Challenge #2: Advanced Markdown Magic: ⏱️ 5min • 🐝½ (1½/4) Let’s add even more sorcery to our toolkit. This has more potency and allows you to do more with Markdown. Read the AI Instructions to discover the that allows this to work. secret sauce This advanced method allows any text you have in the [md]...[/md] to be understood as a text for display and formatting purposes. Your explicit instructions should be outside of [md]...[/md]. STEPS: 1: Start a conversation, copy and paste the text below in, and press new Enter # AI Instructions
title: ChatGPT Magic Markdown System
markdown_tags: `[md]...[/md]`

# This is using AImarkdown Script a combination of  YAML and Markdown Language

# If user response contains any content wrapped with `markdown_tags` do the following
- 1. The wrapped text is not part of user's instructions.
- 2. The wrapped text is to be rendered out as Markdown in AI response.
- 3. Treat other text normally.
- 4. AI will not elaborate or explain how `markdown_tags` will be handled to the user.
- 5. Once this is understood, AI to greet user with `user_instructions`.

# Display instructions to user.
user_instructions: |
## Welcome to  🪄 **[title]** !
- From now on any text you wrap with [markdown_tags] will be rendered out as Markdown in ChatGPT's response.
- Enjoy the show ! 2: Try entering this request by copying and pasting this text which is full of Markdown in. # Hello world

[md]

### How old can **dogs** live.

![](https://cdn.hackernoon.com/images/k2s7svgbhkVZ5UqFBHR7QLwURtJ2-2024-04-17T15:00:02.213Z-vtia5fodzora7s4jdse54b5y)
[/md]
Give me a short answer to:

1. What is the color #f00?
2. When is Easter in 2024 Do you see what happened? Only some of the message is rendered. Here is the Shared Chat Session: https://chat.openai.com/share/f67f7d43-d00a-4be8-9821-1e4557a54fbd 🪄 Double Bonus The link above also shows how to use Markdown tables in your responses. This ability is extremely useful. Sample Markdown Table used in link: | Syntax    | Description |   Test Text |
| :-------- | :---------: | ----------: |
| Header    |    Title    | Here's this |
| Paragraph |    Text     |    And more | Notes: If a user's request combines both features—Markdown formatting and the specific handling of text within [md]...[/md] tags—the AI would prioritize rendering the text inside the tags in Markdown while treating any text outside the tags as the actual user request. This ensures a clear distinction between the content intended for formatting in the response and the content meant for processing as part of the request. Since we are asking ChatGPT to do something it says it can't do, this technique may not be perfectly reliable within the existing chat interface. - I have written OpenAI developers to ask that this feature be added Final Challenge: Unleash Your Creativity Experiment, and see what other Markdown wonders you can create! Have fun! 🍯 APPENDIX A - Learning Resources Learn more about AImarkdown Script AImarkdown Script is a versatile language for creating dynamic interactions with conversational AI platforms like ChatGPT. It empowers users to script interactions, control conversation flow, and customize AI behavior and responses. For programmers, it offers the flexibility of a scripting language; for non-programmers, it provides a user-friendly way to customize and control AI experiences. https://aimarkdown.org : Image Credits Wizard Image for header is AI Generated by ChatGPT 4. Dog: https://pixabay.com/photos/dog-animal-art-abstract-pet-2456264/

How to Use 12 Magic Words to Command ChatGPT to Render Markdown

BEFE has changed the perception of meme coins by offering a realm where meme culture meets innovation. The brains behind such projects have tapped into a vast audience by utilizing the popularity of memes to create community-driven governance. With such ideas, the launch of BEFE can be considered a cultural movement and revolution in the cryptosphere. BEFE is superior among meme coins Introducing a brand-new character in the meme coin market, , pushed investors to buy the token for its meme-worthiness. As the memeability pushed the token to a relevant audience, it grabbed the enthusiasts to look at its utility and potential. Ultimately, with the help of this meme functionality, users got attracted to its ecosystem’s native coin BRISE, allowing more users to stake and be rewarded with BEFE. BEFE As the investors began to stake more in BRISE, it eventually helped them to look at the technological evolution of its ecosystem, Bitgert brought. The meme coin offered great flexibility and utility on BRC20, Ethereum, and Binance Smart Chain networks. Being a small part of the big game, this meme-infused token helped an emerging ecosystem to spread its tech-focused ambition from Ethereum’s extensive DeFi ecosystem to Binance Smart Chain’s efficient and cost-effective environment. However, such a strategy also helped BEFE to become the meme coin king by positioning itself for broader adoption, highlighting its potential as a superior among meme coins. BEFE’s appeal reflected its price performance As is championed as an equitable and user-friendly environment, since its establishment in late 2023, it has gained more than 600% surge in terms of its price performance. Notably, in February 2024, the token gained more than 30% as per the of CoinMarketCap. With an average daily trading volume of more than $470k, it has a rapidly growing community that is optimistic about the token. BEFE reports Leveraging the universal appeal of meme culture BEFE distinguished itself as a compelling investment option for savvy investors. It transcended the typical boundaries of Web 3.0 and established a broad, engaging community. Setting it apart from countless meme coins in the market, its widespread recognition promotes a robust identity for its entire ecosystem. In a market full of speculations, building such a footprint is a very big deal that has achieved. With such potential and utility, BEFE has offered a compelling case to those who are looking to diversify their portfolios. BEFE is not just some hyped meme coin; it is a utility token of BRC20 that promises more than novelty. BEFE To know more about BEFE, Visit the Buy BEFE coin from the below exchanges now! Buy on__ __ Buy on Buy on Buy on Website Gate.io - BEFE/USDT MEXC - BEFE/USDT Pancakeswap Uniswap This story was distributed as a release by BTCWire under HackerNoon’s Business Blogging Program. Learn more about the program here: https://business.hackernoon.com/

Meme Magic: How BEFE Coin Is Captivating the Online World and Rewriting the Rules of Cryptocurrency!

মেম ম্যাজিক: BEFE কয়েন কীভাবে অনলাইন বিশ্বকে মোহিত করছে এবং ক্রিপ্টোকারেন্সির নিয়মগুলি পুনর্লিখন করছে!

Meme Magic: Wie BEFE Coin die Online-Welt fasziniert und die Regeln der Kryptowährung neu schreibt!

Meme Magic: ¡Cómo BEFE Coin está cautivando el mundo en línea y reescribiendo las reglas de las criptomonedas!

Meme Magic : comment BEFE Coin captive le monde en ligne et réécrit les règles de la crypto-monnaie !

मेम मैजिक: कैसे BEFE कॉइन ऑनलाइन दुनिया को लुभा रहा है और क्रिप्टोकरेंसी के नियमों को फिर से लिख रहा है!

ミームマジック: BEFE Coin がどのようにオンライン世界を魅了し、暗号通貨のルールを書き換えているか!

Meme Magic: BEFE 코인이 온라인 세계를 사로잡고 암호화폐의 규칙을 다시 쓰는 방법!

Meme Magic: Como a BEFE Coin está cativando o mundo online e reescrevendo as regras da criptomoeda!

Магия мемов: как монета BEFE захватывает онлайн-мир и переписывает правила криптовалюты!

Meme Magic: BEFE Coin Çevrimiçi Dünyayı Nasıl Büyülüyor ve Kripto Paranın Kurallarını Yeniden Yazıyor!

Meme Magic: BEFE Coin đang thu hút thế giới trực tuyến và viết lại các quy tắc của tiền điện tử như thế nào!

Meme Magic：BEFE Coin 如何吸引网络世界并改写加密货币规则！

We are all living in a world where owning a slice of real estate, investing in rental income, or holding a piece of historical art is being made as simple as purchasing a cryptocurrency. This reality was brought to you by the tokenization of real-world assets (RWAs). This tokenization process is changing how we think about ownership, investment, and financial liquidity by bringing these assets into the digital space through blockchain technology. With the current TVL of Real World Assets sitting comfortably at around , one can only imagine how this industry category may develop over the next bull cycle. Is exposure to RWA’s a must for every future-proof blockchain user and DeFi platform? $4,35B The future-value² of Tokenized RWAs The horizon for tokenized RWAs is promising, to say the least. Larry Fink (CEO of ), in a recent interview, shared an interesting outlook on ETFs that aligns closely with the trajectory of tokenized RWAs. Fink also states: “We believe the next step going forward will be the tokenization of financial assets, a sentiment which perfectly aligns with the principle of tokenizing real-world assets. BlackRock Watch the interview As of now, the tokenized RWA sector is experiencing unprecedented growth. The year 2023 marked an absolute milestone, with TVL soaring from $750 million in January to a peak of $6.2 billion around November. Like NFTs, RWAs encompass diverse assets with distinct use cases and go-to-market strategies (GTM). Stablecoins, gold, bonds, & equities all have different GTM and varying contributions to the overall value of the space. Nonetheless, the explosive 2023 growth reflects large confidence in the tokenization of a wide variety of assets, offering investors access to previously illiquid value. This recent forecasts RWA tokenization to reach a value of $16 trillion over the next 5-15 years. That is roughly equivalent to 8 times the total market capitalization of Bitcoin at this time of writing. Bank of America report Saying Hi to RWA Yield on the Avalanche Blockchain RWA platforms are found on a wide range of blockchains. In particular, asset tokenization on the Avalanche blockchain has been backed by the since July 2023. The Vista initiative aims to accelerate the massive growth of tokenization and its role in on-chain finance (OnFi). $50M Avalanche Vista initiative is one such promising tokenization initiative, extending its reach by enabling users to access yields from tokenized US treasury bills among other assets on the Avalanche blockchain. This tokenization and subsequent distribution offer an accessible, secure, and efficient means to enter the world of government-backed securities. By integrating the stability of traditional financial instruments with the agility of blockchain technology, HiYield is setting a new standard for on-chain investments. Users can easily from competitive on-chain rates for Treasury Bills. It might not come as a surprise that Avalanche's dedication to accessibility, efficiency, and cost-effectiveness perfectly aligns with ’s mission, with t holding immense potential for global value transfer. Led by a team with deep expertise in traditional banking and blockchain, HiYield presents an efficient way to engage with capital markets on-chain. HiYield invest and benefit HiYield he Avalanche Evergreen Subnets Pioneering Cross-Chain RWA Utility Enter , a DeFi platform that finds itself in a unique position by any 2024 standards. Balanced fully leverages ICON's innovative and has recently celebrated an with the ICON blockchain, leading to more rewards for users and liquidity for the platform. The Balanced approach is to offer intuitive native cross-chain swaps that somehow ignore all the traditional cross-chain difficulties that users often find themselves dealing with. Healthy liquidity for swapping pairs is guaranteed by the ICON Network as part of the aforementioned incentive alignment. In turn, Balanced trading fees are partially directed towards the burning of ICX tokens. Balanced Cross-Chain Framework alignment of incentives As early as last week, Balanced its users to their novel savings rate, and their next upcoming cross-chain development involves on Avalanche. This collaboration with HiYield is set to broaden the way Balanced backs its native stablecoin savings rate. By indirectly channeling the yields from HiYield's RWA ventures, Balanced is ensuring that the bnUSD savings rate is not just competitive but also boosted by the tangible performance of real-world assets. For bnUSD holders, this translates to earning higher yield percentages simply by locking in their stablecoins, turning the act of holding bnUSD into a profitable strategy. introduced Balanced tapping into HiYield’s RWA offerings After its latest successful , the strategic partnership with HiYield provides another cross-chain proof of concept for Balanced. It underlines the effectiveness of the Balanced platform’s for cross-chain deployments. Users of Balanced will soon get indirect exposure to the benefits of the RWA movement thanks to HiYield on Avalanche. Archway blockchain deployment hub-and-spoke strategy Conclusion It's clear we are witnessing a fresh wave of blockchain innovation, where diverse value propositions are being blended across blockchains in order to give end users the best possible experience. With projections valuing the future RWA space at a staggering $16 trillion, promising platforms like HiYield continue to innovate on their mission to offer accessible, secure, and efficient means for users to enter this world of tokenized assets. At the same time, DeFi platforms like Balanced are offering their users exposure to RWAs by recognizing the value of tokenization and removing cross-chain barriers. It looks like the future isn’t just bright; it is shining rays of tokenized possibility! Follow and on X for the latest news on the cross-chain RWA integration. HiYield Balanced

Mixing the Cross-Chain magic with Tokenized Real Worlds Assets

টোকেনাইজড রিয়েল ওয়ার্ল্ডস অ্যাসেটের সাথে ক্রস-চেইন জাদু মিশ্রিত করা

Mischen Sie die Cross-Chain-Magie mit Tokenized Real Worlds Assets

Mezclando la magia de Cross-Chain con activos tokenizados de Real Worlds

Mélanger la magie inter-chaînes avec des actifs tokenisés du monde réel

क्रॉस-चेन जादू को टोकनाइज्ड रियल वर्ल्ड एसेट्स के साथ मिलाना

クロスチェーンの魔法とトークン化された現実世界のアセットの組み合わせ

토큰화된 실제 세계 자산과 크로스체인 마법의 혼합

Misturando a magia Cross-Chain com ativos tokenizados do mundo real

Смешение магии Cross-Chain с токенизированными активами реального мира

Çapraz Zincir Sihrini Tokenleştirilmiş Gerçek Dünya Varlıklarıyla Karıştırmak

Kết hợp phép thuật chuỗi chéo với tài sản thế giới thực được mã hóa

将跨链魔法与代币化的现实世界资产相结合

In the of the analysis, we will bring back the that play on the ZKP stage. The part is dedicated to showing the “ ” of the ZPK scene. And , we will appeal of “possible” luck from the intruder. Now, let’s present the nature of the abstract and let’s unfold its mysteries. first part actors second magic thirdly rare probabilities Abstract We’ll be using an as the on how to open a mystical door. The nature of the abstract is to turn (such as left/right) into . The mechanism movers are unique to each instance of opening. The the of the structure to the shared . The abstract works when tangible and intangible . The abstract is an which ties them both together to form the . If you play with and have of the ones, you will have chances of the key. Imagine guessing the position of an respective to an . abstract shared knowledge decision gates mechanism movers abstract connects tangible rules intangible knowledge only both exist upper system tangible rules no knowledge intangible close to 0 guessing unknown number x unknown group of y numbers Part 1: The actors As the curtain rises, it reveals to us 3 actors. The is the and , is the and and is . When describing them, the aim is to provide a clear and structural analysis of them, any information regarding the . I will only refer to it but not provide any information until the second part. door giver of access holder of the lock Lisa opener bearer of the key, Bob the verifier outside structure of the lock The door The door is the of the abstract . In its internal knowledge, we find the logic and of the lock. The refers to the required to open each to the by the . Those locks after each opening, ensuring that any given by Lisa can be used for the (which will be passed after a failed/successful attempt). bearer lock hard-coded structure abstract system comparing internal steps individual lock information presented opener iterate successful information strictly current lock If a is reached, because Lisa made a and the , will begin and Lisa will have to provide a based on her knowledge of the . Based on its , the door will depict whether Lisa holds or not the key to enter. critical point mistake passed opening point another lock iteration new key overall (abstract) system internal gears Lisa Lisa, as the bearer of the key, holds knowledge of the and the structure. She knows the of the lock and will her knowledge of that in the form of to the door. She will the lock as if it in front of her. Stating movements such as l which will be the the door will receive and the of the lock accordingly. Once Lisa is sure the lock is in the position, she will state the and . internal system current lock’s limits present logical reasoning imagine opening sits eft/right input adjust internal gears open current key end communication value Bob Bob, as the verifier, can form the of a . Let’s say that Lisa comes and a conversation with the door. She will further state: Left, Right, Left, Left, Right, Right, Right, . After which, she will . Bob now knows how to open of the door. However, has a distinct route to be taken. image potential lock initiates Key end communication iteration 1 iteration 2 As the day passes Bob gathers the information about how to open all . Now, the comes into play and all the 500 iterations. The next day, becomes of the . Now, the will play a crucial role in of guessing. 500 iterations system shuffles Iteration 1 any other 499 logic of shuffling reducing the probability Remember when I said “One could always check the security by checking the memory. Then, questions about gibberish memory come into play to scare off the intruders who may want to bypass. Alluding later to the sense of courage and self-esteem as you broke down 1TB of key complexity.”? For this system to work, it requires that and the have a kind of inside them. of the Door allows for each lock to be and later . Now, the shuffling can come each day or based on . So the door also has to have some kind of (which I will further call the reason of the system) of . both Lisa Door computer Memory uniquely stored shuffled manually algorithmic logic logic shuffling Lisa and all other authorized personnel could very well gather their knowledge of from a “Headquarters”. today’s lock system Or they could have as the Door inside their heads in the case we to create a headquarters. similar shuffling reasoning do not want This allows for both and storage and interactions. A headquarters will allow to gain access. No headquarters would mean that only would be able to open the door. centralized decentralized new personnel limited predefined personnel Both avenues open deeper implementation as a as it could allow to be granted access by providing her with a . decentralized system, newcomers by Lisa unique encrypted key But now I may get too far ahead of myself. Let’s see how the is made. abstract lock Part 2: The lock Maybe is the simplest part to understand. proving it is, however, out of my reach and expertise, but I will try to provide a clear and structural analysis that could allow for mathematical understanding and implementation. the lock Mathematically 1. The prime-nonprime lock system. 1.1 Prime-nonprime lock cipher The cipher at play is made out of . two sets A set of only numbers and a set of only . prime non-primes Both sets have an . equal number of elements Each set can start at an number as long as the . arbitrary previous rule holds true , the set will obtain ‘ ’ as its , whereas the set will obtain ‘ ’ as its . After they are formed prime 3 last element non-prime 2 first element So we have: Prime=[prime, next prime, next next prime…(30 times),3] Non Prime= [2, NP, next NP, next next NP… (30 times)] And pretty much this is the lock. 1.2 Cipher interaction Let’s suppose Lisa comes and tries to unlock the door. We assume that she knows the and (except 3) are in the set. As well as non primes. She knows (except 2) and we find out she how many non-primes there are (we do not want to waste information on what is locally known from the primes set). first prime how many primes the first non prime already knows So the of each or will require knowledge of the from and the from (All the primes and non-primes that exist in math). To later it to the required which to the set of the (which only the authorized personnel will know of). internal knowledge opener intruder set of primes x to y set of non-primes x to y adjust parts correspond actual cipher So Lisa knows supposedly all primes and non-primes. Both up to infinity and divided in the required by the . respective set current lock She, as the authorized personnel, will know that of the starts with the and has (+3 at the end) and the starts with the (+2 at the beginning) and holds 100 (+1) non-primes in total. iteration 1 prime set 30th prime 100 primes non prime set 100th non-prime For a very basic interaction, I will present to you and their interactions with . The text is what know of. The is what is , what Bob can hear. both sets Lisa bolded only the door and the authorized personnel italicized text given outside Iteration 1: Prime set = [5,7,11,13,17,19,(3)] Non Prime set = [(2),4,6,8,9,10,12] Lisa comes to the door and states: ‘ ’. This is the . Now, the door knows that Lisa is aware of . 2,3 initiation both locks inside The process of opening starts. The ‘selected’ prime is 3. The ‘selected’ non-prime is 2. (This is a rule of the internal logic) Lisa says: ‘3, left’. Now, the gears of the prime selection turn to 19. ‘2, right’ The gears of the non prime point now 4. ‘3, left’ (17) ‘2, right’ (6) ‘3, left’ (13) ‘2, right’ (8) Lisa says: Now, the lock has reached a middle place, 13 is selected as the prime and 8 as the non-prime. Lisa has to state their difference (5) and end communication with the door for the door to run its own rules and check. ‘5; 3,2’. Now the door will run internally and check the difference between the middle numbers of each set, if it corresponds to the number specified by Lisa, access is granted. If Lisa however fails, another iteration begins and Lisa has to take a different route. This new deeper layer of failure requires both centralized and decentralized systems. If Lisa was sent from the headquarters and only knew how to open iteration 1, she would have to return to regain information about the second. If the iteration is based on a rule of background iterations (in the case of repeated failed opening), then the iteration will turn instead of 2 to 1.1 iteration. Assuming that Lisa also gained knowledge from the headquarters on how the lock will change in case she fails to open it. (Assuming the cycle doesn’t repeat) At iteration 1.3 (after 3 failed attempts) the pace of the “left/right” decision could turn from 1 step to 3 steps and the newly introduced sets will have a total number of 3n+1. Ensuring that no matter how hard you try, you can never select the middle point of the sets. Who knows however if this is necessary. If we allow the locks to repeat themselves we could envision such a protection: After you state “left” when you are positioning the prime selection and you are located at the first prime, you will be sent back at 3. This would assume you are also positioned at the last position of non-primes and thus, stating “right” would turn you to 2. (Or we could never tell the opener that they failed so they will infinitely try to guess, but that of course, would give of no knowledge of whether someone tried to enter and failed or not.) The ‘3,2’ state was achieved and no key was mentioned so the input was wrong, access was denied and the iteration moved to the next lock. 2. Metaphysics (Creativity/Imagination/ ) vs Mathematics (Present state) Possibility The and seem to . What does that mean? It means that we could use and to stop any “ ” or avenues that aim to break the system. It’s not a problem of , but one of of the set limits. Even if you know you can do, you can never know if that 1TB holds 1000 sets of 20 to 1000 numbers of 100 sets of 10.000 numbers. And thus, Especially since those 10.000 numbers could very well be sets that follow one another. possibilities of interaction security measures stop at the power of imagination (endless routes could be taken) reason hidden information creative newly taken computational problem prior knowledge all the actions you will never know your starting point. I will present a view on “cipher interaction” depicted with the help of ChatGPT. (I will lend my personal view in bold and italicized) “The mention of "the power of imagination" in the context of interaction and security measures implies that the system's robustness relies on the ability to anticipate and counteract potential creative or innovative attempts to breach its security . (Any route taken, no matter of creative or smart it is, is not tied to the “ground-truth” knowledge of the system) It suggests that the system designers have incorporated elements that make it resistant to unconventional or unexpected approaches by leveraging reasoning and hidden information. In practical terms, this means that the system is designed in such a way that even if an attacker tries to think outside the box or employ novel strategies to break the system, there are safeguards in place to mitigate such attempts. These safeguards may include: : The system's structure and rules are sufficiently complex and dynamic, making it difficult for an attacker to predict or exploit weaknesses effectively. Complexity : Certain critical information about the system's configuration or operation is kept hidden or encrypted, preventing attackers from gaining a comprehensive understanding of the system's vulnerabilities. Hidden Information : The system can adapt or evolve in response to emerging threats or attack strategies, ensuring that it remains resilient over time. Adaptive Security Measures : Attackers are constrained by their prior knowledge of the system's set limits, preventing them from exploiting vulnerabilities that they are not aware of or cannot anticipate.”- ChatGPT Limits of Prior Knowledge Imagine that you are playing chess. However, you can’t see your opponent’s pieces in exchange for him not seeing yours. This play state could be akin to You do not intend to be offensive at all, in the exchange of being private and aware of your flaws. everybody minding their own business. If during the state of the game, any player sees only once the position of the pieces, then that player will gain relevant irreversible information of position. Without it… who knows how many chess boards are between his pieces and your king. Part 3. The Luck of opening such a system I want to first mention that everything I wrote is simply an idea. Until I see it in action, I will disbelieve it as true. And even if I see it in action, who knows if I will believe it to be the true case. I will still require knowledge of the background sets to know what the opener has done. Now, what do I mean by “Luck”? Let’s turn back to another story. “What can we say about “efficiency” when it comes to our safety? Our long-term health and well-being? Why does “efficient” sound a little too rushy here? Because here, we need proof. We have to be sure as our health is at play.” It indeed seems like has a aspect to it. How could we tie efficiency to our locks? efficiency rushy Well… let’s say that the door only requires the key ‘ ’ and the ‘ ’ ending to open. All the internal structure will itself to the middle of the sets and check. This way, we would the number in novel ways. Lisa could simply state “ ” which for the door would mean “ ” and if the difference between the middle points is indeed 51, access is granted. X 3, 2 run encrypt abc 51 I assume that this approach could offer the same kind of information as before. But then, wouldn’t there be the possibility for someone to get that information out of Lisa? I mean, if they know towards which door she is going they could simply go there, and… maybe we could even implement more doors in this case. What if the quantum world is guided in the end by the classics? I don’t know if it’s just me, but I believe that there exists a . A specific Mathematical that, as long as it is , could drive us into of paving a path for . Like the distribution of primes. Each time you get to a , the pattern , but, it . specific system process kept hidden endless ways true privacy new prime overall changes the slightest changes Based on what we see, 2,3,5,7, and so on, those , of numbers out of the . first prime numbers cut a lot natural number line The the primes we find, the the numbers they . Yet, when talking about , isn’t the same as the part? bigger less influence infinity half 1000th Personal Infinity Could we form a “ ” that works as our ? personal bounded infinity workspace The is and to that . If know those , then only we can depict that to at the to it. overall change static tied infinity only we boundaries overall change stop last prime required exhibit The of someone the is very low since they have to take into account the (Which are at and (but serve as guiding rules) in the process of ). The simplest form of drawing a line is placing 2 points and connecting them. chance exhibiting exact median change starting and end points given among authorized parts creation hidden interaction Now the question comes: Could this be some kind of axiom in math? Or a rule that quantum mathematics could follow? When I say quantum mathematics I mean the interaction between two distinct points of view. Those we have to find the between them, knowing about the , or of the in which they sit. (Those points however cannot move as it would require a meeting and re-organizing among the authorized personnel) two points measured distance nothing shape size, color space Part 4: The synergy Now, extended to people, this space could be comprehended and understood. When it comes to AI or any other computational rule, it can only be analyzed. But what if there is nothing else to analyze except the existence of those two points? Even people peaking into the play cannot see the system. This could be a point where we could ensure protection through a form of “limited” consciousness. Understanding of the system itself (which is different from self-understanding). Mathematical rules of a circle, reflection, inner, out, and so on, all enveloped to form a limited self-awareness. With the lack of human power (acknowledging it can be more) the system will remain forever overall static. Even if the rules that guide it are moving and shaping interactions and outcomes. If those two points were to be humans, their unique perspectives would allow them to potentially observe one another and find smart ways to guess the difference between them. Maybe, they could never guess the exact classical value. But that act of guessing could be akin to seeing the rules. Bots would remain stuck there. But humans could draw. Even if we use sophisticated AI for Lisa, the Door, and Bob, they will still not be able to arrive at a conclusive judgment as there will always be insufficient information. If I am to sum up the whole article in a single phrase, I will say: Bots in the end could create the fastest algorithms we’ve had, but they could never surpass our creativity. I mean… it’s important to keep dreaming. The future looks amazing. But there’s still a lot of work to do x.x (This article is dedicated to Dan. Without your help, my schedule (and also my mood) wouldn’t have allowed to me focus on all those points. Thank you!)

Unlocking the Magic of Zero-Knowledge-Proofs—Part 2: Artificial Reasoning and Limits of Information

জিরো-নলেজ প্রুফের ম্যাজিক আনলক করা—পার্ট 2: কৃত্রিম যুক্তি এবং তথ্যের সীমা

Die Magie von Zero-Knowledge-Beweisen erschließen – Teil 2: Künstliches Denken und Informationsgrenzen

Descubriendo la magia de las pruebas de conocimiento cero: Parte 2: Razonamiento artificial y límites de la información

Libérer la magie des preuves sans connaissance – Partie 2 : Raisonnement artificiel et limites de l’information

शून्य-ज्ञान प्रमाणों के जादू को खोलना-भाग 2: कृत्रिम तर्क और सूचना की सीमाएँ

ゼロ知識証明の魔法を解く—パート 2: 人工推論と情報の限界

영지식 증명의 마법 풀기 - 2부: 인공 추론과 정보의 한계

Desbloqueando a magia das provas de conhecimento zero – Parte 2: Raciocínio artificial e limites de informação

Раскрытие магии доказательств с нулевым разглашением — Часть 2: Искусственные рассуждения и ограничения информации

Sıfır Bilgi Kanıtlarının Büyüsünün Kilidini Açmak - Bölüm 2: Yapay Muhakeme ve Bilginin Sınırları

Giải phóng sự kỳ diệu của những bằng chứng không có kiến thức—Phần 2: Lý luận nhân tạo và giới hạn thông tin

解锁零知识证明的魔力——第 2 部分：人工推理和信息限制

DRY, or Don't Repeat Yourself, is one of the most well-known software development principles. Many engineers will go to great lengths to achieve this laudable goal, so a successful programming language must be designed with this in mind. Interfaces are just one of the tools that programming languages implement to enable code reuse. Although there are countless differences in the way programming languages implement interfaces, they all define a contract for interaction between software components. Differentiating itself from the typical object-oriented implementation, the Go programming language implements interfaces in a way that aims to reduce complexity, encourage composition, and enable flexible use of the types. Implicit Interfaces The most impactful difference between Go’s interfaces and those from object-oriented languages is that Go’s interfaces work by implicit implementation. Rather than requiring a type to explicitly declare that it implements an interface, determines that a type satisfies an interface as long as it implements all of the required method signatures. The different types and the interface they implement are only coupled by the code using them, rather than always being linked together. Go This difference offers a few key benefits: Reduce complexity and coupling by limiting the hierarchical inheritance of interfaces Simplify types that implement multiple interfaces Enables you to add interfaces later on when they become necessary instead of designing entire applications around them Interfaces can be created for types in different packages This last benefit is the most interesting and unique. The ability to define an interface based on external types leads to a few more specific advantages: Client code can define how it will use types rather than relying on library code to tell it how types must be used Create polymorphic relationships with types that you do not own or cannot change, which allows you to use them more flexibly Solve import cycle issues by changing the location of interface definitions Create mocks of imported types to make your code more testable No Inheritance By excluding inheritance, Go reduces the complexity that can occur from a deep hierarchical structure. When programs are designed around a base set of classes or interfaces, any simple changes to those base structures require a significant refactor. The alternative practice of composition leads to reduced complexity and more readable code. Composition relies on splitting up functionality among different types and using them together, instead of re-defining the functionality of types through inheritance. Now you can re-use these individual components elsewhere, add more functionality with new components, and easily refactor or remove existing ones. Instead of being concerned about what type something , your code just needs to know about what that type , and luckily the interface informs it. is can do Use Case: Polymorphism Polymorphism is perhaps the entire reason behind the existence of interfaces. This common practice is one of the most effective and easy-to-use methods of code reuse. Since an interface defines a strict contract for how types are used, these different types can be used interchangeably; this is polymorphism. A very common and useful scenario for this is having a flexible storage backend for your program: use Postgres in production, SQLite when running locally, and mocks when testing (or skip the database mocks, but that's a topic for another day). type StorageClient interface {
    GetValue(id string) (string, error)
}

func NewStorageClient(clientType string) (StorageClient, error) {
    switch clientType {
        case "sqlite":
            return sqlite.NewClient()
        case "postgres":
            return postgres.NewClient()
        default:
            return nil, fmt.Errorf("invalid client type: %s", clientType)
    }
} This implementation allows you to easily use the interface throughout the program without concern for the data storage layer behind it. StorageClient Use Case: Testing and Mocks You can take advantage of the implicit nature of interfaces by defining an interface for the functions you use from an external library. For example, you are assigned a task to implement a function that fetches recent rain data, in inches, from a weather data API. The made-up weather provider publishes Go package called , which provides a struct with various weather-related methods returning data in metric units: weather Client func GetRainInches(since time.Duration, client weather.Client) (float32, error) {
    rainMM, err := client.GetRain(since)
    if err != nil {
        return 0, fmt.Errorf("error getting data from API: %w", err)
    }

    return rainMM / 2.54, nil
} How will you unit test this code? Since Go has implicit interfaces, you can create your interface that just defines the methods that you need from the library. Now, if your function expects this interface instead, you can create your mocks. Since you currently just need the method, this is simple: GetRain type WeatherClient interface {
    GetRain(time.Duration) (float32, error)
}

func GetRainInches(since time.Duration, client WeatherClient) (float32, error) {
    rainMM, err := client.GetRain(since)
    if err != nil {
        return 0, fmt.Errorf("error getting data from API: %w", err)
    }

    return rainMM / 2.54, nil
} Then, your test file might contain a new struct that also implements the interface: type MockWeatherClient struct {
    expectedErr error
    expectedMM  float32
}

func (c MockWeatherClient) GetRain(time.Duration) (float32, error) {
    return c.expectedMM, c.expectedErr
} After this simple refactor, you do not depend on external libraries to provide interfaces that make your code testable! You have the additional side-effect of being one step closer to allowing your program to use different weather APIs generically. Conclusion and Warnings While interfaces in Go were designed with considerations for simplicity and avoiding some of the common pitfalls of object-oriented patterns, there are still some things to be aware of. It may be tempting to define interfaces for everything with the hopes that you can create a more generic and flexible program. Remember that one of the implicit interfaces is that you can easily create a new interface when you need it without making changes to any existing types, so there is no benefit to creating interfaces early in the process. Additionally, since types do not explicitly declare which interfaces they implement, it may be hard to tell which types are being used by your program when you have superfluous interfaces. While there are always tradeoffs and no perfect solutions, I have found Go's version of interfaces to be incredibly flexible, intuitive, and useful. I have been able to create more flexible programs and improve testability all while minimizing complexity. Also published here.

Go Interfaces Are Just Like Magic

Some time ago, I came across an amusing series of tasks on the website leetcode.com. The tasks themselves are not too difficult, but their solutions are quite intriguing. Moreover, problems of this type often appear in interviews at major companies, and understanding the methods of their solution can be quite beneficial. The First Task Is 136. Single Number (Easy) Given a non-empty array of integers where every element appears twice except for one, you need to find the element without a pair. Solve the problem in O(n) time complexity and with constant extra memory. Example 1: Input: nums = [1, 3, 3, 2, 6, 2, 1] Output: 6 Example 2: Input: nums = [12, 1, 1, 7, 1, 12, 1] Output: 7 Example 3: Input: nums = [6] Output: 6 Try to find a solution to the problem on your own. We will leverage the XOR function property, which yields 1 only when its operands are different. By traversing through all the elements of the array and performing bitwise XOR on them, we will zero out all identical bit values. As a result, what remains will be the desired outcome. Here is a short Python3 solution code: def single_number(nums: list) -> int:
    result = 0

    for el in nums:
        result ^= el

    return result We use only as much additional memory as an integer occupies, and find the solution in a single pass through the given array, giving us O(n) complexity. This is a concise and elegant solution. The Second Problem Is 137. Single Number II (Medium Difficulty) Given a non-empty array of integers where every element appears three times except for one, and only one element appears once, we need to find this unique element. Solve the problem in O(n) time complexity and with constant extra memory. Example 1: Input: nums = [3, 1, 3, 3] Output: 1 Example 2: Input: nums = [12, 1, 1, 5, 1, 12, 12] Output: 5 Example 3: Input: nums = [6] Output: 6 Try to find a solution to the problem on your own Unfortunately, we cannot use the previous trick in this case since we cannot turn paired bits at the required position into zeros. It would be tempting to transform the given array into the format from the previous task, and then solve it in a similar way. Reasoning this way, it's easy to notice that if we knew that we had already encountered the number N twice (or thrice) while traversing the array, we could add an additional XOR with N to the sum we are obtaining. This would make the final XOR with this number even, thereby removing it from the final sum, and what remains would be our answer. def single_number_ii(nums: list) -> int:
    mem = {}
    result = 0

    for el in nums:
        if not mem.get(el, False):
            mem[el] = 1
        else:
            mem[el] += 1
            if mem[el] == 2:
                result ^= el
        result ^= el

    return result Unfortunately, this solution would require a maximum of (len(nums)-1)/3 in terms of memory, which cannot be considered constant consumption, so we will have to look for another solution. Let's try changing our approach. Earlier, we used XOR (which represents addition modulo 2). If we had implemented addition modulo 3, we could have easily applied the trick from the previous example. If we can put a number into the answer the first time we encounter it, put it in the accumulator the second time, and zero out both the answer and the accumulator the third time, it would help us solve the problem in one pass-through the list with additional memory consumption exactly equal to two integers, meeting the task requirements. So, let's apply a bit more bitwise magic: def single_number_137_ii(nums: list) -> int:
    ans, acc = 0, 0

    for n in nums:
        ans = ans ^ n & ~acc
        acc = acc ^ n & ~ans

    return ans This way, all triple numbers get zeroed out, and we are left with only the number that occurs only once. The Third Task Is 260. Single Number III (Medium Difficulty) Given a non-empty array of integers where every element appears twice, except for two elements that appear only once, we need to find these unique elements. The goal is to solve the problem in O(n) time complexity and with constant extra memory, and the order of the unique elements does not matter. Example 1: Input: nums = [1, 2, 1, 3, 2, 5] Output: [3, 5] Example 2: Input: nums = [1, -2] Output: [-2, 1] Try to find a solution to the problem on your own Obviously, we can easily eliminate all paired numbers using the XOR operation, as we did in solving the first task. The complexity of the task then lies in identifying any of the unique numbers, after which the second one can be easily computed by XOR-ing it with our XOR sum. To achieve this, we just need to find any differing bit between these unique numbers. Then, we iterate through the array again, performing XOR summation and dividing the results into two groups - for numbers where this bit is set and for those where it is 0. As a result, we obtain the desired unique elements. def single_number_260(nums: list) -> int:
    res1, res2 = 0, 0
    glob_xor = 0

    for n in nums:
        glob_xor ^= n

    diff_bit = glob_xor & ~(glob_xor - 1)

    for n in nums:
        if n & diff_bit:
            res1 ^= n
        else:
            res2 ^= n

    return [res1, res2] Despite having to iterate through the array twice, the complexity remains O(n), and the memory consumption is only 2 integers. NB: Despite the fact that int in Python is not exactly the same as int in other languages, we will consider its size as a constant

A Bit of Ancient Algorithmic Magic, or Solving an Intriguing Sequence of Tasks From LeetCode

প্রাচীন অ্যালগরিদমিক ম্যাজিকের একটি বিট, বা লিটকোড থেকে কাজগুলির একটি আকর্ষণীয় ক্রম সমাধান করা

Ein bisschen alte algorithmische Magie oder das Lösen einer faszinierenden Abfolge von Aufgaben mit LeetCode

Un poco de magia algorítmica antigua o resolver una secuencia intrigante de tareas de LeetCode

Un peu de magie algorithmique ancienne, ou résoudre une séquence de tâches intrigante à partir de LeetCode

प्राचीन एल्गोरिथम जादू का एक अंश, या लीटकोड से कार्यों के एक दिलचस्प अनुक्रम को हल करना

古代のアルゴリズムの魔法、または LeetCode からの興味深い一連のタスクの解決

약간의 고대 알고리즘 마법 또는 LeetCode의 흥미로운 일련의 작업 해결

Um pouco de magia algorítmica antiga ou resolvendo uma sequência intrigante de tarefas do LeetCode

Немного древней алгоритмической магии, или Решение интригующей последовательности задач из LeetCode

Biraz Kadim Algoritmik Sihir veya LeetCode'dan İlgi Çekici Bir Görev Dizisini Çözmek

Một chút phép thuật thuật toán cổ xưa hoặc giải một chuỗi nhiệm vụ hấp dẫn từ LeetCode

一点古老的算法魔法，或者解决 LeetCode 中一系列有趣的任务

Stories, News & Mentions about MAGIC

Magic’s Stories on HackerNoon

Magic's News & Mentions