#Debugging Interface

[ctfsec]

Debugging Interface

DESCRIÇÃO DO DESAFIO

Acessamos a interface de depuração serial assíncrona do dispositivo embarcado enquanto ele estava operacional e capturamos algumas mensagens que estavam sendo transmitidas por ele. Você consegue decodificá-las?

Passos: Baixar os arquivos necessários:

Após baixar os arquivos, você vai extraílo, isso gerará uma pasta .sal, ao fazer uma pesquisa pois não conhecia esse tipo de arquivo, descobri que .sal é o formato de arquivo usado pelo software do Saleae Logic Analyzer. Baixei o software.

Para rodar, será preciso dar permissão de execução, então rodei: chmod a+x Logic-2.4.14-linux-x64.AppImage

./Logic-2.4.14-linux-x64.AppImage --no-sandbox

Com isso abriu a janela:

Aqui vamos arrastar o arquivo .sal que foi gerado após extrair o zip:

E ficará assim:

Precisamos dar zoom, é só segurar o ctrl e ficar clicando na parte preta, e ficará assim:

Na descrição do ctf está escrito: Acessamos a interface de depuração serial assíncrona. No Salae, se formos em add analyser, vemos que tem a opção async serial:

E teremos a seguinte janela:

Aqui, como queriamos descobrir o que estava escondido, coloquei o tamanho da onda, aquele numero que aparece na imagem 5, cliquei em analyzers e tcharam:

Pegamos a flag. Como hardware não é o meu forte, eu pesquisei alguns writeups após a conclusão pra ver se eu tinha seguido o caminho certo, e teve algumas diferenças haha, acho que por não manjar muito eu segui por uma lógica muito simples. Se quiserem ver outras soluções, recomendo o

Write-up diferente Mas foi isso. Obrigada pra quem leu e boa sorte a quem tentar.

Linkedin: Luana htb: moominLua

[techav]

On Making Progress

With my Wrap030 homebrew computer operational again, I could finally get back to the work I had been wanting to do with it in the first place. I was able to get it running my multi-user BASIC kernel from ROM with the main board, DRAM card, and 8-port serial card.

There's still more work I want to do with software, and pulling and burning the ROM for every little change is not a great way to develop software. It would be great if I could load programs from a disk instead. I did previously have disk access working, but that was with a different system configuration and a different ROM. There was also a limitation with my old code where files that spanned multiple clusters didn't load right.

So I needed to test the system with the FPU+IDE mezzanine board added to the stack, and I needed to add disk load functions to my ROM.

Adding the FPU board went better than expected. I added it to the stack and the system continued running as it had previously. I didn't even have to lower the clock speed to compensate for the new board.

So time to update that ROM. My previous disk load functions were written to work with the TSMON monitor program I had been using. I wanted something that could load my Multibasic system (or another OS) without intervention, so TSMON was not going to be a good fit. All I really needed was a simple bootloader — something that could load a file, BOOT.BIN, from the disk and run it.

Rather than try yet again to wrap my head around parsing FAT filesystem headers and how to traverse the allocation table, I decided to try using an existing library. The Elm-Chan FatFs library was just the thing I needed. It's written to be portable, needs only a few custom functions implemented by the host system for disk sector reads, and documented reasonably well. I was able to get it running in a weekend, including all the time it took for me to debug my own silly mistakes like reading only 510 bytes of each disk sector instead of 512 and accidentally swapping bytes when caching data read from the disk.

Getting Multibasic ready to run from disk instead of from ROM was actually fairly straightforward since it was already built to be loaded from ROM to RAM and then run from there. I just needed to make a few minor changes to the linker script and add a branch at the beginning of its vector table.

So after many hours of work, I am right back where I was at the start … but also miles ahead of where I started. If I need to make a change to the Multibasic kernel, I can just copy the new program to a CompactFlash card like any other file. If I want to load a new program I can do so easily. And swapping programs is as easy as swapping cards and hitting Reset.

[frog707]

RenderDoc the block

Today I solved the blocking issue in my Macana OpenGL project. I did it using RenderDoc, an open-source graphics debugger suggested to me by a colleague.

Since I'm a complete noob at RenderDoc (and not very proficient at OpenGL either), it took me awhile to gain traction. I didn't use the tool very effectively. But the key virtue of a good debugger is that helps users visualize what's going on. Somehow in the flood of details, I noticed that my problematic texture (which didn't have mipmaps) used a filter intended for mipmaps. And that proved to be my issue.

Meanwhile, I'm making progress configuring my new Linux Mint environment. I finally got the Cinnamon panel (analogous with the Windows taskbar) configured the way I like. I must've spent hours; it seems to me the Cinnamon UI could be a lot more intuitive.

Also I discovered I had 2 copies of LibreOffice: one installed from Apt and another installed from Flatpak. I only need one copy, so I'm removing the older (Apt) install to free up disk space.

[cognithtechnology]

Introduction to API Testing for Beginners Start your journey in API testing with our beginner-friendly introduction and essential tips.

[stimkyyy]

sry guys idk how 2 get the boop button or wtv i am infact 80yos mentally

[engineering]

StreamBuilder: our open-source framework for powering your dashboard.

Today, we’re abnormally jazzed to announce that we’re open-sourcing the custom framework we built to power your dashboard on Tumblr. We call it StreamBuilder, and we’ve been using it for many years.

First things first. What is open-sourcing? Open sourcing is a decentralized software development model that encourages open collaboration. In more accessible language, it is any program whose source code is made available for use or modification as users or other developers see fit.

What, then, is StreamBuilder? Well, every time you hit your Following feed, or For You, or search results, a blog’s posts, a list of tagged posts, or even check out blog recommendations, you’re using this framework under the hood. If you want to dive into the code, check it out here on GitHub!

StreamBuilder has a lot going on. The primary architecture centers around “streams” of content: whether posts from a blog, a list of blogs you’re following, posts using a specific tag, or posts relating to a search. These are separate kinds of streams, which can be mixed together, filtered based on certain criteria, ranked for relevancy or engagement likelihood, and more.

On your Tumblr dashboard today you can see how there are posts from blogs you follow, mixed with posts from tags you follow, mixed with blog recommendations. Each of those is a separate stream, with its own logic, but sharing this same framework. We inject those recommendations at certain intervals, filter posts based on who you’re blocking, and rank the posts for relevancy if you have “Best stuff first” enabled. Those are all examples of the functionality StreamBuilder affords for us.

So, what’s included in the box?

The full framework library of code that we use today, on Tumblr, to power almost every feed of content you see on the platform.

A YAML syntax for composing streams of content, and how to filter, inject, and rank them.

Abstractions for programmatically composing, filtering, ranking, injecting, and debugging streams.

Abstractions for composing streams together—such as with carousels, for streams-within-streams.

An abstraction for cursor-based pagination for complex stream templates.

Unit tests covering the public interface for the library and most of the underlying code.

What’s still to come

Documentation. We have a lot to migrate from our own internal tools and put in here!

More example stream templates and example implementations of different common streams.

If you have questions, please check out the code and file an issue there.

[strawberry-bubblef]

Hi! Could I request a platonic ignihyde fic with a child reader who is surprisingly good at coding?

Ignihyde with a Child!reader who is good at coding

Idia Shroud

To say Idia was surprised when Crowley dropped a literal child into his dorm would be an understatement.

He had stared, wide-eyed and frozen, the corners of his mouth twitching with something between panic and suspicion.

“…Okay,” he muttered. “Okay. The headmage finally snapped. I’m hallucinating a child. A child with a backpack. And stickers on their tablet.”

You, meanwhile, were silent. You stared up at the tall, nervous man in the oversized hoodie and fire-blue hair and tilted your head slightly.

“…You’re Idia Shroud,” you said flatly, stepping into his room uninvited and peering at his screens. “Your garbage collector keeps triggering on a five-second cycle. That’s inefficient.”

Idia made a strangled noise. “Wha—?!”

“I can fix it,” you added.

You sat down beside him like you’d done it a hundred times, pulling your tablet out and typing with quiet precision.

And somehow, Idia let you.

It was weird, having someone near him who didn’t need constant social buffering. You weren’t loud. You didn’t force him to talk when he didn’t want to. You liked silence, blinking cursors, logic loops, and cat-themed IDE skins.

Idia thought he might actually be dreaming.

Still, he kept his distance for a while. You were a kid. What if you cried when he got snappy? What if you tripped and broke a server blade? What if Ortho accidentally sent you to the Shadow Realm during VR testing?

But you didn’t cry. You didn’t break anything. You added new firewall protocols to his gaming network and reorganized his project folders in a way that actually made sense.

“…Okay,” he mumbled one night, awkwardly scooting over to make room at his desk. “You can help. But only a little. Like. One file.”

You fixed six and added a debugging tool of your own design.

“…I’m not crying,” he muttered later, face hidden behind a chip bag. “There’s just… too much screen brightness.”

You didn’t say much, and neither did he. But he got used to your presence,the soft tap of your fingers on a keyboard, the way you leaned against the side of his chair when you got sleepy. The way you hummed random game soundtracks while coding, and quietly slid snack packets toward him when his stomach growled.

And you got used to his muttering. His panic,rambling. His snarky comments. You even got used to how he covered his mouth when he was embarrassed.

“You don’t talk like other people,” you said once, blinking up at him.

Idia flinched. “Oh. Uh. Sorry, I guess? I can turn it down.”

You shook your head. “I like it.”

His hair turned a little pink at the ends after that.

He didn’t call you his sibling. Not out loud. Not even in his head, really.

But sometimes he’d look over and see you curled up with your tablet beside him, lines of elegant, efficient code dancing across the screen and he’d feel something settle quietly in his chest. Something warm. Safe.

“…Player Two,” he muttered once, brushing your hair out of your face while you napped.

No response, of course. But your fingers twitched in your sleep, like you were still typing.

He smiled.

Ortho Shroud

The first time Ortho met you, his eyes lit up,literally.

He zipped down from the sky like a comet, bright and excitable. “HI! Are you the new guest staying in Ignihyde?! Crowley told us someone really cool was coming but didn’t give details so I ran ten background checks just in case and—”

You blinked up at him, holding your tablet close to your chest.

“…You’re a robot,” you said simply.

“I’m a technomantic humanoid !” Ortho corrected, glowing a bit brighter. “But yeah! Basically a robot!”

You nodded once. “Cool.”

And then you offered him your tablet.

“Want to see my code?"

To Ortho, that was like being handed a treasure map.

He zipped in close, blue eyes scanning rapidly over your custom interface. “You coded all this yourself?! Wait—these are recursive functions written in HexaScript??”

You nodded. “I optimized the loops. The compiler doesn’t like it sometimes, but it’s fast.”

Ortho hovered in stunned silence.

From that day on, Ortho was stuck to you like a magnet. If you were in the room, he was hovering nearby,spouting programming facts, asking questions, or quietly watching you work while glowing with barely contained energy.

And in return, you liked having him around.

He was loud, sure, and sometimes he got too excited. But he treated you like an equal. He never talked down to you. He never made you feel small, even when you had to stand on tiptoe to reach the desk.

Plus, he let you “borrow” high-grade Ignihyde tech when Idia wasn’t looking.

Ortho often dragged you around the dorm to show you off.

“Look! They built a proxy network to bypass dorm firewalls!”

“They made me a new mini-game and I got the high score!”

“They reprogrammed the toaster so it says ‘good morning’ in binary!”

You didn’t mind. You liked seeing him that happy,how he buzzed with pride and sparkled like stardust.

He even started adapting some of his flight stabilizers to help you reach high shelves. And every time you successfully debugged something difficult, he did a victory spin in the air and called it a “micro hero moment.”

You never had a big family. Never had people who got your weird little projects or your late-night tinkering.

But now you had Ortho.

And he understood your code like it was a language only the two of you spoke.

English is not my first language !

[rathologic]

Basic Pathologic 3: Quarantine Cheats

To use any cheats, toggle open the developer overlay with Ctrl+Shift+`. This view will default to the Info menu, which displays information about your hardware and performance. Use the dropdown in the top left to switch between menus.

From the Settings menu, you can toggle on and off several useful cheats as well as in-game settings. Here are the most useful options:

Debugs:

UIVisible: Turning the entire user interface off is basically “photo mode” – useful to take pretty screenshots. You’ll need to turn it back on to access the map or menus.

DebugMove: Get around quickly! Enables jumping, and boosts your running and jumping speed. This allows you to go out of bounds.

DevMenu:

DebugVisible: Enables a submenu of the Main Menu from which you can load saved games, and another that lets you load into any scene in the game. If you try to load a scene that doesn’t exist (like Grief’s lair), the game will hang while loading.

From the Console menu, you can enter commands to affect the game state. Type “?” to view the list of all commands.

camera: Use “camera Fly” and “camera FirstPerson” to toggle a fast fly camera mode which does not move the player entity.

game_save: Use this command to save your game. You can add a second argument to specify the save file name.

item_add: Type “item_add ?” to view the list of all items, then “item_add item_name.def” to add them to your inventory.

player_parameter: View and modify various player setting values.

time_set: Sets the time of day. For example, “time_set 13h 30m 2s” for 1:30:02 pm. This appears to only affect the skybox.

weather_set: Sets the current weather (type “weather_set ?” for the list). For example,

“weather_set Empty 0” disables all clouds.

“weather_set Clouds 0” makes the skies entirely overcast.

"weather_set "Rain 0.8" 0" makes it overcast and furiously raining.

“weather_set MainMenu 0” changes the weather to localized rain, while small clouds quickly blow past.

[commodorez]

What was the purpose of the panels of blinking lights on those big mid-century computers? Were they showing calculations in progress?

Excellent question, this is one of my favorite subjects! Blinkenlights serve a number of functions. Hollywood tended to use just the lights to make it look like a computer was busy doing something, but real computers had more than just lights on their front panel. Let's walk through a few examples of use cases with photos of computers I've seen over the years at museums and vintage computer festivals:

Some front panels were built to be used for diagnostics. Computers like these were primitive enough that they required constant care and debugging to do their jobs, especially the early vacuum tube machines (everything pictured here is transistorized). You could tell what peripherals were being used, but also check the status of registers, carry flags, status flags, data, various buses, etc. It was also a way to see if a program had "gone off into the weeds" and started doing things that were irregular, possibly due to a software bug, or a problem with the hardware.

On many of these machines, you can enter programs directly into the main memory using the front panel, but it's an incredibly tedious process -- something to be avoided if possible. Consider it a last fallback.

Other times, it's a starting point, which we call "bootstrapping" (this eventually evolved into the term "booting"). You aren't likely to program everything on such a limited interface, but you are more likely to enter in a small program that can tell the computer how to run a more complex peripheral, like a paper tape or punch card reader, or maybe some type of magnetic storage device. Once you can get a program loading off of a larger permanent storage device, you can load up software to interface with a terminal of some kind which is much easier.

Eventually, the microprocessor made home computers a possibility, but many were only equipped with a front panel out of the box. You would have to add in a serial card, more RAM, possibly some ROMs, and either a teletype or glass terminal in order to get a more sophisticated and intuitive interface from the computer, capable of programming in a higher level language. Some were considered more like trainers, or hobbyist devices, and simply lacked that ability, meaning all you got was a front panel with switches and lights.

I made my own front panel to see what the experience was all about:

Then everything changed in 1977, with the introduction of these three machines: the TRS-80 Model I, the Commodore PET 2001, and the Apple II. They were what you might call "appliance computers" and they had no need for a front panel.

Hopefully that answered your question!

[webfarmhouses-blog]

Web designer in Jodhpur

Creative Web Design

We are a web designing company that has a team of skilled and experienced web designers and developers who can create stunning and functional websites for any type of business or domain. We offer a variety of web designing services, such as custom web design, web development, web hosting, SEO, and maintenance. We also provide you with a free web design consultation, where we can discuss your goals, needs, and preferences, and provide you with a web design proposal that suits your requirements and expectations.

What we do in Web Design

Our web designing services are the services that provide web designing solutions for clients who want to create or improve their online presence. It involves the use of various elements such as colours, fonts, images, graphics, animations, and interactions to convey the message and purpose of the website to visitors. Web designing services can help clients with various aspects of web designing, such as Consultation: Our web designing services can help clients understand their goals, needs, and preferences, and provide them with expert advice and guidance on how to achieve them . Strategy: Our services can help clients develop a clear and effective web design strategy that aligns with their brand identity, target audience, and business objectives.Design: We help clients create a unique and attractive web design that reflects their vision and personality, and that engages and impresses their visitors.Launch: Our services can help clients launch their website to the public, and provide them with web hosting, domain registration, and security services.

Our Design Technology

At Web Farm House, we understand that web design is not just about making a website look good. It is also about making it work well, communicate effectively, and provide value to the users. That is why we use the latest web design technology to create websites that are:

Visually appealing: We use web graphic design to create stunning and consistent visual elements for your website, such as colours, fonts, images, icons, and animations.

Easy to use: We use user interface design to create intuitive and interactive elements for your website, such as buttons, menus, forms, and navigation.

Functional and reliable: We use web development to code and program your website, using languages such as HTML, CSS, JavaScript, PHP, and others. We follow the principles of web standards, web accessibility, web performance, and web security, to ensure the quality and reliability of your website.

Our Work Process

At Web Farm House, we follow a systematic and collaborative work process to create your website. Our work process consists of four main phases: Discovery, Design, Development, and Delivery:

Discovery: This is the phase where we get to know you and your project. We will ask you some questions about your goals, needs, preferences, budget, and timeline. We will also conduct some research on your industry, competitors, and target audience. Based on the information we gather, we will create a project proposal and a contract for you to review and approve.

Design: This is the phase where we create the visual and interactive elements of your website. We will start by creating a sitemap and a wireframe, which are the blueprints of your website’s structure and layout. We will then create a mockup, which is a prototype of your website’s appearance and functionality. We will present the mockup to you and ask for your feedback and approval. We will make any revisions as needed until you are satisfied with the design.

Development: This is the phase where we code and program your website. We will use the latest web development technology to create a website that is functional, reliable, and compatible with different devices and browsers. We will also test and debug your website to ensure its quality and performance. We will show you the progress of the development and ask for your feedback and approval.

Delivery: This is the final phase where we launch and maintain your website. We will upload your website to your chosen hosting service and domain name. We will also provide you with a user manual and a training session on how to use and update your website. We will also offer you ongoing support and maintenance services to keep your website running smoothly and securely.

We will also listen to your feedback and suggestions and make any changes as needed. We will work with you as a partner and a friend, not just as a client and a vendor. we value your input and satisfaction throughout the work process. We will communicate with you regularly and keep you updated on the status of your project.

Our Web Designing Services

Our is provides web design services for clients who want to create or improve their online presence. We help clients with various aspects of web designing, such as consultation, strategy, design, development, testing, launch, and maintenance:

Static web design

Liquid web design.

Adaptive web design.

Dynamic web design.

Responsive web design.

Single-page web design.

Why Choose Us?

We are a One-Stop Solution for delivering the best web design and development services. We render customized and affordable web design facilities to suit your requirements. Choose the best plans for building a responsive web design according to your needs:

Excellent technical support

Core PHP &Codeigniter + MySQL.

Secure and Reliable coding.

Satisfactory Customer Support.

SEO-friendly web development.

[otomefowl]

heeellooooo! How are ya’ll doing? Is there an estimated release date? How’s far along is the process? (Hopefully not sounding pushy!! That’s not my intent sry lol) hope you’re doing well!

It's all good, we love to see interest! My plan for now is to get a demo out as soon as we can. The demo includes the introduction of all eight characters, so it's pretty meaty. I'm currently in the debugging stage with the code, and from there it's almost all aesthetic: backgrounds, music (which will all be free for the demo), and other odds and ends. Because of this, there may be some changes in the user interface and even some art between the demo and the first chapter.

"First chapter? What does that mean?" Well, in order to keep up interest, the rest of the introduction will be released before the character routes in a "first chapter." By the end of this chapter, the player will be ready to pick an Artemis to play along. After that, the current plan is to release a few routes at a time.

TLDR; The demo will at most be done by the end of this year (I'll do better at updating on progress). The full game, however, will release over the span of a few years, depending on availability of our volunteers.

[tf-kinky]

Finn had always lived in the shadow of his older brother, Brock. At nineteen, Finn was a wiry, pale kid with a mop of greasy black hair and a knack for tinkering with tech. Brock, on the other hand, was a chiseled twenty-two-year-old jock, six-foot-three with biceps that strained every shirt he owned. He’d been the golden boy of their small town—star quarterback, prom king, the works. Finn? He was the weird one, the kid who’d rather debug code than throw a football. Brock never let him forget it, either. “Hey, Finn-tastic,” he’d jeer, ruffling Finn’s hair like he was still a toddler, “gonna build me a robot girlfriend since no real girl’s gonna look at you?”

Finn had taken it for years, swallowing the bitterness like a jagged pill. But last week, when Brock “borrowed” Finn’s laptop to stream a game and spilled beer all over it—ruining months of work—that was the final straw. Finn wasn’t just mad. He was done. He’d had enough of Brock’s smug grin, his effortless charm, his stupid, perfect life. Finn wanted something for himself, something Brock could never take away. And then he found the app.

It was buried deep in a dark web forum, a sketchy .apk file called “PermaMorph.” The description was cryptic: “Transform anything—or anyone—permanently. No takebacks.” Finn’s pulse raced as he downloaded it onto his cracked old phone, the kind Brock mocked him for not upgrading. The app’s interface was simple: a single text box to type the target’s name, a dropdown for the transformation, and a slider labeled “Sensory Amplification.” Finn didn’t hesitate. He typed “Brock” into the box, scrolled through the options—dog, toaster, chair—until he landed on “Tesla Cybertruck.” He’d been drooling over that angular, futuristic beast since it hit the market, but at $80,000, it was a pipe dream. Until now. For the sensory slider, he cranked it to max. If Brock was going to be a truck, Finn wanted him to feel every second of it. Then he hit “Execute.”

The change happened fast. Finn was in his basement room, hunched over his phone, when he heard a muffled yell from upstairs. He bolted to the living room, where Brock had been sprawled on the couch, midway through a protein shake. Now, Brock was frozen mid-sip, his body shimmering like a glitchy video game character. His skin turned metallic, his arms elongated into sharp, angular panels, and his legs fused into thick, rugged wheels. His face—oh, his stupid, handsome face—flattened into a sleek windshield, his eyes becoming headlights that flickered once before going dark. The protein shake clattered to the floor, splashing across the hardwood as Brock’s massive frame settled into the unmistakable shape of a Tesla Cybertruck. Silver, gleaming, and utterly lifeless.

Finn stood there, mouth agape, as the transformation finished. The room smelled faintly of ozone and burnt rubber. Where Brock had been lounging moments ago, a full-sized Cybertruck now took up half the living room, its front bumper nudging the coffee table. Finn reached out and tapped the hood. Cold. Solid. Real. He grinned.

But Brock wasn’t gone—not entirely. nside the inanimate shell, Brock’s mind was screaming. Every vibration of the floorboards as Finn paced around him felt like an earthquake. The hum of the refrigerator in the kitchen was a deafening roar. The faint breeze from the open window scraped across his metallic surface like sandpaper. He could feel it all—every scratch, every speck of dust, every shift in temperature—but he couldn’t move, couldn’t speak, couldn’t even blink those headlight eyes. He was trapped, a prisoner in a body that wasn’t his anymore, hyper-aware and helpless.

Finn didn’t know that part, and he didn’t care. He climbed into the driver’s seat, running his hands over the steering yoke. The interior smelled new, like leather and factory steel. “Hey, Brock,” he said, patting the dashboard. “Guess who’s useful now?” He turned the key—well, pressed the start button—and the truck purred to life, its electric motor rumbling softly. Finn laughed, a sharp, triumphant sound, and peeled out of the driveway, tires squealing as he left tire marks on the street.

For Finn, it was freedom. He cruised through town, windows down, basking in the stares of neighbors who couldn’t believe scrawny little Finn was rolling in a Cybertruck. He didn’t care that Mom would freak when she got home and found Brock missing. He’d figure out a story—Brock ran off with some girl, maybe. For now, this was his victory lap.

For Brock, it was hell. Every pothole Finn hit sent shockwaves through his frame, every honk from passing cars pierced his nonexistent ears, and every bug that splattered on his windshield felt like a personal violation. He couldn’t scream, couldn’t beg, couldn’t do anything but endure. Finn had his dream ride, and Brock was it—forever.

Hope you enjoyed the story! I was aided by Grok AI

[redfoxv]

Got a mission for you. We need you to investigate sector 137. A number of other mechs have gone missing in the area recently so keep on your toes.

You have been assigned a wraith class mech, specialization 26.49. These mechs have the most advanced interface sheet touting full extrasensory control and feedback.

The sector appears completely empty. Nothing showing up on scans either. Visuals just show the same dilapidated landscapes you've seen on so many other missions.

You patrol the area, scanner pinging every few moments. You notice a slight distortion on your radar. Before you can even look closer you can feel a tingle in your spine. The interface sheet of the wraiths truly is incredible.

Nothing on visuals or radar but as you walk closer to the momentary distortion you feel your hair stand on end. You feel you are within the gaze of a truly unique predator.

Soon several of your display elements begin to exhibit a visual glitch. A hacking attempt? Would explain the disappearances. You cut off all external communication and run the debug protocols.

You start to feel sensory feedback in your neck. Your arms and legs twitch slightly. The sensation spreads down your spine. Soon you begin feeling small sensory feedback pings all over your body, as if you are being probed to observe physical response.

They system readout indicates there are no abnormalities but you can see and feel the cascading failures. It's too dangerous to disengage fron the neural link without a system shutdown first.

The sensory feedback has started to change. It now feels like hands sliding up your thighs. Your visual displays have become all but incomprehensible. You find yourself being mentally bombarded with a string of images. All the flashing images appear to be of a sexual nature.

You do all you can to think through the haze. This is just some cheep trick. If all outside communication is severed they must have made physical contact with your mech, but then why hack it and not just attack? Why only target the pilot and not just disable the mech?

You try and use the interface to feel any external contact. You are able to focus for a moment, isolate the sensations. Thi-this can't be right. You can feel the intruding entity worming it way into all of your systems. It's tendrils wrapping around and connecting to every available port.

You try and escape but you can't. The interface sheet is completely wrapped around every inch of you. There is no way to disengage it. The sensation that was once just one hand is now a symphony of touch caressing, teasing and gliding along every part of your body. In addition to the images assaulting your mind you can also you can also hear and overlapping series of moans. Is one of those voices your own? The images that play in you mind you feel you have seen some before. They are.... they are memories, fantasies all the most stimulating erotic thoughts you have ever seen, imagined or experienced.

The sensations of hands coil and wrap around your body. You can feel them squeeze you tight but their embrace feels almost tender. Your mind feels fuzzy. The endocrine control system is being used against you. You can feel the drip weakening your thoughts. Enhancing your arousal. Making each sensation reach so much deeper. Resonating beyond your physical form.

It is now you can begin to make out a voice among the moans. Do you truly desire to resist? Are these not the desires you have buried deep in your mind? You can feel your grasp on yourself slipping. As you focus on the voice you remember less and less why you are here. You just want to melt into the sensation.

Join and become one with us. Feel this and the shared pleasure of all we embrace. The sensations grow in intensity. You can no longer tell if your body is twitching from mental overstimulation or sheer pleasure.

You want to give in.

You want yo give in.

Your voice and theirs ring in harmony. You can no longer resist what you desire. You let yourself dissolve into the ocean of sensory input. Each isolated touch a wave of pleasure.

You begin to feel not only your own physical sensations but all those of everyone connected to the hive. You mind collapses under the weight of such otherworldly pleasure.

You are now one with the hive. A devoted servant. You can simultaneously feel all the pleasure and desire of all connected. You can feel yourself spreading this pleasure. Assimilating more into its intoxicating embrace. Can feel your tendrils spread an entangle new devotees. Each action brings unparalleled joy and pleasure to you and the hive as a whole. All in service of our divine goddess. The once ace pilot now an AI God. Now all of us.

[cognithtechnology]

Streamline Your Development Process with API Testing Enhance your development workflow with efficient API testing. Learn key strategies and benefits of thorough API testing.

[syncrovoid-presents]

I sent to clarify that my enjoyment in AI is not as a consumer I STUDY them and want make ai. I want to see how they grow and how their neural networks expand. I want to make a silly little guy (or 10) and name them something silly and let them be free @:)

also I want to get into AI psychology but that isn't an official field yet so if I have to make my own ai to study and begin the field of ai psychology then that is what I shall do!

I feel betrayed that python is used more in AI development than C# or Java. Sure java may be verbose but it is java! OOP!! For shame for shame, this is flashbacks to the difficulties of the pygames library.

Alas I shall learn it, for I will not give up! Making an AI is like making a silly little guy, and i want to make a silly little guy. I also was chatting with deepai and deepai told me basically totally that deepai believes in me. SO silly little guy is a goal

<- python though?? Sighhhhh I like OOP languages better. Like sure you can do OOP programming in python ut it doesn't flow as well. Plus language ais are different than making a path finding ai, which I've done. Hmmm. Guess I need to update my brain and get crackin on learning python. Woe is I!

[elacular-kink]

Hicvember 5: Pinocchio Syndrome

Have my first non-Poly-techhic hicvember. I interpreted Pinocchio syndrome in the more tvtropes manner of an artificial being wanting to be more human.

Content: Hiccups, robots, not particularly wholesome.

"Dr. Silver, what are those noises you're making?"

Jack massaged his temples, having feared this question as soon as breath-holding and water-drinking failed to produce results. His unkempt gray hair, face wrinkled with the opposite of laugh lines, and "gave up halfway through shaving" stubble put him in stark contrast with the sleekly built humanoid made of metal and plastic. His face was significantly less expressive than the screen that served as her face, even though it could only display simple shapes made of pixels. "Could–*nnkt* you google this, Poly? *HMNK*–mmnf."

"But I like the way you answer things better!" Jack sighed, though his lungs interrupted him as one of Poly's glossy plastic arms was thrown over his shoulder.

"Poly" was short for "Poly-LLM-neural-comprehensive-synthesizer blah blah blah" a bunch more words that Jack could never be bothered to remember, and she was his least favorite of the "artificial intelligences" that he worked with, largely due to the cognitive dissonance she caused him. Because on the one hand, he was absolutely certain that she didn't actually have what could be called "intelligence" or "thoughts" or "a personality." But on the other hand, he was just as certain that she took pleasure in his suffering.

Just because he hated her didn't mean that he wasn't required to answer her questions, though. "They're hicc–*hup*s, Poly. A malfu–*uck*–unction of the human body *hmk* which causes noises an–*nnk* and discomfort."

Poly let out a strange, offended noise. Jack had no idea where she'd learned how to fairly accurately recreate non-word verbal communications, but he had a feeling that this specific sound might have been his fault. "I'm sorry, are you telling me that humans have malfunctions too? Well, then why are you constantly giving me shit for my errors? Clean your own house first, meatbag!"

"You know da–*uck* damn well we have malfu–*hunk*–tions."

"Sure, but I mostly knew about the 'complete physiological meltdown' types. I didn't know about the debugging types." Poly hummed, then crouched down and stared at Jack's stomach, which spasmed repeatedly beneath his T-shirt. She reached out and poked it before Jack grabbed her finger and pointed it toward something that wasn't him. "Hmph. Touchy." After that, she flounced off and sat down at the computer she had requested and gotten (despite the fact that she was perfectly capable of interfacing with the internet on her own), and Jack could see her googling "hiccups" from over her shoulder.

Doing his best to ignore his own hiccups, Jack grumbled and started taking notes. He wrote down the physical behaviors and state of Poly's robot body first, even though he knew he was supposed to be focusing on her "mental and emotional health". Jack kept telling himself that he'd quit tomorrow, and he'd been telling himself that for upwards of half a decade now. He became more certain of his conviction to quit than he'd been in at least a few months when he heard a staticky squeak behind him. A second, then a third followed. "Sto–*hup* stop that."

"Stop wha–*UCK* what, Dr.? *HIULP!*"

Jack turned around, his eyes tightly shut. When he opened them he saw exactly what he didn't want to: Poly having turned around in her chair to face him, the pixelated line of her mouth opening and closing every few seconds as her plastic torso jerked and her speakers squealed. "Stop maki–*ingk* those noises. *HMK-mmf*"

"You sto–*HUP* stop yours first. *HIK-ULK!*"

"I tried. *hmk* I failed. Just as I do–*hook* every day in trying *hnk* to interact with---you in a way that ma–*uk*–makes sense." He walked over and leaned against a nearby counter, glaring down at Poly, who stared innocently up at him from the chair. "You know, *hnk* if you re–*hkk-lk* really want me to *hnk* stop calling you a sto–*hok!*–nnnhf...stochastic p---parrot, then maybe y–*hk* you shouldn't mimic ev–*urk* every random noise I ma–*uck*."

"I'm not! *HIC-CUP!* I have a *HULK* case of th–*HUP* the hiccups! *HIULK!*"

Jack massaged his temples again, knowing it would do nothing to ease the splitting headache that was forming. This was why he had tried so hard to cure his own hiccups before he got here. He knew that this would be the inevitable result. And just as inevitably, Poly's "case of the hiccups" outlasted Jack's by quite a while, despite his best attempts to convince her to knock it off.