Monday, September 19, 2016

Some More on MediaWiki 2

Zim Wiki seems to be the closest example to something like this.


FEATURES:
  • Offline capable version
    • uses all same techniques and formats 
    • compatible with online version
    • contained within one app
    • can access local resources
    • lacks multi-user features
  • Auto-markup like Zim Wiki
  • Customizable Object-bank classes
    • a "bank" refers to a visual, searchable, sortable box of a class of items which are defined by a MediaWiki user.
    • if these objects are visual in nature, such as images, or links to YouTube videos, etc, then the visual representation appears in the bank.
    • Otherwise, there is a format for defining visual data cards to represent those objects. (provides the usability of an app store.)
    • Bank classes have associate pages of defining system data fields that users can fill out.


editing features
  • Endless Editable Meta Field classes
    • {{{sub-class of: x, y, z}}}
    • {{{}}}
    • is a type of
    • is a 

Lost Boys cover, from fake parody to heavy tragedy

Song starts out a light song about deciding to cover Lost Boys and riffing on popstars.

Song goes into singer saying why riffing the song is a bad idea, because it sounds gay.

Song goes into hate rhetoric about gays being lost.

"Dixieland I love you so. And I'm a homophic bro. Forever a lost boy you'll be."

The verses progress from hate rhetoric into the singer realizing that he had a childhood homosexual experience.

portrays it as dirty hypothetical
He sprinkled me with fairy dust and told me to believe. Believe in him and believe in me.
ie. "Peter  Pan I love you so, but I'm a homophic bro. So keep that dust off of me."


Sure they made broke. Back a moveeeeeee.
But we don't want that. Dust in the breeeeeze.
"Peter Pan I love you so, but I'm a homophic bro. So keep that #*&! off of me.

The general idea is that the verses progress from being hate rhetoric into being a deep confrontation with sexuality and a then a denial, and then a deep commitment to lifestyle. - a bit tragic.


portrays it as pure memory and ironic internal conflict ensues.

"Peter Pan I love you so. I will never let you go."
"Forever a lost boy I'll be."

Tuesday, September 6, 2016

Distro 2: ASCII Curses Panelling GUI

Old DOS applications went through a phase of having amazing ascii GUIs and games. Somehow Linux seemed to skip that, straight from server cli to desktop environment.

Why not create a native ascii keyboard-only paneled environment similar to i3 in operation?

  • Mod4 can be used for switching panels.
  • Ctrl and Alt can be used for switching application functions and menus.
  • VIM controls can be used for other operations.
  • Panel Arrangement saves on exit

It will be blazing fast and be usable on server systems.  

Box Drawing Characters


This is a replacement for the kernel console










Sunday, September 4, 2016

SharePlace: Content Management

Facebook, Google+, and Twitter lack content management features.

SharePlace has application-global cards that allow the system to represent media items of all types that do or do not exist on the SharePlace servers.
  • Books
  • Music Videos
  • Movies
  • Games
  • Applications

SoundCloud, YourListen, YouTube, Flickr, Picasa, Instragram, Vines, Pinterest, Facebook Video


All media entities have global application cards with meta data about that item. (Books, movies and shows, Songs, music videos, Articles, anything singularly hosted, reference, or sourced in its definition by multiple organizations. (Any media item that could reasonably be turned into a Wikipedia article.)

Privately held media items such as private pictures do not have application global references for others to use.

Saturday, September 3, 2016

SharePlace: Sharing Network

So the concept is what is called a "sharing network."

The social aspects are there, but there is more emphasis on expressing individual nuances of thought and opinion.

Most actions in this sharing network encourage and facilitate:
  • more nuanced expression
  • more diverse expression
  • flourishing creativity
  • flourishing individuality
  • less group-think/more individuality
  • increased expression in argument
This sharing network allows for proportionality in meaning of individual nuanced opinions about matters, as opposed to most social network feeds that allow for only one or two dimensions of perspective.

It does this fluidly and gradually, modeled after the pace at which users typically desire to elaborate.

Users are able to elaborate at the pace they desire to.

If a feature demands immediate complexity and time in such a way that removes the user from their moment of inspiration, then the feature fails to meet the goals of the application.



Expressive Social Network 'SharePlace'


Social Network (also called a "Sharing Network") that Solves Many Problems of Social Networks
This might be the best idea since sliced bread, twitter, and facebook.

  • Users log thoughts and shared posts. 
  • Users create structures of meaning between remixes and recombinations of their posts in a sandbox environment.
  • Users easily agree and confirm a multitude ideas
  • User find new nuanced commonalities and differences
  • Users find new abilities for nuanced expression and opinion
  • Meaning is discovered
  • Expression is preserved and reusable

Most features have dual purposes:
  1. convenient, pleasant expression
  2. forming relational structures between information
The result is that the relational structures of information proliferate into added user value and benefits the more that the social network is used.

In addition, all of these features facilitate monetization competitive with any other social network.

Graphical Modes (Phases)

Two separate meta data structures exist for the same data, enable adaptation to various phases of a creative process.

There are 4 primary graphical modes.


  1. Brainstorm (Phase 0)
  2. Analysis (Phase 1)
  3. Synthesis (Phase 2)
  4. Refinement (Phase 3).
  1. Wiki style
  2. Tweet/Post style
  3. Storyboarding Style
  4. Blog style
 Phases facilitate the creative process in addition to acting independently.


Phase 0: Create (like a Wiki)

  • entering raw thought
    • text formatting
      • tables, bullets, lists, etc.
    • embedding widgets
      • videos, pictures, gifs, memes, sounds, webpage preview links
  • refine information
  • highlighting and creating containers
    • selecting tags
    • creating tags
    • defining and redefining
  • searching information
  • reducing redundancy
Phase 0 can be ignored completely.

Phase 1: Send (much like Twitter)

  • interact with components that behave like tweets
  • accept components defined externally
    • shares from youtube
    • shares from websites
    • shares from urls
    • shares from widgets
    • shares from anything externally defined
  • copy embed links
  • have conversations about
  • copy application's  ID number
  • defining component
    • person (absolute and irreducible)
      • group
    • thing
      • entity defined by set of things
    • time (absolute time)
    • place (more specific)
      • locale or area
    • event (combination of specific time and place)
      • sequence of events
Phase 1 can be ignore completely, or it can be used without any interaction with other phases, much like one would use Twitter.

Phase 2: Relate (guided storyboarding)


  • construct macro connections
  • interact with form data drop-downs and option menus
  • select conjoining terms
    • :: and ::
    • :: but ::
    • :: or ::
    • :: is true however :: is also true
    • :: is still true acknowledging :: must improve
    • while :: is true :: is not necessarily true
    • :: is example/s of ::
    • :: is like/unlike :: 
    • :: resembles ::
    • :: is true as well as/and/in addition to ::
    • :: is parallel to ::
    • :: is the opposite of ::
    • :: causes ::
      • (caused) (will cause)
    • if :: then ::
    • Perhaps :: but ::
    • :: is false
    • :: is true
    • :: is uncertain
    • :: makes :: feel ::
    • :: identifies with ::
    • :: likes/dislikes ::
    • :: about :: 
      • I can like something 'about' something
      • I can identify with something 'about' something
      • implies a sub-component or trait (I like <this> sub-aspect of <this> larger thing)
    • :: because ::
    • :: by way of ::
  • select emotion contexts
    • lots of emotions

    Phase 2 could be used independent of other phases, or completely ignored.

    Phase 3: Charm (like a blog)

    • create presentable information out of former phases
    • create dolled up presentation of information from other phases
    • this is a front-end final product of the other phase
    • Other information and relations serve as parsable web back-end for web data.
    Phase 3 could be used independent of other phases, to use more in the form of posting blog posts like posting Blogger posts on Twitter, Facebook, or Google+. Users can subsequently implement other phases onto your work in order to pick it apart and analyze it.


    Purpose of 1st Two Phases:

    The purpose of having these two phases is to create endless recombinations of information in one phase is to have the benefits of redundancy in one phase (phase 1), but to eliminate redundancy in the other (phase 0).


    Phase 0: is a substrate of ALL components and remixes. It is supposed to serve as the non-redundant, ever-present repository of referencable construction. Endless remixes of text and embeds can be made from recombinations of Phase 0 information.

    The user interacts with this Phase much like a very long set of blog posts or a very long word document separated and entitled by input date/time/instance. The user inserts images, writes text, embeds widgets, and creates tables and lists.

    Phase 0 has multiple rationales. It is about:
    • allowing users to input information in brainstorm form
    • allowing users to go back and change raw information
    • provisioning one single, simple repository of information
    • serves as a search-able reference document
    • maintains a sense of time-frame and history
    • facilitates version and history control in one source (like MediaWiki)
    Phase 0 allows users to highlight material as in a wysiwyg editor, and create tagged containers around any combination of materials.

    Although Phase 0 is foundational to everything else - it can be completely ignored by the user if the user so chooses. The importance of Phase 0 is to act similar in a way to browser history, but also in the way of a database.

    Phase 1: is a modularization of combined information bits from Phase 0 and the web. Unlike Phase 0, Phase 1 is supposed to be redundant.

    Nothing in phase one exists except as a reference to information in Phase 0. Everything is a substitution or transclusion of containers that are defined in Phase 0.


    User Component Equivalences

    Users can equivocate components to others' defined components.

    If a user uses the auto-create component feature of a video site like YouTube, where the video becomes a user component defined by the video's unique embed link, then all contextual relations constructed in phase 2 CAN show up as varied perspectives on that video to others who are consuming that video.

    • users can opt in or out of accepting universal id numbers for individual videos, memes, pictures, article urls, etc.
    • Users can opt into equivocating a component to another user's component
      • persons
      • places
      • events
      • things
      • videos
      • pictures
      • sounds
      • songs
      • anything!

    Derived Meaning and Plains of Meaning

    Because components in Phase 1 can be reused in multiple stories, and contexts created in Phase 2, multiple web-maps of relationships are created on multiple plains.

    Unexpected connections can be drawn from more use of Phase 2.

    In addition to derivations of meaning occurring for multiple components defined  by one individual, derivations of commonalities and differences can be drawn between the components of different users. Users can discover similar beliefs and tastes and perspectives and insights on share, overlapping similarities.




    Phase 0: Raw Expression Phase

    This is a timeline thread of raw information input by the user.
    Phase 0 becomes much like an opt-in history of web activity and thought.
    It is essentially one long document of anything and everything that you want.
    • long text
    • headings
    • bullets
    • numbered lists
    • expanding sections
    • inserted pictures
    • tables
    • data values
    • statistics
    • pie charts
    • embedded:
      • videos
      • pictures
      • memes
      • audio
      • webpage links
      • (anything you can tweet)

    Phase 1: Modular Component Phase

    • This is unordered components of information that look and behave much like tweets.
    • This phase consists of components created from Phase 0 and web buttons, which buttons would presumably be included alongside other similar share buttons for social networks. ie: Google+, Twitter, Tumblr, Facebook
    • All components translate into references to Phase 0.
      • If data is sent directly to this phase, then it is created in Phase 0 automatically, to serve as a reference for Phase 1.