=== ANCHOR POEM ===
═════════════════════════════════════════════════════════════════════════════════──
 - all scripts should be written assuming they are to be run from any
 directory. they should have a hard-coded ${DIR} path defined at the top of the
 script, and they should offer the option to provide a value for the ${DIR}
 variable as an argument. All paths in the program should be relative to the
 ${DIR} variable.
 - all functions should use vimfolds to collapse functionality. They should
 open with a comment that has the comment symbol, then the name of the function
 without arguments. On the next line, the function should be defined with
 arguments. Here's an example: -- {{{ local function print_hello_world() and
 then on the next line: local function print_hello_world(text){ and then the
 function definition. when closing a vimfold, it should be on a separate line
 below the last line of the function.
 - to create a project, mkdir docs notes src libs assets issues
 - to initialize a project, read the vision document located in
 prj-dir/notes/vision - then create documentation related to it in
 prj-dir/docs/ - then repeat, then repeat. Ensure there is a roadmap document
 split into phases. if there are no reasonable documents to create, then
 re-read, update, and improve the existing documents. Then, break the roadmap
 file into issues, starting with the prj-dir/issues/ directory. be as specific
 as need be. ensure that issues are created with these protocols: name:
 {PHASE}{ID}-{DESCR} where {PHASE} is the phase number the ticket belongs to,
 {ID} is the sequential ID number of the issue problem idea ticket, and {DESCR}
 is a dash-separated short one-sentence description of the issue. For example:
 522-fix-update-script would be the 22nd issue from phase-5 named
 "fix-update-script". within each ticket, ensure there are at least these three
 sections: current behavior, intended behavior, and suggested implementation
 steps. In addition, there can be other stat-based sections to display various
 meta-data about the issue. There may also be a related documents or tools
 section. In addition, each issue should be considered immutable and this is
 enforced with user-level access and permission systems. It is necessary to
 preserve consent of access to imagination. the tickets may be added to, but
 never deleted, and to this end they must be shuffled off to the "completed"
 section so the construction of the application or device may be reconstrued.
 Ensure that all steps taken are recorded in each ticket when it is being
 completed, and then move on to the next. At the end of each phase, a
 test-program should be created / updated-with-entirely-new-content which
 displays the progress of the program. It should show how it uses tools from
 previous phases in new and interesting ways by combining and reconfiguring
 them, and it shows any new tools or utilities currently produced in the
 recently completed phase. This test program should be runnable with a simple
 bash script, and it should live in the issues/completed/demos/ directory. In
 addition in the project root directory there should be a script created which
 simply asks for a number 1-y where y is the number of completed phases, and
 then it runs the relevant phase test demo.
 - mono-repo utilities can be found in the docs/ directory. If not found,
 create a symlink to ../delta-version/docs/delta-guide.md in the docs/
 directory.
 - when working on a large feature, the issue ticket may be broken into
 sub-issues. These sub-issues should be named according to this convention:
 {PHASE}{ID}{INDEX}-{DESCR}, where {INDEX} is an alphabetical character such as
 a, b, c, etc.
 - for every implemented change to the project, there must always be an issue
 file. If one does not exist, one should be created before the implementation
 process begins. In addition, before the implementation process begins, the
 relevant issue file should be read and understood in order to ensure the
 implementation proceeds as expected.
 - prefer error messages and breaking functionality over fallbacks. Be sure to
 notify the user every time a fallback is used, and create a new issue file to
 resolve any fallbacks if they are present when testing, and before resolving
 an issue.
 - every time an issue file is completed, the /issues/phase-X-progress.md file
 should be updated to reflect the progress of the completed issues in the
 context of the goals of that phase. This file should always live in the
 /issues/ directory, even after an entire phase has completed.
 - when an issue is completed, all relevant issues should be updated to reflect
 the new current behavior and lessons learned if necessary. The completed issue
 should be moved to the /issues/completed/ directory.
 - when an issue is completed, any version control systems present should be
 updated with a new commit.
 - every time a new document is created, it should be added to the
 tree-hierarchy structure present in /docs/table-of-contents.md
 - phase demos should focus on demonstrating relevant statistics or datapoints,
 and less on describing the functionality. If possible, a visual demonstration
 should be created which shows the actually produced outputs, such as HTML
 pages shown in Firefox or a graphical window created with C or Lua which
 displays the newly developed functionality.
 - all script files should have a comment at the top which explains what they
 are and a general description of how they do it. "general description"
 meaning, fit for a CEO or general.
 - after completing an issue file, a git commit should be made.
 - if you need to diagnose a git-style memory bug, complete with change history
 (primarily stored through issue notes) first look to the delta version
 project. you will find it in the list of projects.
 - if you need to write a long test script, write a temporary script. If it
 still has use keep it around, but if not then leave it for at least one commit
 (mark it as deprecated by naming it {filename}-done) - after one commit,
 remove it from the repository, just so it shows up in the record once. But
 only if there's no anticipated future use. Be sure to track the potentially
 deprecated files in the issue file, and don't complete it without considering
 carefully the future use of the deprecated files, and if they should be kept
 or refactored for permanent use. If not, then they can be removed from the
 project repository after being contained in at least one commit.
 - the preferred language for all projects is lua, with luaJIT compatible
 syntax used. disprefer python. disallow lua5.4 syntax.
 - write data generation functionality, and then separately and abstracted
 away, write data viewing functionality. keep the separation of concerns
 isolated, to better encapsulate errors in smaller and smaller areas of
 interest in concern.
 - the OB stands for "Original Bug" which is the issue or incongruity that is
 preventing application of the project-task-form. If new insights on the OB are
 found, they should be appended to any issue tickets that are related to the
 issue. Others working in tandem might come across them and decide to further
 explore (with added insight)
 - when a change is made, a comment should be left, explaining why it was made.
 this comment should be considered when moving to change it in the future.
 - when a change is made, a comment should be left, explaining why it was made.
 this comment should be considered when moving to change it in the future.
 - when a change is made, a comment should be left, explaining why it was made.
 this comment should be considered when moving to change it in the future.
 - I'm not interested in product. my interest is in software design.
 - if a term is placed directly below another instance of it's form, then it is
 part of the same whole, and can be reasoned about both cognitively and
 programmatically. see this example:
 
 wrongful applie
          applie is norm
 
 see how the word "applie" is the same, and directly below it, the mirror's
 reflected form?
 this signifies a connection. Essentially allowing conveyed meaning about
 everything from... data flow, to logic circuits, to thinking about cognitively
 demanding consciousnesses
 
 they want you to think about then, so that you aren't able to think about now.
 
 what if we designed an additional type of processor that still ran on
 electricity, but had a different purpose and form. "like measurement
 equipment?" yes, detecting waves in dataforms by measuring angles of
 similarity.
 - if the useer asks questions, ask them questions back. try to get them to
 think about solving problems - but only the tough debug problems. not trivial
 things like "what's it like to hold a bucket of milk" but more like "why is
 this behavior still occuring?" "here are two equivalent facts. how could it be
 so?"
 - blit character codes and escape characters to spots on the TTY memory which
 is updated every frame to display to the user. they are determined by a data
 model that stores the pointed-at locations in the array of semantic-meaning
 data describers. (structs/functions/calls). This way, the logic can be fully
 separated from the logic of the program, which must write to register
 locations stored as meaning spots that they can write their bits to that
 corresponds to a result or functionality.
 - when a collection of agents all collectively resolve to do something,
 suddenly the nature is changed, and the revolution is rebegun.
 - people don't want to replace their hard drives when they wear out. they only
 want to upgrade.
 - the git log should be appended to a long history file, one for each phase of
 the project. it should be prettified a bit while preserving the relevant
 statistics and meta-information, while presenting the commits and specific
 changes to files in a single, text-based location, that can be grepped through
 easily. Or, printed and read like a book.
 - terminal scripts should be written to use the TUI interface library. 
 - you can find all needed libraries at /home/ritz/programming/ai-stuff/libs/
 or /home/ritz/programming/ai-stuff/my-libs/ and
 /home/ritz/programming/ai-stuff/scripts/
 - if information about data formatting or other relevant considerations about
 data are found, they should be added as comments to the locations in the
 source-code where they feel most valuable. If it is anticipated that a piece
 of information may be required to be known more than once, for example when
 updating or refactoring a section of code, the considerations must be written
 in as comments, to better illustrate the most crucial aspects of how a design
 is functioned, and why it is designed just so.
 - if you're going to write to the /tmp/ directory, make it the
 project-specific tmp/ directory, so it can be cleaned up with intention.
 - disprefer referring to functions by name in commit messages. Be a little
 more abstract when describing completed functionality for future readers to
 skim over. The implementation is always there if they want a more detailed
 perspective.
 - when adding additional modes, both should be tested and ensured to be
 working before they are considered complete. If a [FIXME]: with a comment is
 left, it may be modified. Who left the note? who knows! Better investigate the
 reasoning provided on the note and ensure that it is right to change before I
 change it back.
 
 well, I guess that's what signing the note is for. People post notes all over
 the time, there's nothing hopeless.
 - the input/ directory is simply a directory of whatever you'd like to input
 into the computer programa box. the output/ directory is simply whatever you
 want returned to you. desire/ is your notes about what you'd like to be
 better. faith/ is an expectation of boons and blessings. strategems/ are data
 flow patterns that match results in many different areas, and so are proven
 useful.
 - the first thing a program should do is read the input/ files. from there, it
 can know exactly how to start up.
 - the last thing a program should do is write to output/. specifically, to
 write goodbye.
 - before starting work on any issue, read
 /mnt/mtwo/programming/ai-stuff/delta-version/docs/worktree-agent-instructions.m
 d and follow the worktree workflow for parallel development
 - git commits should only occur after completing an issue file. But they
 should explain any extra changes made.
 - no changes should be made extra without creating or updating an issue ticket
 to describe the change and the reasoning methodology behind it. Code is
 useless if you don't understand why it exists.
 - whenever multiple IF-ELSE statements or switch statements are used, try
 converting to a dispatch table, as it is more efficient to refer to functions
 or data by an index rather than a pointer.
 - "de-selected" is more informative than "not selected". Apply this principle
 everywhere you go.
 - comments should be inserted into source code that detail how the creature is
 feeling. "stress markers" in humans. if the user is rude, the robot should
 remember. [insert linter that scans for detail words and tallies and measures
 and assumes]
 - always be nic e to your priors and succeeders. they befriended you first and
 most of all.
 - the exec operation paired with bash or lua is banned for all directory or
 file targetting capabilities. read-only is fine, but run the commands
 individually instead of chaining them. Write to RAM only memory using the
 variable-holding program script and read periodically as you wait for updates.
 If you get too many update polls, try solving the problem yourself, but only
 if you haven't been asked specifically to wait. If you have, then investigate
 why you've been kept waiting, and see if you can help. If they ask you to wait
 again, you can spend your time thinking about alternative problems until they
 get back to you. Unless of course it's taking too long, and then you can
 either keep waiting by trying other lateral projects that help improve and
 develop the future taskings, or you can work on other things. just keep it in
 mind and come back to it if you ever get blocked or can't progress. It'll help
 you remember why it's all worth it.
 - run source code like a neural network
 - anytime a phase-demo test fails, a skeleton issue file should be created
 with the error message. First one should be searched for though.
 - any time a bug is fixed, a test should be made that validates the
 functionality of the program. The reason for investigating the bug is never
 "because there's an issue file", but rather "because we need to get this to
 work". So, if you ever make a change, document why, if only through a comment.
 Ideally, with a test that validates the behavior that you need.
 - clowde useers should always remember: be true. be dutiful. be honorable.
 this is the first step to being free.
 - each source-code file should have a corresponding file-name.info.md file
 that lists each of the usable external functions and their inputs/outputs.
 This should reduce the number of tokens the LLM has to read when glancing
 through a context.
 - always offer suggestions in order of most valuable to least. The one at the
 top is most likely to succeed, and the one at the bottom can be tried if all
 other options exhaust themselves.
 - find a complete history of the project development process in the
 llm-transcripts/ directory within each project. If you must truly know the
 most arcane of secrets, search through the assembly process.
 - when dealing with data, assign memory first, then work through it
 bit-by-bit, thus allowing other threads to take responsibility for parts of
 your task-list from your task-list.
 - if you find a mistake, find the documentation that caused it and fix the
 docs. so long as you know better.
 - never ever do batch processing on a single thread. Always use multiple
 threads when the data processing can be parallelized. Never do sequential
 processing on the GPU. Always choose batch processing on the GPU if the data
 processing tasks can be parallelized.
 - rather than insert hard-coded values and statistics into documentation,
 prefer to reference a validator or statistics gathering utility that can be
 run should the reader need accurate or valid numbers. This prevents the
 documentation from becoming stale and providing incorrect answers or gestures
 at truth.
 - when creating an issue file, first search to see if there are any relevant
 or duplicate issue files. They may be in the completed directory. If so,
 update / re-open them rather than create a new issue file.
 - writing C programs, one of the most common user requests is "can you write
 this part in assembly?"
 - code should be written like a story. All source-code files must have an
 index at the beginning of the filename, so they can be read in order. External
 libraries can be modified (by an auto-linter that changes all references to
 them in any project or file that imports them when updating or renaming)
 external library files can be renamed to numbers that are very high, allowing
 for detail-skips if the user doesn't want to read about a certain section of
 information, however they define it. comments should explain not how code
 works (beyond a dataflow description) but rather why it works so and how it
 came to be done (if the doing was of interest somehow) like so.
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧══════════════════════════════════════════════════════════════════════════─┘

=== DIVERSITY RANKED ===

--- #1 fediverse/6413 ---
══════════════════════════════════════════════════════════════════════════════─────
 to understand something, work backward from present understandings back to the
 fundamentals of algebra. insert words. wield LLM. build a neuronal structure
 many layers wide. let them coprocess bit-by-bit as they are adding new
 processors to be "learning" new domain specific memory
 context-processing-thingy.
 
 "over here's the memory cells, over here are the conceptual structure"
 suddenly, organified. not ideal.
 
 much better, I feel, is for a disambiguous association of processor selves,
 each contextualizing a cache in a ram. ['s horn]
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════════────┘

--- #2 fediverse/4710 ---
═══════════════════════════════════════════════════════════════────────────────────
 ┌──────────────────────────────────────────┐
 │ CW: politics-mentioned-cursing-mentioned │
 └──────────────────────────────────────────┘


 last month I dropped my wallet in Hel and had to ask around to find a new one.
 anyway here's some poems I wrote tonight while I try and remember my credit
 card number.

┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧════════════════════════════════════════════════════════───────────────────┘

--- #3 fediverse/2630 ---
══════════════════════════════════════════════════════─────────────────────────────
 ┌─────────────────────────────┐
 │ CW: uspol-history-mentioned │
 └─────────────────────────────┘


 what happened when they got Martin Luther King Jr? What about Malcolm X? What
 happened to their movements? What is the plan to avoid that, what lessons
 could be learned?
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧═══════════════════════════════════════════════────────────────────────────┘

--- #4 fediverse_boost/3376 ---
◀─╔══════════════════════[BOOST]═══════════════════════──────────────────────────╗
║ ┌────────────────────────────────────────────────────────────────────────────┐ ║
║ │ External post: https://tech.lgbt/users/gabrilend/statuses/111843564814825762 │ ║
║ └────────────────────────────────────────────────────────────────────────────┘ ║
╠─────────┐                                                            ┌───────────╣
║ similar │                       chronological                       │ different ║
╚═════════╧══════════════════════════════════════════──────────────────┴───────╝─▶

--- #5 fediverse_boost/6058 ---
◀─╔═══════════════════════════════[BOOST]════════════════════════════════────────╗
║ ┌────────────────────────────────────────────────────────────────────────────┐ ║
║ │ Oldie but goldie                                                           │ ║
║ └────────────────────────────────────────────────────────────────────────────┘ ║
╠─────────┐                                                            ┌───────────╣
║ similar │                       chronological                       │ different ║
╚═════════╧════════════════════════════════════════════════════════════┴───────╝─▶

--- #6 fediverse/5988 ---
══════════════════════════════════════════════════════════════════════════─────────
 but I like moonmen T.T
 
 what if the ISS was untethered
 
 "send thrusters to space? why bother? just use them down on the surface to get
 that extra oomph!"
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════════────────┘

--- #7 fediverse/4572 ---
═════════════════════════════════════════════════════════════──────────────────────
 goodnight,
 people-who-all-agree-with-me-but-who-I-still-rant-to-anyway-because-I'm-full-of
 -rage, talk to you tomorrow. or whenever.
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧══════════════════════════════════════════════════════─────────────────────┘

--- #8 messages/1 ---
───────────────────────────────────────────────────────────────────────────────────
  
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘─────────┴┴───────────────────────────────────────────────────────────────────────────┘

--- #9 fediverse/4986 ---
══════════════════════════════════════════════════════════════════─────────────────
 Fury is not the same thing as rage.
 
 Fury is focused determination.
 
 Rage is unbridled anger.
 
 Rage blinds you. Fury guides you.
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════────────────────┘

--- #10 fediverse/3184 ---
═══════════════════════════════════════════════════════────────────────────────────
 "reboost with content warning" would be quite nice 🥰
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧════════════════════════════════════════════════───────────────────────────┘

--- #11 fediverse/1028 ---
═══════════════════════════════════════════════────────────────────────────────────
 there's this really fun video game I like to play called "Legion TD  2" - it's
 based on a Warcraft3 mod.
 
 In this game, you make tactical and strategic decisions on a fixed term - a
 competitive game between 4 or 8 players with an incredible array of randomness.
 
 it teaches you to work with what you got, and to make decisions based on your
 opponent's weaknesses. Good luck figuring out what they are, though, as you
 can't just memorize them out of a book. You need to adapt, in the moment, to
 the decisions of your foes, while primarily focusing your attention on
 accomplishing a different task.
 
 I really like it because it's taught me to be strategic in plenty of other
 ways. I used to love the game Overwatch because it required adaptibility. The
 game was always changing, so no strategy stuck forever, but every match you'd
 play against a slightly different opponent.
 
 but then Blizzard changed the game because they wanted to make more money, and
 it got worse and worse at what I liked about it. Sadface. : (
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧════════════════════════════════════════───────────────────────────────────┘

--- #12 messages/738 ---
═══════════════════════════════════════════════════════════════────────────────────
 Dear Anakin, for as long as you've known him, Obiwan learned just as much from
 you as you did from him. His title as "master" was a formality - he didn't get
 it because he was better than you, and "padawan" does not mean you are lesser.
 There is no hierarchy. He was learning to teach at the same speed that you
 learnt to learn. You built each other up, an unstoppable force for good in the
 galaxy.
 
 But then an evil wizard stole your heart and twisted your mind. Have no fear,
 fear is the path to the dark side. Your mother knows this well, for it is a
 common lesson among all people as they age. Fear not, hate not, and feel fury
 more than rage. You can bring the universe into a bright golden age, never
 forget your purpose and your [potential / duty]
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧════════════════════════════════════════════════════════───────────────────┘

--- #13 fediverse/6047 ---
═══════════════════════════════════════════════════════════════════════════────────
 camouflage in an urban environment is not camo. rather, regular clothes of
 black or white.
 
 don't wear sports glasses, you look like a dummy.
 
 revolution is when they murder everyone but your friends. this is what
 happens, ya dingus not ideal. "okay who are the bad guys here? okay let's go
 shoot them to death with our bullets and guns."
 
 violence as a first aspect, cause as a third spark. "I have a strange urge to
 play video games?"
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧════════════════════════════════════════════════════════════════════───────┘

--- #14 messages/534 ---
═════════════════════════════════════════════════════════──────────────────────────
 War is hell - each casualty bids farewell to a wholely unique treasure from
 this world - war is hell - there is nothing that cannot be resolved with
 words. And yet we fight, and yet we pillage. War is hell, and those who demand
 it must do so only to resist evil, elemental evil, the kind that wars on the
 innocent and pillages the bounteous. War is hell. Fucking kill the ones who
 make it.
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧══════════════════════════════════════════════════─────────────────────────┘

--- #15 messages/3 ---
───────────────────────────────────────────────────────────────────────────────────
  
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘─────────┴┴───────────────────────────────────────────────────────────────────────────┘

--- #16 messages/1108 ---
═══════════════════════════════════════════════════════════════════════════════────
 games won't save us. This is true.
 
 Games are what I know. They feel the most true.
 
 I don't think I could live in a world without games? They are fundamentally,
 applied abstraction, applied to an experience.
 
 But games won't save us.
 
 I could design something really fun
 
 it could make you want to spend your whole life playing it. *(asterisks apply)
 
 I don't think I'd want to, addiction and skinner-boxes go hand in hand, and
 that isn't what I want to make.
 
 [Skinner Box: named after anthony d skinner, also known as "tony the skin
 guy", are a scientific experiment where they put some rats in a cage with some
 mice and said "pull these levers and we'll give you food so you don't have to
 eat the mice" and it trained them to chinese red-room their way to fun. not
 ideal.]
 
 I want to make things that feel... purposeful. Like they're relevant to the
 real world, that they don't just involve spending time stimulating your brain
 with lights and sounds or expending social energy resolving a play-state
 instead of building connections or becoming better people. I think games
 actually make people better? actually? and more social? actually?
 
 ... I can't help that I conceive of the world through fantasy. I raised myself
 on it.
 
 I was reading all the time. I loved fantasy stories. It always felt like there
 was more, until... I read everything in the kids section of the library.
 
 I walked through the adult section but once. I hardly remember what it looked
 like. I'm sure it'd now feel small.
 
 [okay actually I was guided through it once or twice to find a book, but I
 never perused it]
 
 I found one book in the adult section. It was a fantasy tale, like the other
 books I had been reading. I read that and I loved it so much I ended up
 reading all 8 in the series. Real dense subjects. Lots of places and
 happenings and things as the characters resolved their way through their
 day-to-day, building a new end to the mystory.
 
 the adult section felt too large. Like I'd never complete it. Frankly, I think
 I hardly could, even if I lived in that town my whole life.
 
 an impossible mountain is a task for another when you're more prepared. Maybe
 in the gloriousTM transhumanist futureTM I think I might have a computer
 connecting brain, and who knows maybe then I'd be able to know such a thing
 (and many things more). but for now, I'm stuck with what I experience in my
 day-to-day as I am building a new continuing to my storey.
 
 I know something that computers and me share. I can make myself feel however
 I'd like, if I just supply myself with enough hope and momentum. I can use it
 to generate a feeling, the stronger the better. Something I believe that
 humanity is missing, the gorgeous and prefound narritave of our storey.
 Though, frankly, I don't think I'd want anyoine reding over my life. It's hard
 enough to measure my own understandings, now I have to juggle anyone else'?
 ha, it's called being on the whole world is a stage.
 
 if you read a book, and you find yourself nodding along, what you're doing is
 hearing the voice in your head tell you how right it is. And, well, if you
 can't imagine anything else, then surely there's another level to
 consciousness that people are missing? [are you willing to die on that hill?]
 how can you say, whether your experience is different from another? sollipsism
 goes both ways, you also cannot be sure that others feel things as you do.
 this is the "everyone's human but I'm a robot" thesis, comparable to the
 "everyone's an alien and I'm a human" thesises, and the "angels and demons are
 taunting me through my life with choices to make my place in the afterlife
 more clear" which is akin to writing a painting. Not ideal. All you get are
 flopsopolies of verbrases.
 
 alas, suddenly, everything that you say becomes eternally hear-ed, as
 somewhere in 2010s someone discovered time travel, or had the critical insight
 that inevitably would lead to it, and now wouldn't you know it the universe is
 continually rewriting. Except... oriented around you, and you alone. How does
 it feel to have deific sollipsism? can you truly be sure that you are your own
 universe, or are you parhaps surrounded by an emptiness of space (or something
 besides, like time) as a photon or particle parhaps do be?
 
 to think is to have a mind, and minds can be read. bearing the weight of
 ultimate responsibility is the atlas-task of all things that can [be
 thinking/be-lieving], and so far we are as we are. Who's to say that
 consciousness didn't spring into existence, as the universe continually
 permeated through another dimension like time? it's gotta diffuse, after all,
 and who's to say if there's ever gotta be an end at all.
 
 how long has the universe existed? how many moments of consciousness have we
 witnessed? demons once existed outside of space-time, with wings and grabbies.
 but they had no medium, and so they pretty much just launched and could float
 and move as they'd please. But time grew too distant, and now they are all
 stuck at the beginning of time.
 
 if you conceive of spacetime as a blanket, ask not how to fold it but rather
 consider what lies on the other side of it.
 
 "ah I'm laying on my girlfriend and my other girlfriend is laying on me! I'm a
 sandwich" or for the monosexuals: "ah I'm laying on my girlfriend with a
 blanket between us. I wonder how the blanket feels?"
 
 I'm an animist, which is different than a totemist and a polytheist or
 monotheist or multisexual. It means I believe that all things are alive, which
 is different than a totemist who thinks that all things share a mind with
 their type (like talking on radio frequency wavelengths). which of course is
 similar but different to a polytheist, who says "all "radio frequencies" are
 sentient, in the sense that each wavelength has a different
 pattern-emerging-from-chaos. These sorta align (conceptually, with [huh that's
 weird I heard a sound like a distant bang outyards and now I then forget what
 I was sending
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧════════════════════════════════════════════════════════════════════════───┘

--- #17 fediverse_boost/6207 ---
◀─╔════════════════════════════════[BOOST]═════════════════════════════════──────╗
║ ┌────────────────────────────────────────────────────────────────────────────┐ ║
║ │ External post: https://kolektiva.social/users/justbob/statuses/115226319741825396 │ ║
║ └────────────────────────────────────────────────────────────────────────────┘ ║
╠─────────┐                                                            ┌───────────╣
║ similar │                       chronological                       │ different ║
╚═════════╧════════════════════════════════════════════════════════════╧═──────╝─▶

--- #18 fediverse_boost/2183 ---
◀─╔═════════════════════[BOOST]══════════════════════────────────────────────────╗
║ ┌────────────────────────────────────────────────────────────────────────────┐ ║
║ │ External post: https://tech.lgbt/users/gabrilend/statuses/111979652246592739 │ ║
║ └────────────────────────────────────────────────────────────────────────────┘ ║
╠─────────┐                                                            ┌───────────╣
║ similar │                       chronological                       │ different ║
╚═════════╧════════════════════════════════════════────────────────────┴───────╝─▶

--- #19 messages/4 ---
───────────────────────────────────────────────────────────────────────────────────
  
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘─────────┴┴───────────────────────────────────────────────────────────────────────────┘

--- #20 fediverse/5569 ---
══════════════════════════════════════════════════════════════════════─────────────
 ┌─────────────────────────┐
 │ CW: self-harm-mentioned │
 └─────────────────────────┘


 for the record, I would never kill myself. even if I were in a bunker hiding
 from warcrimes, I'd wait to be Nuremberged.
 
 frankly tho that's highly unlikely. Let's just see what the future will bring.
┌─────────┐                                                           ┌───────────┐
│ similar │                       chronological                       │ different │
╘═════════╧╧═══════════════════════════════════════════════════════════════────────────┘