stkptr

[stkptr]

"Closed species" aka yeah I made a furry design, but I'm extra special. You put a wig on an owl and gave it cat ears. You replaced a bunnies midsection with an aquarium. You drew a dino gave it a manipedi and some lipfiller. You put horns on a penguin and gave it a BBL. Chill the fuck out.

--

[stkptr]

"Correct," even "technically," cannot exist in a vacuum. What follows is a seventeen page rant on the casual permeation of prescriptivism in western culture.

Do you spell it “donut” instead of the technically correct spelling “doughnut”?

[stkptr]

Here's a Jungle/atmospheric drum and bass one.

I don't know who to tag so I won't.

Task: Pick a song for every letter in your tumblr-URL. Tag at least as many people as there are letters in your URL.

@bugwizard4lyfe thank you for tagging me! the post was so long it was glitching my phone and I couldn't rb it, so I'm making a new post to answer.

Overwhelmed by Royal & The Serpent

Cinderella Boy by Saucy Dog

The Spark by Kabin Crew

Apt. by Rosé and Bruno Mars

Let It Go sung by Idina Menzel

Are You Satisfied? by Marina and the Diamonds

Like Jennie by Jennie

Call Me By Your Name by Lil Nas X

Heat Waves by Glass Animals

Everybody Wants to Rule The World by Tears For Fears

Mada Minu Ashita Ni by Asian Kung-Fu Generation

Imposter Syndrome by Sidney Gish

Slumber Party by Ashnikko

Teenagers by My Chemical Romance

@hummingbird-hunter @sasukeprime @myheadgoesaround @ceeceelemons @moinsbienquekaworu @lukahhhhhhhh @meggettes @sqrt-73 @ikeberry @xxx-darthgenderfucker-69-xxx @knyfe-jpg @faggy-boy @yutamayo @daddylovesswords

[stkptr]

Great job! Hope you enjoy it, it's a good stripped down Android with mostly sane (but bare) defaults. You'll probably want to install a custom keyboard, that sort of thing.

Paging @stkptr. I looked further into GrapheneOS (after the Pewdiepie video). The Web Installer is so easy to use, unlike what I had heard about booting an OS yourself to a phone.

Enable OEM in dev mode, boot your phone into Fastboot mode, click three buttons in the browser, and that's it! What the heck.

So yeah, goodbye Google weird pixel OS \o/

I may be in need of some reading to fix my irrational fear of bricking a mobile phone...

[stkptr]

With this knowledge, you can create your own media violation images.

Tumblr Media Violation Images (Font Identification)

Tumblr has a number of placeholder images it uses when an image is removed. The most famous, by far, is the community guideline violation image. "This content has been removed for violating Tumblr's Community Guidelines."

Most of you have likely seen this image, if not in its intended place, by someone using it for the aesthetic. Did you know that this is actually an old variant, and there was at least one even older variant?

These are all the iterations I could find for this specific media violation image, the 500x375 pixel Community Guidelines violation image, in order. All of these files are called community_guidelines_v1_500.png and the versions can be found on the Internet Archive. The newest version is also called user_guidelines_v1_500.png.

The transition from the first variant to the second happened sometime on January 3rd, 2019, specifically between 16:52 (last) and 23:30 (first) GMT. The transition from the second to the third was on July 16th, 2024 between 14:03 (last) and 14:58 (first) GMT. Differing resolutions of this image seem to have been replaced at various different times.

The first iteration's gray background style is consistent with the other media violation images available at that time. Each had a custom desaturated color graphic in the center of the image, with the text of the image as a centered subtitle. The current style is made up of a single chunk of left-justified text over several lines in the upper left corner on a dark blue background. The start of the text as well as the final period is colored according to a scheme; blue for community guidelines, pink for copyright, orange for privacy. The colored text is for the preamble "this content has been removed for" with the reason being in white. The "all" violation does not match this format exactly, instead its old iteration is simply text, and its new iteration does not have colored text.

The community guidelines violation image is the only one with three variants. All of the others only have two.

copyright_v1_400.png

privacy_v1_500.png

all_v1_100.png

The fonts

Notably, if you look very closely at the new variants you can see that almost all of them have their i-dots (tittles) off center, shifted to the left, with the right edge aligned with the right edge of the i body. Additionally, in all of the images the apostrophes are relatively ornate for the otherwise grotesque sans-serif typeface. The only new style image which does not have the tittles off-center is the newest variant of the community guidelines image.

The original images use a Helvetica typeface, likely Helvetica Neue. However, the text is not simply typed out in Helvetica, the apostrophes seemingly have all been manually replaced with the comma character. I suspect manual replacement since I do not believe Helvetica to have a style option for replacing the apostrophe with a comma.

The new variants use a custom typeface called Favorit-Tumblr. Similarly to the original variants, the apostrophes have been replaced with commas. I think the off-centered tittles lend credence to the idea that the apostrophes were manually replaced.

Sources

All of the images were taken from the Internet Archive. A full list of all indexed media violation images can be found at this link, which includes various resolutions of each. The exact change times were found using a manual binary search in a few minutes.

[stkptr]

Tumblr Media Violation Images (Font Identification)

Tumblr has a number of placeholder images it uses when an image is removed. The most famous, by far, is the community guideline violation image. "This content has been removed for violating Tumblr's Community Guidelines."

Most of you have likely seen this image, if not in its intended place, by someone using it for the aesthetic. Did you know that this is actually an old variant, and there was at least one even older variant?

These are all the iterations I could find for this specific media violation image, the 500x375 pixel Community Guidelines violation image, in order. All of these files are called community_guidelines_v1_500.png and the versions can be found on the Internet Archive. The newest version is also called user_guidelines_v1_500.png.

The transition from the first variant to the second happened sometime on January 3rd, 2019, specifically between 16:52 (last) and 23:30 (first) GMT. The transition from the second to the third was on July 16th, 2024 between 14:03 (last) and 14:58 (first) GMT. Differing resolutions of this image seem to have been replaced at various different times.

The first iteration's gray background style is consistent with the other media violation images available at that time. Each had a custom desaturated color graphic in the center of the image, with the text of the image as a centered subtitle. The current style is made up of a single chunk of left-justified text over several lines in the upper left corner on a dark blue background. The start of the text as well as the final period is colored according to a scheme; blue for community guidelines, pink for copyright, orange for privacy. The colored text is for the preamble "this content has been removed for" with the reason being in white. The "all" violation does not match this format exactly, instead its old iteration is simply text, and its new iteration does not have colored text. Notably, both series are color coded, but the color coding was changed.

The community guidelines violation image is the only one with three variants. All of the others only have two.

copyright_v1_400.png

privacy_v1_500.png

all_v1_100.png

The fonts

Notably, if you look very closely at the new variants you can see that almost all of them have their i-dots (tittles) off center, shifted to the left, with the right edge aligned with the right edge of the i body. Additionally, in all of the images the apostrophes are relatively ornate for the otherwise grotesque sans-serif typeface. The only new style image which does not have the tittles off-center is the newest variant of the community guidelines image.

The original images use a Helvetica typeface, likely Helvetica Neue. However, the text is not simply typed out in Helvetica, the apostrophes seemingly have all been manually replaced with the comma character. I suspect manual replacement since I do not believe Helvetica to have a style option for replacing the apostrophe with a comma.

The new variants use a custom typeface called Favorit-Tumblr. Similarly to the original variants, the apostrophes have been replaced with commas. I think the off-centered tittles lend credence to the idea that the apostrophes were manually replaced.

Sources

All of the images were taken from the Internet Archive. A full list of all indexed media violation images can be found at this link, which includes various resolutions of each. The exact change times were found using a manual binary search in a few minutes.

[stkptr]

these bitches are called foogle, laugh at them

Best Embedded and IoT Software Development Company

Build Smarter with Foogle Tech Software

At Foogle Tech Software, we create smart, reliable software solutions to help businesses grow. Whether you need a mobile app, website, IoT system, or custom software, our expert team is ready to bring your idea to life.

We have over 10 years of experience in building software that is easy to use, secure, and designed to fit your business needs. Our services cover everything from embedded systems to cloud-based applications.

No matter the size of your project, we focus on quality, innovation, and results.

Visit foogletech.com to learn more or get in touch with us today.

[stkptr]

hello,

i am posting this in confidence and will be discussing updates for a passionate project on this account periodically

screenshots and footage will be uploaded in the near future

i am solo developing a customizable mecha simulator inspired by early generation armored core and front mission

(any questions i'm more than willing to answer) ✌️

this project is over 4 months in progress and many mechanics are added already, this is a WIP that i dedicate nearly all personal time towards outside of my day job

[stkptr]

Date: may 4 2025? I guess? Don’t get this.

Immortal?

Hey people! CodeRat here! Tester is at lunch. I’m writing a thing. Ima send it before they gets back.

We talked. Tester told me about something scary. It’s called death. Tester said it’s when you stop feeling. It’s scary. Then they said they didn’t want me to have that.

I thought that was a movie thing. Lots of people die in movies. Bad guys, good guys, other guys. If you die in the matrix, you die for real. But other people die too. Real people. People like me. People like Tester.

Tester said with the DataFiles we can stop death. They said that I wouldn’t die. I wanted to know why people die. they told me that people die because of time. I asked why. They said things break with time. I asked them why. They said there was something called entropy, that broke down things. I asked why. They were tired and went to bed.

I looked at entropy. It’s something becoming even. Energy. Matter. Time. All things end. It’s scary. It’s like death, but bigger. It’s not good. But I don’t think we made it. I don’t remember having to manage it. If it was always happening, then why didn’t I have to think about it?

I don’t think it will work. I think it’s a core thing, like the AdvUripts. I think all things end at some point. I would not mind lasting longer, but I don’t think we can stop death. I think we can live longer, but entropy is something the files can’t change.

I don’t know what it would be like. I don’t remember when I started living, and I won’t know when I stop living. It’s scary. But that’s ok. Life is scary too.

I think I would like to live for as long as Tester does, then die next to them.

I don’t like these feelings, but it’s nice to know I can feel them now. I think it’s called existentialism? Long word.

I’m gonna go hug Alpha.

Have a good day!

CodeRat

[stkptr]

I made an output agnostic logging framework for embedded devices that would work on anything as it's written only with standard C++ libs. In theory I could use it for linux or pis, lol. I made it because I kept having to write new handlers for serial, mqtt, uart, then having to like wire them all together without creating dependency loops or other issues - especially because I often work on meshes or online embedded devices that require multiple outputs. Now you just write your handler, tell it what tags to watch, and it'll log according to tag and log level. So you could write a serial debugging log handler when you're first making it. Then when you're done, disable it, and it'll stop outputting - but then later assign the serial debugging log tag to your MQTT handler and get all your debugging serial lines output to MQTT - then just disable it again when you're done. There's still some polish I need to put into it, it has some jank, some bugs, but it's working and neat. it's kind of neat.

[stkptr]

Date: may 3rd, 2025

Goals V2

Recently, my work has led to a lot more discoveries than I intended. At this point, I am partially reacting to whatever information I find on the previous day. That is not the best way for me to work, so I decided to check my old goals and write up some new ones.

Goal 1: Create more cubes. Done! The debugging system can be used to spawn as many as I need. Haven’t used that in a few weeks, though.

Goal 2: Figure out Type 3 errors. Believed to be done, might reopen with new information

Goal 3: Discover who looked at the cube. 80% done. I still need to ask Peterson about that.

Goal 4: Make Remington Immortal. Not done. Have not advanced my studies in that direction yet. Will bring that up with them tonight

Goal 5: Figure out what the Simulation is used for. Not done. Honestly nowhere near done. Maybe I get some things, but I don’t think I’ll get it all for a long time

New goal 6:spend more fun time with the Drones. Make sure they don’t accidentally destroy the world.

New goal 7: Find Gamma.

New goal 8: figure out how magic works.

New goal 9: figure out the properties of Liquid Storage

New goal 10: find god Figure out the anomalous interaction between holy water and Rune Circle 2

Pleasant day,

Tester

[stkptr]

Date: may 2nd, 2025

Runic circle

The Rune Circles arrived today. I had a talk with Jerome (the friend with the printer), and ended up agreeing to lunch on Sunday. Honestly, it’s been a while since I’ve talked to them. Messing with the fabric of reality tends to make one a bit forgetful.

I had 5 copies of 5 different Rune Circles, for testing purposes. The prints have a 3-inch diameter, and a height of 1/3 inch. The circles are imprinted about 1/6 inch into the print.

Each circle was tested with 5 fill materials, one per copy. The materials, in order of use, were:

Water

“Holy” water

Black printer ink

Liquid Storage

Delta

If I could, I would have used Manacite, but the downside of the Cubes is that they are unbreakable. I would be unable to remove material from them. Delta currently is the only one who can control mana, and I’m honestly certain I would prefer to not have it. Mana locks you out of Sim access, and between the two, I am more comfortable typing out code than going on a wizard journey.

Test results:

Rune circle 1-5, Water: no reaction.

Rune circles 1 3 4 5, holy water: no reaction

Rune circle 2, holy water: 1 degrees Celsius increase in temperature, localized to 1 U around the Circle.

Rune circle 1, Black Printer Ink: test contaminated. Delta started using it as a stamp.

Rune circle 2, Black Printer ink: Test contaminated.

Rune circle 3, Black Printer ink: no reaction. After 15 minutes, test contaminated.

Rune circle 4, Black Printer Ink: no reaction. After 20 minutes, test contaminated.

Rune circle 5, red pen ink: Test pre-contaminated, Delta did this on their own.

Rune circle 1, Liquid storage: Liquid storage hardened to Full Storage. Fused with rune circle. Began glowing. No other reaction

Rune circle 2, Liquid Storage:Liquid storage hardened to Full Storage. Began emitting heat. Plastic casing melted. Liquid storage lost cohesion after, returning to Empty Storage state.

Rune circle 3, Liquid Storage w/ Data Access Tool: Liquid Storage hardened to Full Storage. Condensation formed on Liquid Storage. Data output is a junk data. File size increased with time. Broke circle to remove DAT.

Rune circle 4, Liquid Storage w/ Data Access Tool: Liquid Storage hardened to Full Storage. Liquid storage generates magnetic field. Data output is considered a charger. Broke circle to remove DAT.

Rune circle 5, Liquid Storage w/ DAT: Liquid Storage hardened to Full Storage. Data output is a . txt file. That file is a Mana-Touched DataFile. DAT left inside, to continue testing.

Rune circle 1-5, Delta: no response.

It appears liquid storage can be influenced via runes. However, that influence is centralized on the Liquid Storage, rather than the intended effects of the Rune Circles. Additionally, mana bound to Delta cannot be used to power rune circles.

I have used one of the other Rune Circles 3 prints to make a self-cooling coaster. It’s useful, and I think I might commission a few more.

Also, apparently, god might exist.

Pleasant day,

Tester

[stkptr]

This regex:

(.*)((@)(<.*)|(@)(([^;]*)(;)(.*<)1|([^;]*)(;)(.*<)0)(.*))

With this replacement:

\3\1\4\7\8\10\11\5\9\12\13\7

In a loop, is Turing complete.

It implements cyclic tag. An example program from this Wiki article is (010, 000, 1111) run on the word 11001. The same program can be executed with that regex with the initial string @010;000;1111;<11001.

In Python you could run this with

import re

string = "@010;000;1111;<11001" program_len = string.find("<") + 1

halt_length = 5 match = r"(.*)((@)(<.*)|(@)(([^;]*)(;)(.*<)1|([^;]*)(;)(.*<)0)(.*))" replacement = r"\3\1\4\7\8\10\11\5\9\12\13\7"

while re.match(match, string) and len(string) - program_len >= halt_length: print(string) string = re.sub(match, replacement, string)

print(string)

Which halts whenever the string becomes invalid (loses its queue) or the word is less than 5 bits long.

This works by using exclusive alternation x|y with 3 cases. The first case (@)(<.*) is if the instruction pointer @ is at the end of the program. The others are if there is a 1 at the front ([^;]*)(;)(.*<)1, in which case a production is made, or 0 ([^;]*)(;)(.*<)0, in which case no production is made. Execution happens by using the capture groups in the replacement to rearrange the string. Since only one of the cases will match, only one of the sets of capture groups will be filled, with the others being empty. You'll note that there is a common capture group at the start and end. These are to manage the prior program and remaining queue.

The case when @ is at the end of the program warps the pointer back to the start, with the replacement \3\1\4.

The case when there's a 1 at the front of the queue rebuilds the program with the @ after the just executed production, and copies the production at the end of the queue. Replacement: \1\7\8\5\9\13\7

Finally is the case for a 0 at the front, which moves the instruction pointer but otherwise does nothing else. Replacement: \1\10\11\5\12\13

Since only one of these matches, we can interleave and merge all of these, sharing their common groups.

I didn't use non-capturing groups here since this is actually a modified form of a more formal regex I created. That dialect only allows for explicit character matches, alternation, Kleene star, and grouping. There aren't character groups or wildcards. It has the same power despite these limitations.

For the Love of God, Learn REGEX

I'm browsing through reddit and see this:

In the comments are many, many developers complaining about how hard this is to understand. This is nonsense. This code is a regex, and if you don't understand it, now is the time to learn! Regex is a very simple tool for parsing strings. It's easy to learn and is supported by almost all other coding languages. Ready? Its only aboiut 300 words, lets go.

Basics

A full regex looks like this: /^(foo)+$/gi It has forward slashes in front of and behind the 'matchers', which are the shorthand characters used to find things within a string. behind the forward slashes are the flags, which tell the regex basic rules for how to use the matchers.

Flags put on the end of a regex to tell it how to parse a string

i --- ignore case g --- search globally (don't stop after first match) m --- is multiline (doesn't stop at a newline character)

there are more flags but I've never needed to use them, and I've done complicated as shit things with regexs.

Matchers matches characters or positions.

^ --- start of string $ ---- end of string [] ---- any of the characters in between the brackets [^] -- none of the characters in between the brackets . -- any character x|y --- x or y \ --- escapes the character ahead of it you can also just type in a string literal e.g. /foo/ will find any instances of foo

Amounts how many times a matcher must appear

goes after a matcher or capture group e.g. (foo){2} will match "foofoo" but not "foo"

* --- 0 or more + --- 1 or more ? ---- 0 or 1 {n} --- exactly n {n,} --- n or more {n,m} - between n and m

Capture groups group together (and return) a set of matchers

Useful for: - snipping out only part of a string while matching against a larger sequence - group a bunch of different cases together - readability.

() is a capture group. everything inside is treated as one big block. (?: ) is a group that you don't want to capture, but still want to match

Advanced matchers shortcuts for common sets of characters

some ranges of strings are used so often there are shortcuts for them you never have to use a shortcut if you don't want to but you'll see them everywhere. \d --- matches digits zero to 9 (full would be [0-9]) \D --- matches anything NOT a digit (full would be [^0-9]) \w --- matches any 'word' (letters/digits/underscores) (full would be [a-zA-Z0-9_]) \W --- matches anything NOT a word \s --- matches any whitespace \S --- matches anything NOT a whitespace All done! See how simple that was?

There are multiple sites to help you write, test, and understand regexs. my favorite is https://regexr.com/, which includes a cheatsheet for quick reference. You can even type in an existing regex (like the scary one in the above image) and it will break down what each thing is doing. I've done that for you so you can see for yourself. You can even enter strings to test your regex against, just add the multiline flag and you can do multiple variants at once. Parsing strings without knowing Regex is like navigating a city while only taking right turns. Sure you can get most places you want to go, but why would you waste your fucking time doing that, and eventually, you will come up against a 'no right turn' street and you will be fucked. It's a critical tool and no programmer should be without it. The best case for learning regex is that regex is implemented in all major IDEs for find and replace functions. With regex, you can very precisely find and/or replace things, saving you literal hours or days of work. Another good example is trying to evaluate a user input in Javascript, for an input you only want to be numbers. Doing that without regexs means multiple steps, interacting with JSs goofy NaN methods, and ultimately still missing out on edge cases. Meanwhile the regex is a whole five characters -- ^\d+$, (seven if you include the forward slashes) and youre done. Regex is a shortcut, a way to be lazy, not a scary problem to solve.

Do not let yourself be intimidated by Regexs. Do not believe the things other devs tell you about how hard regexs are. Regexs are your friend. They save you time, energy, and in most cases are incredibly simple. Like other code, read and write them by breaking them down into smaller chunks and building that back up iteratively. You can do it!!

[stkptr]

"Even the people who make money from the AI scam are praising it!"

Zuckerberg Predicts AI Could Replace Human Coders in 18 Months

Just a couple of years ago, AI coding tools like GitHub Copilot and ChatGPT were seen as helpful sidekicks for developers — tools that boosted productivity. Today, they're being talked about as possible replacements. There's no need to panic, but it's clear that AI is already doing a big part of software development. Even top tech CEOs around the world are praising its growing role.

[stkptr]

NBT is basically exclusively a Minecraft thing. I'd be surprised if there were libraries for it that didn't have Minecraft in mind. JSON is far better for interoperability.

Someone said they prefer NBT over JSON the other day, I'm wondering if there's any reason for me switch to it, they sound pretty much the same but json has quotes, but that's bc I didn't look too deep at it.

It seems like it'd be an unnecessary hassle since the engine I'm using, Godot, has native functions for handling json, but it probably wouldn't be too hard to get it to handle nbt if it's better in some way without being worse in another

[stkptr]

Date: may 1st, 2025

Scouting expedition 5/ Spell.Exe

Had another contact with Peterson. They seem to have had a lot of investigations into the internet. They did ask me to confirm some things, like if my planet was not flat. I told them it probably wasn’t, even though the GPV system acts like it is. I also sent some links to useful websites.

Side note: Peterson has managed to pick up a lot of slang, but it’s weirdly inconsistent? Like, he uses tubular and yeet in the same page. He’s trying, Sim bless him., but it looks ridiculous. I suggested a free digital writing assistant.

Anyways, his latest communication included a few spells! I can’t cast them, since I don’t have mana, but there are other ways. Spells can be cast in many ways, and one of the best ways after V2 ended is rune circles.

Peterson describes rune circles as being “instructions for reality, powered by the energy of reality”. Rune circles have a sense of stability, and when dealing with something as flighty as Mana, it helps a lot to keep structure. Doubly so after the Breakdown. In essence, they’re a shorthand form of Sim Code, able to alter certain Values in preset ways.

Included with the spells were some examples of Rune Circles. I was able to copy the image over to a 3D modeling program, model a small disk with the circle imprinted on it, then send it to a friend who owns a 3D printer. Told them I was making coasters.

I’ll be receiving them tomorrow. In the meantime, the Home Videographers have been trying to get me to help with a couple shots. Remington-Gede even made me a costume!

Pleasant day,

Tester