VCs are excited about generative AI startups that can make coding more efficient. Poolside, Magic, and Augment have raised the most funding.

AI coding startups are becoming a hotspot for VCs. Here are the 12 copilots that have landed funding from funds like a16z, Lightspeed, and Menlo Ventures.

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

The Orlando <strong>Magic</strong> have hit the home stretch of the regular season vying for home-court advantage in the first round of the playoffs, as they host the struggling Portland Trail Blazers on Monday.

Magic, buoyed by stout defense, take on depleted Blazers - CBSSports.com

The NBA has released their last two minute report for Clippers vs. <strong>Magic</strong>

NBA Admits Big Missed Calls in LA Clippers vs. Orlando Magic

Analyzing Saturday&#x27;s Memphis Grizzlies at Orlando <strong>Magic</strong> odds and lines, with NBA expert picks, predictions and best bets.

Memphis Grizzlies at Orlando Magic odds, picks and predictions

Los Angeles Clippers superstar Kawhi Leonard speaks to the media following the Clippers 100-97 win over the Orlando <strong>Magic</strong>. Kawhi finished the game with 29 po...

Kawhi Leonard Reacts To The Clippers 100-97 Win Over The Magic. HoopJab NBA - YouTube

Los Angeles Clippers star Kawhi Leonard speaks to media after Clippers beat Paolo Banchero and Orlando <strong>Magic</strong>. Kawhi Leonard interview. Kawhi Leonard postgame...

I'm Not Worried About Playoffs!' Kawhi Leonard Reacts To Clippers Win Against Magic - YouTube

Memphis Grizzlies vs Orlando <strong>Magic</strong> Mar 30, 2024 player box scores including video and shot charts

Memphis Grizzlies vs Orlando Magic Mar 30, 2024 Box Scores | NBA.com

Expert recap and game analysis of the LA Clippers vs. Orlando <strong>Magic</strong> NBA game from March 29, 2024 on ESPN.

Clippers 100-97 Magic (Mar 29, 2024) Game Recap - ESPN

Magic

magic

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.

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/

Stories, News & Mentions about MAGIC

Magic’s Stories on HackerNoon

Magic's News & Mentions