#ascii > test

[transienttest2]

this post is tagged "ascii [ascii character62] test" (note the spaces).

[claire-starsword]

The track listing on my Shining Force II post was derived by The 16 Bit Audiophile Project. A post regarding the sound playback hack for Shining Force II indicated that the songs were assigned dialogue lines in the Japanese version where there is a sound test mode. I have not seen Takenouchi credited on a Shining Force II OST other than the symphonic suite. The symphonic suite is available on Soulseek and has scans if you're interested. :)

Thanks, I had no clue about the JP-only Sound Test!

[mistfunk]

Mistigram: a #blockASCII reworking of the M20 logo drawn for our use by long fellow traveller mattmatthew of blocktronics, to christen the inaugural test of ConsoleJockey's automated Mistigram syndicator in this, the month of our 30th anniversary celebration.

[pillowspace]

I had two programming apps on my 3DS and would create simple programs when I was about 9 or 10. I can't say you're wrong

Annoys me badly that I only have a phone and can't develop games because sometimes I'll have a good idea for one and it will just rotate in my head so hard

[commodorez]

Alright Nova 1200, your turn. Let's figure out why the /CONRQ signal isn't happy...

Except for some reason it works now. So I put the front panel cover back on, gave it a bit of a rest to make sure it wasn't a temperature issue, and tested again and it's still fine.

Next problem: test the serial functionality with two programs:

One that spits out ASCII barf [check] One that echos whatever was typed into the terminal [check]

Well, both pass, so now it's time for the bootstrap loader, followed by the binary loader. Those seem to work. Let's try 095-000036-01 Nova 1200 Logic Test from 1970 to 1974. They built it for exactly this purpose.

Passes the first check aaaaand... fails the second. Okay, let's work with that. Later, serial tests stopped working too. Great...

See that blue line spiking? That's the input that triggers things, and it's subtle analog bullshit, which is then turned into clean digital high/low. It's very unorthodox compared to how we do things today.

So this turned into a more complicated issue, or set of issues. The front panel started getting mad again (/CONRQ again). And after studying the circuitry for awhile, I deduced it was from the 5V rail being below the safe threshold for the logic to work. The 5V rail delivers at most 12A to this computer per the specs, which is for a few hundred logic IC's (lamps and core memory use different voltage rails). That means if it isn't adjusted right, the voltage sags pretty badly when you get far enough away from the PSU.

That's on the front panel. Not ideal. It's not much different on the CPU board. The problem is that if I boost the 5V adjustment trimpot on the PSU to reasonable levels, the -5V and +12V rails climb.

-5V isn't so much of an issue, not much needs that to work. 12V is used by only 2 things, neither of which is logic: the front panel lamps (which are rated for safe operation between 11-17V per Data General), and the industrial Noctua fans in the PSU chassis.

When 5V is happy, 12V is more like 13.5V, which is liable to degrade and eventually destroy those fans. So I built this little thing to protect those fans: a pair of diodes to drop the voltage down just below 12V. We don't need to worry about the lamps, they're fine

But that fixed the PSU issue, which fixed the /CONRQ issue.

[thefirstknife]

Man. This week.

There's a few things I want to point out again that are really cool and the first is that once you finish the story and get the radio and the lore tab and everything, speak to Failsafe again. She'll give you an "epilogue" quest which requires you to find secret stuff in Encore. There's 8 of them, and all of them are voice recordings of Maya and Chioma from when they had a normal happy life. And they're all absolutely incredible and devastating. They're not uploaded anywhere that I can find yet, I'll try and put them here later with transcripts unless people put uploads online.

These are really important to me because they keep reiterating that there was a time (and Maya) that used to be fine. It's the woman Chioma loved and her transformation into the Conductor is almost an anomaly of only one of the Mayas. The others, even other copies from the Vex Network seem to be different and fine.

Anyway, we tried to find this Maya's Chioma, but it turned out Maya already tested her and rejected her, thus killing the one she was looking for. But I really like how it's done because Chioma wasn't just helplessly clueless in this; she had her own agency and made her own decision upon realising what Maya had become. More under:

So that's okay. Dies.

But the thing is that this is true only for this one Maya, the Conductor one. Other Mayas and other Chiomas are fine. This is really interesting in the dialogue you get for the last chest:

This is the 87th copy of Maya who is looking for 50th Chioma copy. This is fascinating because it means that .87 Maya lost her Chioma and found another. Multiple others even! She mentions how she's become a widow many times over, which means she bonded with multiple other Chiomas just fine. And now she's looking for the .50 one, hoping she's still out there.

And some of them are still out there! There's more Mayas and Chiomas still in the Network and at the end in the lore tab, it's discussed is that Osiris and Saint are going through the Vex Network looking for them.

But before that, our confrontation with the Conductor! She does manage to control us, but Saint breaks free. And he said the line!

He's the only one ever actually. But the thing is, we didn't exactly kill her. She went back into the Network and she took the Echo with her. So that's probably not good overall.

There's a really nice message after from Failsafe who doesn't really want to say goodbye, but also realises that she doesn't have to rely on other people to feel like there's a point in going on. She can go on for herself. Which definitely didn't make me cry (lie).

And Saint also confirms after that Maya is still around:

And Saint being Saint:

Also from Ikora from the radio message, really important stuff:

Lore tab is really cool as well! Some absolutely hilarious bits with Nimbus and Failsafe and I need more interactions between them now:

She shrewdly routed the message alerts to her external display screen. "Nimbus, buddy—" she began. "Hint taken," Nimbus grinned, spreading their huge hands wide. "I'll let you get back to your whole being-a-ship thing. If you see Osiris, tell him Jisu Calerondo is looking for an interview about his sick bird hat. Or, no, say that the CloudArk is losing integrity and only the biorhythms from, like, a truly old and decrepit dude will save it!" "I'm on it," Failsafe said, and pushed an ASCII image of a thumbs-up to her display. Nimbus laughed and gave Failsafe two enormous finger guns as they transmatted out.

Failsafe's reaction to Eido sending her a message as well:

She puzzled next over a message from House Light Scribe Eido, as it did not appear to contain any discernable requests. She marked it for non-urgent reply and sorted it into one of her new subfolders: SOCIALIZATION (PLATONIC).

Then there's Osiris with the information that he and Saint are looking through the Network for Maya and the Echo. It's a really good one for closing the episode.

But as I said, there's still an epilogue quest which requires going into Encore again and finding "anomalies" which contain recordings between Maya and Chioma that killed me in one hit.

There's also a secret triumph this week that can be unlocked and it relates to the Whisper portal, but it's a secret so if you don't want to google around, basically: load into expert Encore and head to the Whisper portal location. The door will be closed, but there should be the Whisper exotic perk icon above it. If you equip Whisper, the door will open and then you can go through the portal which will be active. Once you do that, you'll have 35 minutes to complete Encore on expert to unlock the secret triumph and get an emblem we were wondering about last week. No need to do the extra puzzles or anything, just complete the mission.

I really enjoyed this episode overall as it hit all the right interests for me. Really good cast, loved the return of Failsafe, absolutely died over everything in regards to Saint and Osiris and how close and physical they were allowed to be on screen so much (which is, btw, the first time they've done so. We've had lore tabs and the kiss cutscene and all, but Saint and Osiris have never actually been together on screen in this way before, as all previous appearances was Savathun or them just standing next each other or just them together on comms; the level of physicality and contact and all the stuff they talked about is so important as we've not really had anything like it before).

Absolutely incredible that we got to see Maya and Chioma, what they looked like and all their interactions, especially the epilogue ones where we got a glimpse into how their life was before everything fell apart. And with the knowledge that there's more of them in the Network, I will continue to believe that somewhere out there they're still living a happy life. And Ikora agrees:

Getting to hear these two together on comms and getting so many updates and information about them was an incredible treat. They've been such foundational and important characters to Destiny since the start. We knew about their relationship since the beginning, even back in the day when queer content was really, essentially, not allowed and pushed under the rug. But Maya and Chioma were there and we got to learn so much more about them. A lot of it really heartbreaking, but a lot of it also really nice.

I hope Maya and her Echo will continue being in the story in some way in the future. There's also a question of her Vex Collective as well and what she's done to the Vex in general, but also specifically the Precursors. I wonder if we'll get more into that eventually when the Vex are back as a threat (because in a way, they have to).

[s-lycopersicum]

That post got me thinking about programming, and that maybe I should talk about one that I really had fun writing recently, and that I'm kinda proud of, so here it goes!

So, in my computer experiments and stuff like that, I often have to write scripts that process entries in various stages. For example, I had a thing where it read a list of image urls and downloaded, compressed, extracted some metadata, and saved them to disk.

That sort of process can be decomposed in various stages which, and that's the important part, can be run independently. That would massively speed up the task, but setting up the code infrastructure for that every time I needed it would be cumbersome. Which is why I wrote a little library to do it for me!

That gif is a bit fast, so here's what it looks like when it's all done:

This is from a test I wrote for the library. It simulates running a set of items through 4 different processes (which I named production lines), each with their own stages and filters.

Each line with a progress bar is a stage in the process. If you follow the traces on the left side, you can visualize how the element enter the 4 production lines on one side, and are collected on the other. The stages I wrote for the test are simple operations, but are written to simulate real world delay and errors.

To set up the processes, I do practically nothing. Just initialize the production line structure and connect the stages together, and that's it! All the work of setting up the async tasks, sending the entries from each stage to the next, filtering, error logging, even the little ascii diagram, all that happens automatically! And all that functionality packed into one data structure!

I feel like trying to explain how it does all that (and why having built it myself makes me proud) would make it harder to believe that I actually had fun doing it. I mean, it involved reading a lot of code from high profile open source projects, studying aspects of the language I had never played with (got really deep into generics with this one), and I can't really explain how I really enjoyed doing all that.

I don't know, I feel like I lost the point of what I was trying to say. Hm, I guess this feeling are harder to pin down that I expected.

[chaeshortcake]

The Ultimate List of Junk Journal Supplies

꒰ ⪩ 📜 ⪨  ꒱   Paper and Patterns :

- Washi Tape

- Music sheets

- Sticky notes

- Napkins

- Openwork napkins

- Newspaper scraps

- Old book pages ( note: you can also use old books as a base for your junk journal )

- Pages from differently lined / colored notebooks

- Crumpled paper

- Ripped paper

- Coloured paper

- Decorative paper

- Gift / Bouquet wraps

- Fabric scraps

- Foil

- Colouring books

- Burnt paper

- Coffee soaked / stained paper

꒰ ⪩ 🖨️ ⪨  ꒱   Printouts :

- Your digital art

- Picrew avatars

- Paintings or Vinyls

- Chat screens

- Album covers

- Pinterest boards

- Spotify codes

- Sticker sheets

- Screenshots

- ASCII / Kaomoji

- Personality test results

- Vents / Rants from your notes app

- Whispers you liked or made

- Conversations you never sent

- Voice message waveforms

- Songs waveforms

- Tier Lists

꒰ ⪩ 🎠 ⪨  ꒱   Life Events :

- Business cards / Invitations

- Checks/receipts from stores (note: some may fade over time)

- To-do lists

- Shopping Lists

- Cookie messages

- Maps / Travel brochure cutouts

- Letters / Envelopes

- Newspaper articles

- Cut-out dates / Stamp dates

- Polaroids / Photobooth photos

- Your grades / Teacher's note (if not needed elsewhere)

- Verses from religious texts (handwritten or printed)

- Shopping or luggage tags

- Travel clippings

- Food/snack packaging

- Foil packaging from pills

- Price tags / Labels

- Lottery tickets / Coupons

- Clothes or shoe badges

- Recipes

- Postcards and envelopes

- Tickets

- Greeting cards

- Friend's handwriting / notes

- Childhood drawings

- Wishlists

- Expired id / student etc cards

- Expired SIM cards

꒰ ⪩ 🎀 ⪨  ꒱   Decorations & Fillers :

- Magazine/poster cutouts

- Magazine letters

- Crossword / sudoku cutouts

- Origami

- Tea / Sugar bags or sachets

- Daily / weekly etc. horoscopes

- Daily / weekly etc. affirmations

- Song lyrics / Poems / Quotes / Essays

- Calendar pages

- Old/expired photo film

- QR codes / Barcodes ( note: QRcodes can be interactive )

- Sketches / Small drawings

- Hand / Fingerprints

- Lip imprints

- Small flat crochet or knit decorations

- Children's tattoo stickers (temporary tattoos)

- Ribbons / Lace / Decorative threads

- Glitter / Rhinestones

- Googly eyes

- Hole-punched stars / flowers

- Cut-out hearts / stars

- Stickers

- Fruit stickers

- Eastern egg decorations (wraps, stickers, etc.)

- That circle cardboard from shoe boxes

- Broken CD pieces

- Candy wrappers

- Playing cards

- Can openers

- Used postage stamps

- Interactive windows/curtains (flip open surprises!)

- Angel numbers

- Puzzle pieces

- Tarot cards

- Flower prints

꒰ ⪩ 🌱 ⪨  ꒱   Nature :

- Pressed flowers

- Fall leaves / Pine spikes

- Tree bark

- Feathers ( artificial )

- Dried moss

꒰ ⪩ 💻 ⪨  ꒱  Media :

- K-pop photocards / Cutouts from albums

- Characters from your favorite shows

꒰ ⪩ 🔨 ⪨  ꒱   Other useful items :

- Thick 2-sided tape (adds dimension)

- Felt and Foamiran

- Decorative threads

- Buttons / Beads / Letter beads

- Pins / Paper clips

- Zipper bags

- Markers

- Stamps

- Perfumes

Dividers by : @huraxy

[forcefem-octahedron]

oh wow what a cool looking die whys there a b on it i wonder what that means *rolls you gently*

Kunzie pulls out her phone and speaks to her informant. "hey, Steph~... yeah, i understand it's taken a few days of testing... glad to hear it!... of course, what's the isekai brane number? ... thank you."

Kunzie manifests a portal and leads you through it. you observe your surroundings -- a nearly empty void, broken mainly by a few paragraphs of text here and there. you notice that you've been turned into an ASCII art representation of yourself.

a text cursor jumps onto you and selects you. it replaces your clothes with frilly_magical_girl_outfit.txt -- a dress with petal-shaped sleeves and skirt, a pair of gloves with beaded bracelets around the wrists, a circular pendant, and an elf-like hat and shoes. it colors the text constituting your new outfit in various shades of pink -- except the pendant and bracelets, which instead become rainbow. to complete the look, it edits your hair to be a crimson color and to have two buns, and it animeifies your face.

you walk back through the portal, whereupon the ASCII art style demanifests from your body. now in high fidelity, you look down at yourself and recognize what has happened to you -- you have been dressed to resemble Doremi Harukaze.

a nondescript anime girl exits shortly thereafter. Kunzie acknowledges her, then speaks into her phone. "alright, Steph, note this down. the rescue mission is successful. moreover, this appears to a good brane for forcefem. promising to visit in the future... excellent. bye~"

[inspired in part by this post by @luetta]

[techav]

As I've mentioned before, the ultimate goal for my 68030 homebrew systems is to run a proper multi-user operating system. Some flavor of System V or BSD or Linux. I am not there yet. There is still so much I need to learn about programming in general and the intricacies of bringing up one of those systems, plus my hardware does not yet have the ability to support multiple users.

I've toyed with several ideas as to how to get the hardware to support multiple users, but ultimately decided to leverage what I have already. I have a fully-functional modular card-based system. I can easily build new cards to add the functionally I need. And to make development and debugging easier, I can make each card simple, dedicated to a single function.

The catch is I've already run into some stability issues putting everything on the main CPU bus. So what I really need is some kind of buffered peripheral bus I can use for developing the new I/O cards I'll need.

So that's where I started — a new 8-bit I/O bus card that properly buffers the data and address signals, breaks out some handy I/O select signals, and generates the appropriate bus cycle acknowledge signal with selectable wait states.

It wasn't without its problems of course. I made a few mistakes with the wait state generator and had to bodge a few signals.

With my new expansion bus apparently working I could set out on what I had really come here for — a quad serial port card.

I have it in my head that I would really like to run up to eight user terminals on this system. Two of these cards would get me to that point, but four is a good place to start.

I forgot to include the necessary UART clock in the schematic before laying out the board, so I had to deadbug one. I'm on a roll already with this project, I can tell.

So I get it all wired up, I fire up BASIC, attach a terminal to the first serial port, and get to testing.

Nothing comes across.

Step-by-step with the oscilloscope and logic analyzer, I verify my I/O select from the expansion bus card is working, the I/O block select on the UART card is working, the individual UART selects are working. I can even see the transmitted serial data coming out of the UART chip and through the RS-232 level shifter.

But nothing is showing up in the terminal.

I've got the terminal set for 9600bps, I've got my UART configured for 9600bps, but nothing comes across.

I did note something strange on the oscilloscope though. I could fairly easily lock onto the signal coming out of my new serial card, but the received data from the terminal wasn't showing up right. The received data just seemed so much faster than it should be.

Or maybe my card was slower than it should be.

Looking at the time division markings on the oscilloscope, it looked like each bit transmitted was around ... 1.25ms. Huh. 9600bps should be more like 0.1ms. This looks something more like 800bps.

I set the terminal for 800bps and got something, but it wasn't anything coherent, it was just garbage. I wrote a quick BASIC program to sweep through the UART baud rate generator's clock divider setting and output a string of number 5 for each setting until I got a string of 5s displaying on the terminal.

So then I tried sending "HELLORLD".

I got back "IEMMOSME".

No matter what I changed, I couldn't get anything more coherent than that. It was at least the right number of characters, and some of them were even right. It's just that some of them were ... off ... by one.

A quick review of the ASCII chart confirmed the problem.

'H' is hex 0x48, but 'I' is 0x49. 'E' is 0x45, but was coming across correctly.

... I have a stuck bit.

The lowest-order bit on my expansion bus is stuck high. That's why I wasn't seeing any coherent data on the terminal, and it also explains why I had to go hunting for a non-standard baud rate. The baud rate generator uses a 16-bit divisor to divide the input clock to the baud rate. When I tried to set the divisor to 0x0018 for 9600bps, it was getting set to 0x0118 — a difference of 256.

Another quick BASIC program to output the ASCII chart confirmed this was indeed the problem.

Each printed character was doubled, and every other one was missing.

That sounds like it could be a solder bridge. The UART chip has its D0 pin right beside a power input pin. A quick probe with the multimeter ruled that out.

Perhaps the oscilloscope would provide some insight.

The oscilloscope just raised more questions.

Not just D0, but actually several data bus pins would immediately shoot up to +5V as soon as the expansion bus card was selected. As far as the scope was concerned, it was an immediate transition from low to high (it looked no different even at the smallest timescale my scope can handle). If the UART was latching its input data within the first third of that waveform then it certainly could have seen a logic 1, but it doesn't make sense why only the one data pin would be reading high.

I thought maybe it could just be a bad bus transceiver. The 74HCT245 I had installed was old and a little slow for the job anyway, so I swapped it out for a newer & much faster 74ACT245.

And nothing changed.

It's possible the problem could be related to the expansion bus being left floating between accesses. I tacked on a resistor network to pull the bus down to ground when not active.

And nothing changed.

Well ... almost nothing.

This was right about the time that I noticed that while I was still getting the odd waveform on the scope, the output from the terminal was correct. It was no longer acting like I had a stuck bit and I was getting every letter.

Until I removed the scope probe.

Too much stray capacitance, maybe? That waveform does certainly look like a capacitor discharge curve.

I had used a ribbon cable I had laying around to for my expansion bus. It was long enough to support a few cards, but certainly not excessively so (not for these speeds at least). It was worth trying though. I swapped out the ribbon cable for one that was just barely long enough to connect the two cars.

And finally it worked.

Not only was I able to print the entire ASCII set, I could program the baud rate generator to any value I wanted and it worked as expected.

That was a weird one, and I'm still not sure what exactly happened. But I'm glad to have it working now. With my hardware confirmed working I can focus on software for it.

I've started writing a crude multi-user operating system of sorts. It's just enough to support cooperative multitasking for multiple terminals running BASIC simultaneously. It may not be System V or BSD or Linux, but I still think it would be pretty darn cool to have a line of terminals all wired up to this one machine, each running their own instance of BASIC.

[liquidcrystalsky]

im mad cuz i learned something stupid, that everything does wrong, but very much Doesn't matter because it's purely visual that a very few amount of people will ever care about.

think of just a pure ascii text file. It's common practice to add a newline to the end of a file, so that if another file is added onto it, the first line of the file will be on the line AFTER the last line rather than being smushed into the same line.

this makes sense, and most text editors do this. See this test file before and after hitting save, a line 2 appears.

this behaviour is correct! text files or source files or anything should end with a newline and a text editor adding it automatically is a good thing.

A newline is signified by the ascii "LF" (Line Feed), and while LF originally meant to advance a typewriter to the next line, the definition of a line by POSIX states that the newline character is part of the line itself. It is not a separator between lines, but a line terminator, referred to as End of Line (EOL)

meaning while the text editor should be adding a EOL character to the end of the file, it should not be displaying that there is a extra line at the end, as it's the end of a line, not the start of a new one.

vim, emacs, gedit are basically the only text editors which do this correctly. You can see the EOL symbol displayed but a second line does not appear underneath.

you can make an argument this be behaviour is correct on windows however, because the newline character on windows is ascii "CR LF" (Carriage Return + Line Feed) for compatibility with teletypewriters, where a CR returns it to the beginning of the line, and LF moves the line down, so it advances to an extra line.

but also all these programs even the ones specifically made for windows, specifically call them line ENDINGS.

vscode, kate, notepad++, all of them refer to it as EOL however they display it as a separator rather than a terminator. vscode is MADE by microsoft and they still call it an EOL. get real.

[transienttest2]

this post is tagged "ascii test" (two space characters).

[deepdreamnights]

Music Monday - This one puts a smile on my face every time.

This one takes maybe some explaining.

Okay, so I was trying to get something with cowbell, which Suno takes as meaning "country" apparently, despite that not being the intent.

Moreover, this wasn't meant to be a full song, I was doing tests to see which ASCII symbols produced notes, which is a way to control (to a degree) the non-lyrical content of suno gens. In this case I tested this:

˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· ˜ ‚„·· ˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· °¶ ¯ ˜ ‘ º˜º ˜ ‘ ˜˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜ ˜ ˜ ‘ ˜ ˜¯ ¯ ˜ ‘ º˜º ˜ ‘ ˜˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜ ˜ ˜ ‘ ˜ ˜¯ ‡ ~ ˜ ‚„·· ˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· ˜ ‚„·· ˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· ° ¯ ˜ ‘ º˜º ˜ ‘ ˜˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜ ˜ ˜ ‘ ˜ ˜¯ ¯ ˜ ‘ º˜º ˜ ‘ ˜˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜ ˜ ˜ ‘ ˜ ˜¯ - ~ ˜ ‚„·· ˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· ˜ ‚„·· ˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· ° ¯ ˜ ‘ º˜º ˜ ‘ ˜˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜ ˜ ˜ ‘ ˜ ˜¯ ¯ ˜ ‘ º˜º ˜ ‘ ˜˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜ ˜ ˜ ‘ ˜ ˜¯ ~ " ~ ˜ ‚„·· ˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· ˜ ‚„·· ˜ ¸ ˜˜ ˜ ˜ ¸ ˜˜˜ ‘ ˜˜˜ „ ˜ ‘ º „ ˜ ‘˜ • ¸ ˜ ˜˜ • ¸ ˜˜ ‘ ˜º „ º ‚¸ ·· ° ¯ ˜ ‘ º˜º ˜ ‘ ˜˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜˜ ˜ ‘ ˜ ˜ ˜

And some part of that was read, when combined with country as "huk-a-ruk, buck-a-roo" and similar such sounds. For reasons difficult to explain, the song makes me laugh pretty much every time.

This is probably partially because of the faux emotion the simulated voice puts behind utterly nonsensical sounds, and partially because I imagine the song being sung by a band of capybaras in cowboy hats.

[why-is-it-always-autumn]

Currently obsessed with the idea of Homestuck characters signing up for DNA Ancestry tests pre-game.

Dr. Roxy Lalonde has giant gaps in her DNA that should be a problem but its somehow only junk DNA that isnt actually expressed in humans missing and she's completely fine.

Dave Strider does an ironically sincere tearjerker interview about wanting to find his birth parents and then his ethnicity comes back as "Alternian????" because his genetics are closer to Betty Crocker than anyone else on the planet (other than Rose, but her sample blacked out the scanner when they tried to analyze it)

Jude Harley's DNA is 50% whatever Anna Claire was 50% slime

Dirk Strider's genetic code somehow includes an ascii drawing of a horse wearing sunglasses

[treble-cleff]

I’m gettign back into my cookie run phase hel

ANYWAYS doodles wahoo yayayaayayayay🎉🎉🎉🎉🎉🎉🎉 in a new artstyle I’m testing out too :3

(ocs in 2nd and 3rd images belong to my friends @ascii-malware and @vnillatree !! :] (hope yall don’t mind being tagged!!))

[sztupy]

Aimbots have been the bane of many a shooter fan's existence—and indeed even threw Apex Legends' anti-cheat software for a loop—so you can understand why Ricochet would have cheats like this in its sights. What is a lot less straightforward to understand is how simply typing the words 'aim bot' and sending them to another player could get them banned.

Vizor explained that Ricochet uses a list of hardcoded strings of text to detect cheaters and that they then exploited this to ban innocent players by simply sending one of these strings via an in-game whisper. To test the exploit the day they found it, they sent an in-game message containing one of these strings to themselves and promptly got banned.

Vizor elaborates, "I realized that Ricochet anti-cheat was likely scanning players’ devices for strings to determine who was a cheater or not. This is fairly normal to do but scanning this much memory space with just an ASCII string and banning off of that is extremely prone to false positives."

Arcpálma rovat