Desde hace un tiempo estoy buscando la respuesta a cómo añadir a mi hija a mi perfil de residente. En las FAQ´s, pone que al darse de alta el hijo hay que hacerlo constar. Cuando le dí de alta (es menor de edad) no ví esa opción y ahora no sé cómo vincularla. Si alguien que lea esto, sabe a dónde tengo que acudir o qué puedo hacer, le estaría agradecido. Un saludo, Juan

Hey! Its me again, you are may be getting used to read me, anyways, another of my projects is to create an encryption suite, similar to the SSL standard. It provides 4 features: AIKE(Advanced Iris Key Encryption): It's actually used to encrypt the public key, in case you want to. AIEE(Advanced Iris Encoding Encryption): It's to encrypt and avoid null bytes AIHE(Advanced Iris Hash Encryption): It's to generate a hash and encrypt it, so we can validate the connection AIE(Advanced Iris Encryption): It's the algorithm to encrypt the blocks of data Altho it was more of an introductory post on that suite, i will post on how the actual algorithms work, and if possible, i would like to convince to the IT team to use it instead of SSL

What do i want to achieve with all my work & projects? I want to show to all my beloved Asgardians that there's always hope! You can develop whatever skills are required to do the job. Certainly, there are physical limits, but usually it's a problem of mental barriers. So go ahead! I will keep showing that all is possible with time and motivation!

_______________________________________ UREL _______________________________________ ·Objective: -. Use Ultraviolet light(type-A) bounced from the Earth surface/Troposphere. ·Description: -. Installation at the bottom-side of the ship a series of PV Cells to convert the UV-A bounced from the Earth surface/Troposphere, due to CFC particles dividing Ozone into chlorine monoxide and oxygen, into electric voltage. _______________________________________ TGE _______________________________________ ·Objective: -. Use the high temperatures of individual gas molecules. ·Description: -. Using thermo-electric materials to capture high-temperatures individual atoms of gas and convert it to electricity(may needs a thermo-resistant material layer to filter such temperatures(they can reach ~2000ºC)). _______________________________________ IAE _______________________________________ ·Objective: -. Approachs the ionization of atoms thanks to the Ionosphere. ·Description: -. Use electrochemical cells to convert ionized atoms to electricity using carbon nanomaterials to extract the electric charge.

Okay, the mirrored moon project were a bit ideally. Well, actually, a lot(that doesn't means that we won't take any action on the future if we can), so… lets talk about something that is happening right now, the Iris Project, a brand new programming language. Short showcase that only shows the compilation of const global vars -> https://vimeo.com/357272053 Long showcase that shows the whole UI(we will make it more beauty, don't worry) and a bit of the features the language will have, unfortunately, it's in Spanish -> https://www.youtube.com/watch?v=eZWAON-Lg5A But… Why we did reconsidered to don't develop the C++ framework. Simple enough, C++ is deprecated. And no, don't get us wrong, we know the C++ language features have been evolving(C++11, C++14, C++17, C++20...) and the libraries/frameworks has also been in constant development. We say it's deprecated, because its low level features are odd, a lot(we can explain that further in the comments section if anyone have any doubts about how we ended up into that resolution). We try to see other languages that offer some solutions to the C++ problems, such Rust & Go, but Rust memory model didn't offer what we are looking for, and Go just has a lot of problems of design for us. So now we have the initial motivation to go for, but it's not a real reason to design an entire programming language and the tools that it implies. Why we would do that then? The answer is the language itself. We really loved each new piece of design that came to our mind. And we are gonna share that here, today, now. First, we decided to make the language totally network dependent. What does this means? And why would we make it? This concept implies that the code written by the client, would be sent to our server, hosted(TOTALLY) by us, being compiled, and send back the response to it(a binary or a retina map(similar to AST format from Clang/LLVM)). Obviously the data would be encrypted for both sides. The reasons to do that: - Multi-platform(i.e., compile from a Windows machine for a Linux) - Multi-architecture(i.e., we could compile the same code sent by the user for the different target architectures, lets say SSE2 and NEON, without any explicit intrinsics or SIMD instruction lossy, absolutely everything will be handled by the compiler in a perfect way by generating a new binary for each architecture specialization). - But wouldn't generating a binary for each different target architecture consume a lot of the client hard disk space? No, because the library/application will be offered by stream: ·Libraries: - The code will be formatted to Retina map, so further compilations will take shorter times. - The retina map will be stored at the server, and it returns an ID and the public, external methods symbol/arguments, so the Iris IDE will know how the exported methods are structured. - The ID and exported methods are stored at the client hard disk with the extension .retina, and it's imported at the Iris IDE importing project at anytime it's gonna be used. - Once we compile using that library, the ID will be sent, and the server will create a relationship between that ID and the library code formatted before to retina map, so the compiler knows we are linking against that. Application: - The code is being compiled for the different platforms/architectures on their respective ABI format, and stored at the server hard disk. - A retina file with(only) the ID that links against the location of the compiled application will be provided for the programmer client. - The end user must have installed Iris Manager, which sends to the server the input(the retina file with the ID), and the detection of the actual user OS/Arch capabilities, retrieves the most appropiate(if any) version of the compiled application. MORE FEATURES AT THE COMMENTS SECTION

Asgardia plans to add in a near future, spaceships over the Earth orbit. The design for these spaceships is pretty big, bigger than any satellite around us, right now. So, how could we feed that monstrosity at the dark side of the Earth if the Sun's light doesn't show up there? Would the energy that we got from the far-far stars be enough? May be, but at Iris Technologies we don't think it's something to leave to any researching study, so we came up with an alternative solution, mirrors at the moon. Now we planned the problem, how that fancy solution would work? To answer that, we need to ask ourselves, which color the moon has at night? White/light gray! Here's the thing. Meanwhile our spaceship is at the darkside of the Earth, due to the Earth itself hiding us from the Sun, the moon isn't! Unfortunately, the moon surface material can't reflect a high percentage of the UV's rays it receives, but… Who said we would be using the moon surface? Affortunately, there are tons of UV-A reflective materials, and they are relatively cheap, so we could build a camp of mirrors with this reflective material. There we go! We have our ship being fed by our reflective mirrors, isn't it? Yes, but..., just for a second. Because our ship would be constantly moving, and that is the last step to achieve our goal. So what we will need now is first, to install a rotator on the base of the mirrors so they can rotate to reflect the UV rays effectively at the position of our ship, and next, we will need to get this position by installing a GPS to our ship that sends our(spaceship) actual coordinates to the mirrors(through an antenna), and use some math on the angles, to constantly rotate to the right axis the mirrors. Now we are really done, and we have our Project: Mirrored Moon completed.