Most important people you would like to interact with have some special characteristics and of course also interact more than other with you and vice versa.
You have easily grown to hundreds of links on Social Networks but you really want to have part of them more prominently part of your social lifestyle. We do not work at the same level on all of your linked list of people on all social networks you are on but on set of them that happen to be the one, we hope, you would like to.
Goose logically links some common operations on Social Networks as part of your social lifestyle and as such is a valuable choice but will not in any way substitute the full set of options you find on a dedicated App.
Instead Goose will concentrate of giving you additional features that later could be shared or included into the Social Networks you use. Therefore we strongly encourage to use Goose on iOS or Android where you also have the specific Social Network App installed.
Goose logically links on Social Networks and each logical Goose operation will share or act equally on all Social Networks respecting their API policies and your privacy. In this sense Goose will encourage the use of Social Networks and push the sharing of information among them. We respect your privacy beyond anything. We will not interfere, save or use information that you did not give permit to Goose or could not be freely read by one on your public profile on a Social Network.
One of such feature is a Space Time Map you may use to navigate into the dimensions of space (into the map surface) and in time (selecting the time window on which you want to look into the map).
To locate a point on a Space Time map you need a location and a time reference associated to any meaningful Social Network action Goose can read out of your Social Network channels related to you and your friends. A geo-localized Post or Tweet, a Check-In, a geo-referenced image coming from your Social Network feeds can be allocated onto a Space Time Map.
Cross Sharing in Goose is more than simply sharing the same post on multiple Social Networks. It is an integral part of the App. Take your time to watch this excerpt of features from Goose Cross Sharing.
See the Video
A Space Time Map is one of the most innovative ideas running on standard Social Network data.
Goose does much more by letting you traverse a geo map on a time bar. It gives you the ability to set a point in future time where you will be going.Find what you want to know. Discover more yourself ☺ and take your time to watch this excerpt of features from Goose Space Time Map.
See the Video
Download the newest and most complete App for going around and across Social Networks, getting the most of them by publishing and retrieving information in a single, unique App. Discover the wealth of new services built on top of common Social Networks, around you and your friends.
Goose is not another Social Network but it rather works in conjunction, above and across Social Networks to offer you the best integrated experience. However some Goose features may be interlinking users in some way. Goose will never replace an official Social Network App since it concentrate only on the most useful functions of each Social Network in your Social Networks set and to a maximum of 100 people around you. We call Goose a Meta Social Network App.
On Goose you may logically define a Social Network working set by selecting all the most important Social Networks. Once logged and activated, Goose silently will start collecting a limited amount of data referring to you and your friends by scanning all the Social Networks in your set. Goose most delicate task is to bail out across privacy, data policies, API limitations and policies: this is a very sophisticated task to be accomplished on the incoming side of Goose. On the outgoing side Goose offers Cross Sharing functionalities across all the Social Networks in the set (even if each Cross Sharing operation may just simply switch on and off Social Network channels as you like). So, to answer to this question: you activate a number of Social Networks (say 5) you want Goose to work on incoming side and Goose starts collecting your friend data and yours on those channels (Posts, Check-Ins, Tweets, Images, Like, Re-tweets, Mentions, …) and will blend all these data into a single timeline for each friend of yours. So, there are limits (one of such limit is the API limits given by the various Social Networks) but Goose has a mechanism to prevent hitting these limits. It is anyway a fact that 5 to 8 Social networks are a good guess for a Social Networks set in Goose.
You were over flooded by “a bit of” unwanted information and Facebook Edge Rank/Story Bumping/… did not help you too much and now you can’t easily read your timeline anymore. We designed the Goose App to have a limited number of close friends. We set this limit to 100. We believe people need to stay in contact and share more and more sensibly with the people they like most. So 100 is a good guess for us, no over flood, close friends and maybe more. We are giving you the chance to look over all the “Ok, come-in” you were given too easily away to select your real friends in the sense the one you care most. If you do not want to select Goose will help you with its Merge Rank (see below) to automatically select the friends you interact more across multiple Social Networks not just one of them. Since we added a specific timeline for you (the Diary) we manage 101 profiles. So the 101 Highway is your safe Social Network Highway where you run with Goose. Your 100 friends can be subdivided into Circles and we created a simple set of Circles for you and one special the Core Circle (see below).
We believed you were to say who is going to be included into the timeline you want to see. That is why we developed a more robust algorithm to guess what is going to be on your timeline based on a social metric, that is the social distance separating your friends from you. This algorithm works on a variety of data taken on social network channels (concerning your friends and you) and a set of factors associated to these data ontologies and of course the “interaction levels”. The biggest bang for the buck is to collect them on multiple Social Networks. We call this algorithm “Merge Rank” to recall the fact we work merging information from multiple Social Networks. Merge Rank works on diverse levels and for diverse topics. On one side it help defining who is “socially” closer to you and eligible to be included into the “core” circle (you have your Core definitions into the Circle/Core section of Goose and a dynamic view of the Core Circle is also available on the Universe Section of Goose) while on the other side it helps showing all the relevant data onto the only merged Timeline on the Goose HOME section (whereas all other friends timelines are simply served in chronological order).
We believed you were you would like to start from your friends when you want to see what they do, if they were active, when and where. So each friend of yours has a single timeline where to blend all the Social Network feeds from Twitter, Facebook, LinkedIn, etc. related to any “action” he did on that place. The most important thing to know is that you will see on this timeline all his/her activity on all Social Networks in your set he/she is active on, in chronological order, nothing will be missing. The only exception to single user timelines is the Home (page) Section timeline where we merge all the data, again in time order, applying also an algorithm to manage it in the most useful way for you. In this timeline we merge diverse friends activity (coming from the 101 Highway), so this is a multi-user timeline.
Of course they can and this is one of the very powerful thing to know! We do not require your friends to have Goose. We will give them the option to see what benefit they would have by using Goose anyway. Let analyze a simple case where one friend of yours “Foo” is on Twitter and on Facebook. First “Foo” will appear in Goose as a single friend known on two Social Network channels (Twitter, Facebook) on your Contact section. You can interact with “Foo” directly on Facebook or Twitter by just using one of the icons at the top on the Contact Section/”Foo” and this is straight forward. So one way is to use the official App or Web site through the Goose App on the Contact section. Another way is to select the Timeline icon and use Goose for interacting with them. Let’s see from “Foo” perspective. “Foo” uses the Facebook App and post something then Twitter for tweeting something else mentioning @you and you will see both interactions later on his specific blended timeline on Goose an the tweet as well on your Diary since it directly concerns you. So Foo(Twitter, Facebook) can easily interact with you on both channels even if he/her does not use Goose and you will see all his/her action as part of the “Foo”’s integral timeline. Additionally, if “Foo” is aware of the #tags and /commands mechanism he/she can as well interact on all the newer and higher level services instantiated through Goose.
We believed you would like to have, close around you, the set of friends that are interacting more with you, so the Core Circle is made by the people who normally interact more often with you (as seen over the full active set of Social Network you enabled under Goose). Of course you can decide to include or exclude people from the Core regardless from the fact that Goose might think they should be in (and this is done through aspects covered by the Merge Rank). In this case Goose takes note that these people are included or excluded by you and will not exclude or include them anymore. People into the Core Circle will have special features enabled to interact more with you through Goose and also will be have a special place in the Universe and Social Life Style sections of Goose. Within the Goose Core Circle, depending on the distance metric, we distinguish close, near and far zones that might enable additional tailoring capabilities, on Goose, in future.
3 p.m. – where will you go tonight? I will be at Ravi’s Inn at 9 p.m. Let your friend know. Take Goose and Cross Share the text “I will be at Ravi’s Inn at 9 p.m. Join me if you like!” checking in at “Ravi’s Inn” Facebook (Place Id) and Foursquare (Venue Id). Goose Cross Sharing will send a Post on Facebook a tweet on Twitter and record Place Id and Venue Id onto the Goose Server along with the date and time for you. If you and your friends are using Goose they will see you on the Space Time Map in the future at 9 pm at Ravi’s Inn location onto the map (just sliding the map in the future, swiping the time bar to the right [although they could have been searching for you on the map or got to know that by being notified on the Home page). If they search you or if they ask a PATH of your check-ins they will know that as well. Additionally if they are in your Core Circle they will get notified onto their Home Section. When it’s 9 pm and you or any of your friends are close to the location it is also possible to check in with Facebook, Foursquare or with Goose (multiple check-ins in a single operation). Casual events are simply indications that you will be somewhere sometime in the future. They are simply created by using Cross Sharing a message with a location and with a future time/date. In particular they are activated as soon as a future check-in will be recorded on the Goose Server during a Cross Sharing operation. Future check-ins are a simple way to forward an indication of where you will be into the future. Casual Events also add some side information like people attending (as soon as they indicate they will join) and reason why you are going out in a very simple way. So people using Goose will have a complete understanding of where people are going and when (using the Space Time Map and searching for people, places or just spotting items on the map). How about people not using Goose? How they can interact with you and say something like “Yes I am coming too” on a tweet and have Goose to update the attendees list? By using “/” (slash) commands into their tweet or post (see “Slash” commands). “/” Commands are an equivalent of the #tags but oriented to define actions related to a hash-tag (see the section Slash Commands for a detailed explanation). People can start using /commands on their posts or tweets without changing the meaning of the message but Apps capable of interpreting that logic will act accordingly. When you do a future check-in a Casual Event tag is created (i.e.) #Goose_12345678 and your post or tweet is extended automatically as “#Goose_12345678 I will be at Ravi’s Inn at 9 p.m. Join me if you like!”. Therefore your friends on Twitter could reply with a “#Goose_12345678 I will /join” tweet. Since Goose creates also a Twitter hash-tag #Goose_12345678 people on Twitter can follow that hash-tag too by using any hash-tag capable App. Goose is capable of properly interpreting this tweet and update the attendees list of that casual event. The result is that you and all your friends on Goose will then know who will be going there too. Now you know you can /join and /disengage (with a tweet) from a Casual Event and much more using “/” commands. Casual Events are a good example of intermixing interactions between Goose and non-Goose Apps cooperating to create higher value services.
Goose is retrieving data across Social Networks within the limits and the policies imposed by these channels. Goose caches some data (for a limited time and within the respective policies) on your behalf ONLY on your mobile device. No data acquired by Social Networks is saved on the Goose Server. Social Network data cached on your behalf on your device is under your control and nevertheless cached data undergoes a periodic aging procedure to comply with the limited space we use on your device for this purpose. Goose saves at Goose Server only data to enable newer and on top services, which cannot be driven directly only using the official Social Network channels.
Slash commands or slash instructions (“/”) are a generic mean just like hash-tags and are just a nice way to easily insert in-text commands to be interpreted by any application capable of doing so and Goose is the first one. For instance a text from Mr. Stark “Hello, I am Iron Man. /fb:incl:It’s good to be back/” will tell Goose (like any any App understanding “/”s) managing a Post to multiple social networks to include the string “It’s good to be back” only when posting on Facebook. Another use of the “/” instruction is when used together with named #tags released by the Hash-tags Authority, like “#Goose_12345678 (where “Goose” represents the local Authority name tag and 12345678 is an identifier tag known internally to the Goose Authority). The underscore sign is used as a separator accepted by the hashtag naming convention. For instance when the text to be posted contains “#Goose_12345678 like to /join” any App reading the post could infer that the person posting will join the 12345678 Unique Object ID (UOID) issued by Goose which turns to be a casual event located in 3786 Ingraham St. San Diego, CA 92109 at the Rocky’s Crown Pub in San Diego. This App (as Goose does) may therefore update the list of attendees of the “#Goose_12345678” casual event. In this case the / command has a scope beyond the in-text and it is related to the App capable of interpreting / commands for higher level services.
In this case to complete the example, “Goose” as a local hashtag domain authority for the hashtag name “Goose” was registered at the general and well known hashtag authority:
So at hashtag-authority.org there will be a correspondence:
→ Authority:#Goose, Name:@Goose, Web-url:goose-app.com, Mail:firstname.lastname@example.org, iOS:goose, Android:goose, … and all the related ontologies
Therefore and consequently there will be other correspondences at:
→UOID: #Goose_12345678, Type:”Casual Event”, Location:”3786 Ingraham St. San Diego, CA 92109”, Place:”Rocky’s Crown”, Date: … and all the related ontologies (e.g. including Server description and API call for querying)
The local (Goose) hashtag-authority is responsible to maintain uniqueness among its OIDs. This property and the above url is good for all applications that want to cooperate on that UOID.
Since this UOID is specific to Goose the Goose Server will be instructed by the Goose App to do more. The Goose Server, will keep track on its database of this UOID and record all the related actions happening on that Casual Event – that is /join /disengage happening before “Date” and /check-in /leave happening while the Casual Event is started issued by Cross Sharing between all the Goose App or generic Apps using both the #Goose_12345678 and the /join (for instance) command.
There are a number of well known / instructions (or commands) which should be implemented (but you do not have to) while all the rest are free on their usage. Here follow a simple list yet not exhaustive since there are quite free. / Instructions have to be managed by the respective domain authority to which they belong.
Here follows an in-text Slash instructions simple list (the words instruction and command can be interchangeably used in the / context). Alongside each instruction we have inserted enclosed into curved brackets a qualifier to highlight the effect of the instruction, whether it is a text expansion or a distant action (see the list below). Although in-text is a very general concept, here you find the current in-text commands (instructions) accepted by Goose Cross-Sharing in-text. These Goose in-text are subdivided into the following four types:
/ Instructions related to text creation, image attachment, local actions, posting and forwarding
For additional info on / commands see the related API and APP documentation.
Goose App has been developed by Clouds Opera S.r.l. and sponsored by Sardegna Ricerche