How

HOW

Floves modelling

If you view any lovely action in life, it should be easy for you to place it in any of the limited lovely expressions of life – flove(.org)

When thinking on modelling certain lovely expressions there will be layers too abstract that not need practical modellings but deeper explanations, hence the importance of the 3 Language apps proposed. 

Within the minimal set of practical floves (see them reducted here and know why here), as lower the layer (and or lovely keyword in it) is, the more concrete (and costy) will be the modelling of the proposed interactions (i.e. it is harder to be lovely with money3 than with lending2 or gifting1).

Within all possible lovely practical actions at different reduced layers, we have to be smart in choosing to focus in some minimal ones only for each of the layers.

 

Models defaults

Choose a layer (or lovely keyword), see an inviting phrase (with its childs as complementary words) to perform an action within it, edit it, save and/or send it (to a friend, network, etc)

This is the more basic, simple and consensuable default we can offer for any lovely expression of any layer. Any of the words of the phrase should refer to some set of specific clauses that can be selected for that part of the suggested action, while anyone can add their specific wills or additional information to the default lovely action-phrase and produce another outcome (or more custom phrase – action).

That was the more basic way, but that is not the only one. There are a lot of apps already doing very lovely things, but sometimes their owners don’t want to do some more lovely break-through featurings within them. So, we have to look at what there is already developed, and propose to add the more minimal additional feature to them (either in the existant app itself or in a paralel new prototype).  

A boomerang photo in instagram forwarded to facebook, which is reforwarded to Myflove there where it is better shown, stored and crawled

Flove.org and its subdomains are spaces that seek simplifications of what we would most like to create, therefore they should take into account what there is but also look beyond what there is, and without looking over their shoulder at anyone, they are places bounded to serve for new inter-project collaboration where to increase our productivity and effectiveness. So, very basically expressing it, if at some layer there is not any other platform that entangles lovelier, there flove.org should go. See as i.e. this (very poorly drafted) proposed section for improving loveliness in housing.

 

 

 

Partial entangled apps

Whatever culture, big or small action: get a part of flove for you.

Flove actions can be offered in a simpler or partial version of the whole flove model (or set of apps),  The partial apps could be distributed independently, but it also makes more perfect sense for every partial app also to be as a launcher of other partial apps.  

Flove minimal apps should be offered stand-alone and as a module at the same time, or with custom bundles that are mixing parts of different models (i.e. evil code, etc), where anyone could entangle them with the others.

So finally speaking, the very simple and big complexity flove.org should be interested in achieving, is to suggest an action that involves the featuring all the reduced lovelies from all layers.

As a demonstration for it, see the offer model, this edgy challenge for a very ambituos technical target to possibly achieve, but always think whatever big flove thing to do has to be also easily reachable from Souls main or initial app.

I first downloaded that Instashare lite for sharing things, now that is (i am!) fully entangled in MyFlove

Even if reducting all technical modelling only to the 3, 6 or 9 more practical layers of life, we still have to reduce a group of functionalities in them. There it comes the intelligence in suggesting certain minimal apps only i.e. The most minimal entanglement would be to connect the major scope to be developed (the personal being loveliness) with lovely practices of the minor layer (swap), or with the upper (freed) from its lower (offer) i.e.

For now, most of these practical models are focused in the personal twin souls matching and freed expressions developments. These first development targets are choosen for showing the importance of seeing how the layers and lovelies are entangled and are of relative importance, and because these particular personal match and material freed flove actions (within other floves) are flover than other and more easily specified than another feature from a lower layer, i.e. local trust and social freedom rationals + share and swap offers are more difficult to model and costy to implement.

See also: Review of a standlone offers implementation

 

 

MAIN PROPOSED DEVELOPMENTS

1. Language  

2. A practical example from top to bottom: Add an offer with attached souls as a wish

3. A practical example from the bottom up: Worthing a meter for expressing the different values of a thing.    

 

 

VERSION CONTROL

Develop any part, any time, for any pack

This way we will be able to make the necessary debates on the priorities more flexible and the volunteers will need less hierarchical and expensive moderations and or administrations.

 

Versiones

Cosateca 

Red (V2)

Vida (V3)

SYSTEM

     

Intentionality

Conversate

Localize

Tecnify

Development

Nuclear

Modular

Nodal

Localization

Crear nodo local

Local nodes network

Confederalism

Architecture

Centralized

Decentralized

Distributed

Aplication

Apped HTML5

Mini Apps

Entangled Apps

Data

     

Property

Own

Shared

Paid

Representation

Multilingual

Gamificada

Sinestésica

Minning

Forms

Subliminality

Multimedia

Multipublish

External

Integrated

Infinite

Documentation

Flows visualization

ChatBots

Robóts

Functionalities

     

PERSONAL

     

Reference

Activity

Profile

Profiles

Description

Text

Exportable

Biometrics

Reputation

Likes

Ratings

% of flove

LOCAL

     

Entities

Users

Agencies

Arbitration

Trusts

Comment

OwnTrust

Grants

Grups

Description

Families

Free Families

SOCIAL

     

Federation

Mediation

Integrative

Asistentialist

Comunity

Autócrata

Sections

Incomes

Formalization

Safe creative – DOI

GPL Brand

Institutional

MATERIAL

     

Extraction

Eco bolean

Meassurers

Compensators

Manufacture

Craft bolean

Projects

Crowdcrafting

OFFER

Offer of things

Oferta/request of things/services

Co-offer, Hybrids & Packs

Gift

Clausulado

Dar al común

Quick Commons redirect

Lend

Ofertante elije claúsulas

Claúsulas ideales para cosas y solicitantes

Automated accesses

Exchange

For another thing

Sell in Hours, MS, and crypto

Directed swap

 

See also:

Models

Challenge