text:
Q: How to add soap basic auth request to WSDL How can I had soap AUTH BASIC auth to a WSDL, so who ever reads the WSDL knows I require that operation for a specific method ?

A: Using the example bellow I have managed to pass the SOAP basic autentication to the php webservice on the other end.
The PHP.net/Soapclient has a simple working example, but in csharp I found this link to be a solution to my problem.
link
Michaelis.MockService is the Webservice library extracted you may see an example on how to do this in:
link Mono project website.
Michaelis.MockService service = new Michaelis.MockService();

// Create the network credentials and assign
// them to the service credentials
NetworkCredential netCredential = new NetworkCredential("Inigo.Montoya", "Ykmfptd");
Uri uri = new Uri(service.Url);
ICredentials credentials = netCredential.GetCredential(uri, "Basic");
service.Credentials = credentials;

// Be sure to set PreAuthenticate to true or else
// authentication will not be sent.
service.PreAuthenticate = true;

// Make the web service call.
service.Method();

A: There is no way to specify this, as far as I know.


Chief Minister of Uttar Pradesh Yogi Adityanath is most searched CM across The Country. Yogi Adityanath is ahead of Other CM of BJP Including Madya Pradesh CM Shivraj Singh Chauhan, Rajasthan CM Vasundhara Raje Scindia, and Goa CM Manohar Parrikar, Gujarat CM Vijay Rupani.
Yogi Adityanath is also ahead of Uttar Pradesh's Two Former CM supremo Mayawati and Akhilesh Yadav.
This Google trend Shows The popularity chart of the Yogi Adityanath. He appointed as Chief Minister on 26 March 2017. After that BJP won the state assembly elections.
As per Google Trends, 70% of searches were targeted at Yogi Adityanath.


My daughter is a supe rhero. She goes by the alias "Super Ruby Princessa" which has a touch of her Swedish/American bilingualism in the name. I think often about my daughter's curly blonde hair (maternal grandma's), her blue eyes (paternal grandfather's), her oh-so-tannable skin (maternal grandpa's) and so on. But I've only recently discovered the lineage of her super-heroine powers. She got this from me! Her Mom! I'm a superhero.
Doulas are peacemakers, miracle workers, superheros. Just our very presence in the world, make the world a safer, more peaceful place. So we are a lot like Wonder Woman.
So, why I am I a doula? Well, for no less greater cause than saving the world.
You may need to be a little familiar with 70′s American Saturday morning TV (or Marvel comic books) to get this metaphor, but Eat, Pray, Doula in Bali, was a lot like a gathering of the Justice League in a tropical place with organic, locally produced food and homemade ice-cream. Debra Pascali-Bonero, Katherine Bramhall, and Ibu Robin Lim, the more seasoned Super-heros lending some expertise to us novice, very enthusiastic, but perhaps not-quite-in-total-control-of-our-powers yet newbies on the Superhero scene.
Yes, to take the metaphor further, there is in fact a bat doula and Debra (or Bat Girl???) will tell you all about it at the Eat, Pray, Doula Workshop.
Actually, it's Katherine who drives a moped…perhaps she is Bat Girl!?
And the fact is, Ibu Robin's name is Robin…a coincidence? I think not!
On one of first adventures together, the newly initiated – myself and my three Wonder Twins (so we are Wonder Quadruplets in this case), Anita, Chrissy, and Alison find ourselves in the parallel universe of Bumi Sehat Birthing Clinic on Nyepi, the Balinese New Year – the Day of Silence. No one, not even a superhero, may be in the streets on Nyepi or else the evil spirits (think Legion of Doom) will make life on Bali really difficult the following year and none of us are willing to take that chance. Besides some super doulas must be at the clinic if any birthing moms show up (birthing moms on the back of mopeds are invisible to the evil spirits).
Anita Wonder Twin and 1st Doula-on-call: Form of loving, creative, continuous, non-tiring support for mama!
Chrissy Wonder Twin: Shape of water bucket!
Alison Wonder Twin: Form of hot water!
Amy Wonder Twin: Shape of water transport!
Success – in short, we harness our powers, dodge the Legion of Doom, and Anita doulas a gentle birth. One more step toward saving the world!
I thank my children and all my super doula sisters from Eat, Pray, Doula 2012 (especially Katherine, Debra and Robin) for inspiring and guiding me to focus my natural superhero qualities in such a meaningful way. And thanks to Anita for the super Bamboo clothing tip. Note to self: Synthetics+Tropics=Bad.
Love you all! And love to all future EPD attendees.
Building peace, one Mother, one Baby at a time.
Amy is a doula and practices hypnobirthing in Sweden. Read her birth story of baby Henry on #obirth or visit her at www.amyneuhedel.com/thecord.
Recently I attended the Eat Pray Doula, DONA approved Birth Doula Training in Ubud, Bali facilitated by Katherine Bramhall, Debra Pascali-Bonaro, and Robin Lim. This week-long training included birth doula education, postpartum care, childbirth education and breastfeeding support. The skills to become an effective birth doula were definitely the goal of the training, but what I was not prepared for was the adventure of sisterhood and connection that would happen in merely a week.
This trip to Bail, Indonesia was filled with "firsts": my 1st international flight, my 1st time using a passport, my 1st time walking through a "monkey forest" and my 1st time being on a global stage talking about the benefits of breast milk! Yes, the latter was a 1st for me and I have had many opportunities to share the benefits of breast milk in various settings.
On March 22 several of the EPD birth keepers and I attended the 7th Annual Bali Spirit festival. When we arrived, we settled in to watch the local entertainers. When they finished performing, the crew began setting up for the next performers. To pass time, the MC came to the on stage and began to share some "interesting facts." He began his chatter with a statement about kids and parents and eye color….interesting, but nothing mind-blowing. Then the gavel landed and he stated his fact that coconut water had the same ingredients as breast milk minus one thing….breast milk contained magnesium! I gasped! The other birth keepers gasped! We immediately went into a frenzy telling everyone around us that that was not accurate information that that there is absolutely no comparison of breast milk and coconut water in terms of beneficial properties to a baby's needs and development!
I quickly ran toward the stage and engaged him in a dialogue about how making a statement, as a fact, could have grave ramifications on the efforts to get indigenous women to breastfeed. If women feel that breast milk and coconut water are equivalents, then they may feel no NEED to BREASTFEED! They could simply contend with coconut water, which is in abundance in Bali. Also, I shared two (2) KEY/ESSENTIAL ingredients that are in breast milk that could NEVER be in coconut water. We exchanged some relevant conversation and he asked me if I would like to grace the stage and share the FACTS about breast milk that I had so enlightened him on.
First, breast milk contains antibodies. Any foreign object that has ever been in mom's blood stream OR any bacteria or virus that she's ever been exposed to, her blood and plasma cells created antibodies to neutralize them. Thus, those antibodies are present in breast milk and colostrum. Babies that get mother's milk, get their 1st immunization to help build a healthy immune system and strengthen their sensitive little digestive systems with enzymes and antibodies to fight infection and bacteria. Second, breast milk contains human stems cells. These stem cells are life-saving; and, can possibly repair damaged, little organs due to the replication of the stem cells to build tissue and new cells. Human embryonic stem cells are very widely studied for their limitless regenerative properties and the ability to have specialized function in the new cells they produce.
Well, since coconuts are not human and do not have a blood stream, these are 2 very distinct and useful properties (not to mention that there are hundreds of other ingredients with benefits in breast milk that have yet to be identified) contained in breast milk that can never be in coconut water.
I finished my enlightenment opportunity with a lively chant: THE BREAST IS BEST! THE BREAST IS BEST! Empower the women in your life to breastfeed, because coconut water just won't do it!
Learn how you can join the magic in Bali for Doula or Advanced Birthworker Workshop at Eat Pray Doula!
Biography: Nikia Lawson is the owner/operator of Birth Blessings Professional Birth and Doula Services, owner/Project Director of The Natural Way Birthing Project ~ Ft. Worth, and managing partner of Tarrant County Doula Associates. Nikia's goal is to empower women to know that they are divinely designed to give birth; to learn to trust their bodies and listen to their inner spirit as they embark on their birth journey.
Nikia is a DONA birth doula, a 2010 DONA International Doula of Color Fellow and a DONA International approved, birth doula trainer and is an experienced childbirth educator and has taught classes for various community groups and hospitals since 2007. Nikia hopes to return to school complete her post graduate studies in Naturopathy and open her own maternity home for pregnant women.
Learn how you can join the magic in Bali at Eat Pray Doula!


Amazingly beautiful wallpapers made just for the new iPad Retina Display! An image search made just for images fitting the iPad Retina display! Thousands of possibilities!
Thousands upon Thousands of wallpapers made specifically for the new iPad's amazing 2048x1536 display! Your new iPad will looking amazing with these incredibly high quality wallpapers!
Retina Wallpapers allows you to search for any type of wallpaper you like, not just browsing set categories like other apps! It's like an Image Search specifically for amazing HD wallpapers!
This app is also compatible with the original iPad and iPad 2, with a setting to get results for those screen sizes as well.


text:
local uielement = hs.uielement  -- Make sure parent module loads
local application = require "hs.application.internal"
application.watcher = require "hs.application.watcher"
package.loaded['hs.application']=application --preload application so it can be fully required by window
local window = require "hs.window"
local timer = require "hs.timer"
local settings = require "hs.settings"

local alternateNameMap = {}
local spotlightEnabled = settings.get("HSenableSpotlightForNameSearches")

-- internal search tool for alternate names
local realNameFor = function(value, exact)
    if type(value) ~= "string" then
        error('hint must be a string', 2)
    end
    if not exact then
        local results = {}
        for k, v in pairs(alternateNameMap) do
            if k:lower():find(value:lower()) then
                -- I can foresee someday wanting to know how often a match was found, so make it a
                -- number rather than a boolean so I can cut & paste this
                results[v] = (results[v] or 0) + 1
            end
        end
        local returnedResults = {}
        for k,v in pairs(results) do
            table.insert(returnedResults, k:match("^(.*)%.app$") or k)
        end
        return table.unpack(returnedResults)
    else
        local realName = alternateNameMap[value]
        -- hs.application functions/methods do not like the .app at the end of application
        -- bundles, so remove it.
        return realName and realName:match("^(.*)%.app$") or realName
    end
end

local type,pairs,ipairs=type,pairs,ipairs
local tunpack,tpack,tsort=table.unpack,table.pack,table.sort

--- hs.application:visibleWindows() -> win[]
--- Method
--- Returns only the app's windows that are visible.
---
--- Parameters:
---  * None
---
--- Returns:
---  * A table containing zero or more hs.window objects
function application:visibleWindows()
  local r={}
  if self:isHidden() then return r -- do not check :isHidden for every window
  else for _,w in ipairs(self:allWindows()) do if not w:isMinimized() then r[#r+1]=w end end end
  return r
end

--- hs.application:activate([allWindows]) -> bool
--- Method
--- Tries to activate the app (make its key window focused) and returns whether it succeeded; if allWindows is true, all windows of the application are brought forward as well.
---
--- Parameters:
---  * allWindows - If true, all windows of the application will be brought to the front. Otherwise, only the application's key window will. Defaults to false.
---
--- Returns:
---  * A boolean value indicating whether or not the application could be activated
function application:activate(allWindows)
  allWindows=allWindows and true or false
  if self:isUnresponsive() then return false end
  local win = self:_focusedwindow()
  if win then
    return win:becomeMain() and self:_bringtofront(allWindows)
  else
    return self:_activate(allWindows)
  end
end

--- hs.application:name()
--- Method
--- Alias for `hs.application:title()`
application.name=application.title

--- hs.application.get(hint) -> hs.application object
--- Constructor
--- Gets a running application
---
--- Parameters:
---  * hint - search criterion for the desired application; it can be:
---    - a pid number as per `hs.application:pid()`
---    - a bundle ID string as per `hs.application:bundleID()`
---    - an application name string as per `hs.application:name()`
---
--- Returns:
---  * an hs.application object for a running application that matches the supplied search criterion, or `nil` if not found
---
--- Notes:
---  * see also `hs.application.find`
function application.get(hint)
  return tpack(application.find(hint,true),nil)[1] -- just to be sure, discard extra results
end

--- hs.application.find(hint) -> hs.application object(s)
--- Constructor
--- Finds running applications
---
--- Parameters:
---  * hint - search criterion for the desired application(s); it can be:
---    - a pid number as per `hs.application:pid()`
---    - a bundle ID string as per `hs.application:bundleID()`
---    - a string pattern that matches (via `string.find`) the application name as per `hs.application:name()` (for convenience, the matching will be done on lowercased strings)
---    - a string pattern that matches (via `string.find`) the application's window title per `hs.window:title()` (for convenience, the matching will be done on lowercased strings)
---
--- Returns:
---  * one or more hs.application objects for running applications that match the supplied search criterion, or `nil` if none found
---
--- Notes:
---  * If multiple results are found, this function will return multiple values. See [https://www.lua.org/pil/5.1.html](https://www.lua.org/pil/5.1.html) for more information on how to work with this
---  * for convenience you can call this as `hs.application(hint)`
---  * use this function when you don't know the exact name of an application you're interested in, i.e.
---    from the console: `hs.application'term' --> hs.application: iTerm2 (0x61000025fb88)  hs.application: Terminal (0x618000447588)`.
---    But be careful when using it in your `init.lua`: `terminal=hs.application'term'` will assign either "Terminal" or "iTerm2" arbitrarily (or even,
---    if neither are running, any other app with a window that happens to have "term" in its title); to make sure you get the right app in your scripts,
---    use `hs.application.get` with the exact name: `terminal=hs.application.get'Terminal' --> "Terminal" app, or nil if it's not running`
---
--- Usage:
--- -- by pid
--- hs.application(42):name() --> Finder
--- -- by bundle id
--- hs.application'com.apple.Safari':name() --> Safari
--- -- by name
--- hs.application'chrome':name() --> Google Chrome
--- -- by window title
--- hs.application'bash':name() --> Terminal
local findSpotlightWarningGiven = false
function application.find(hint,exact)
  if hint==nil then return end
  local typ=type(hint)
  if typ=='number' then return application.applicationForPID(hint)
  elseif typ~='string' then error('hint must be a number or string',2) end
  local r=application.applicationsForBundleID(hint)
  if #r>0 then return tunpack(r) end
  local apps=application.runningApplications()

  if exact then for _,a in ipairs(apps) do if a:name()==hint then r[#r+1]=a end end
  else for _,a in ipairs(apps) do local aname=a:name() if aname and aname:lower():find(hint:lower()) then r[#r+1]=a end end end

  if spotlightEnabled then
      for _, v in ipairs(table.pack(realNameFor(hint, exact))) do
          for _, a in ipairs(apps) do
              if a:name() ~= nil and v:lower() == a:name():lower() then
                  r[#r+1]=a
              end
          end
      end
  elseif type(spotlightEnabled) == "nil" and not findSpotlightWarningGiven then
      findSpotlightWarningGiven = true
      print("-- Some applications have alternate names which can also be checked if you enable Spotlight support with `hs.application.enableSpotlightForNameSearches(true)`.")
  end

  tsort(r,function(a,b)return a:kind()>b:kind()end) -- gui apps first
  if exact or #r>0 then return tunpack(r) end

  r=tpack(window.find(hint))
  local rs={} for _,w in ipairs(r) do rs[w:application()]=true end -- :toSet
  for a in pairs(rs) do r[#r+1]=a end -- and back, no dupes
  if #r>0 then return tunpack(r) end
end

--- hs.application:findWindow(titlePattern) -> hs.window object(s)
--- Method
--- Finds windows from this application
---
--- Parameters:
---  * titlePattern - a string pattern that matches (via `string.find`) the window title(s) as per `hs.window:title()` (for convenience, the matching will be done on lowercased strings)
---
--- Returns:
---  * one or more hs.window objects belonging to this application that match the supplied search criterion, or `nil` if none found

function application:findWindow(hint)
  return window.find(hint,false,self:allWindows())
end

--- hs.application:getWindow(title) -> hs.window object
--- Method
--- Gets a specific window from this application
---
--- Parameters:
---  * title - the desired window's title string as per `hs.window:title()`
---
--- Returns:
---  * the desired hs.window object belonging to this application, or `nil` if not found
function application:getWindow(hint)
  return tpack(window.find(hint,true,self:allWindows()),nil)[1]
end

--- hs.application.open(app[, wait, [waitForFirstWindow]]) -> hs.application object
--- Constructor
--- Launches an application, or activates it if it's already running
---
--- Parameters:
---  * app - a string describing the application to open; it can be:
---    - the application's name as per `hs.application:name()`
---    - the full path to an application on disk (including the `.app` suffix)
---    - the application's bundle ID as per `hs.application:bundleID()`
---  * wait - (optional) the maximum number of seconds to wait for the app to be launched, if not already running; if omitted, defaults to 0;
---   if the app takes longer than this to launch, this function will return `nil`, but the app will still launch
---  * waitForFirstWindow - (optional) if `true`, additionally wait until the app has spawned its first window (which usually takes a bit longer)
---
--- Returns:
---  * the `hs.application` object for the launched or activated application; `nil` if not found
---
--- Notes:
---  * the `wait` parameter will *block all Hammerspoon activity* in order to return the application object "synchronously"; only use it if you
---    a) have no time-critical event processing happening elsewhere in your `init.lua` and b) need to act on the application object, or on
---    its window(s), right away
---  * when launching a "windowless" app (background daemon, menulet, etc.) make sure to omit `waitForFirstWindow`
function application.open(app,wait,waitForWindow)
  if type(app)~='string' then error('app must be a string',2) end
  if wait and type(wait)~='number' then error('wait must be a number',2) end
  local r=application.launchOrFocus(app) or application.launchOrFocusByBundleID(app)
  if not r then return end
  r=nil
  wait=(wait or 0)*1000000
  local CHECK_INTERVAL=100000
  repeat
    r=r or application.get(app)
    if r and (not waitForWindow or r:mainWindow()) then return r end
    timer.usleep(math.min(wait,CHECK_INTERVAL)) wait=wait-CHECK_INTERVAL
  until wait<=0
  return r
end

--- hs.application.menuGlyphs
--- Variable
--- A table containing UTF8 representations of the defined key glyphs used in Menus for keybaord shortcuts which are presented pictorially rather than as text (arrow keys, return key, etc.)
---
--- These glyphs are indexed numerically where the numeric index matches a possible value for the AXMenuItemCmdGlyph key of an entry returned by `hs.application.getMenus`.  If the AXMenuItemCmdGlyph field is non-numeric, then no glyph is used in the presentation of the keyboard shortcut for a menu item.
---
--- The following glyphs are defined:
---  * "⇥",  -- kMenuTabRightGlyph, 0x02, Tab to the right key (for left-to-right script systems)
---  * "⇤",  -- kMenuTabLeftGlyph, 0x03, Tab to the left key (for right-to-left script systems)
---  * "⌤",   -- kMenuEnterGlyph, 0x04, Enter key
---  * "⇧",  -- kMenuShiftGlyph, 0x05, Shift key
---  * "⌃",   -- kMenuControlGlyph, 0x06, Control key
---  * "⌥",  -- kMenuOptionGlyph, 0x07, Option key
---  * "␣",    -- kMenuSpaceGlyph, 0x09, Space (always glyph 3) key
---  * "⌦",  -- kMenuDeleteRightGlyph, 0x0A, Delete to the right key (for right-to-left script systems)
---  * "↩",  -- kMenuReturnGlyph, 0x0B, Return key (for left-to-right script systems)
---  * "↪",  -- kMenuReturnR2LGlyph, 0x0C, Return key (for right-to-left script systems)
---  * "",   -- kMenuPencilGlyph, 0x0F, Pencil key
---  * "↓",   -- kMenuDownwardArrowDashedGlyph, 0x10, Downward dashed arrow key
---  * "⌘",  -- kMenuCommandGlyph, 0x11, Command key
---  * "✓",   -- kMenuCheckmarkGlyph, 0x12, Checkmark key
---  * "⃟",   -- kMenuDiamondGlyph, 0x13, Diamond key
---  * "",   -- kMenuAppleLogoFilledGlyph, 0x14, Apple logo key (filled)
---  * "⌫",  -- kMenuDeleteLeftGlyph, 0x17, Delete to the left key (for left-to-right script systems)
---  * "←",  -- kMenuLeftArrowDashedGlyph, 0x18, Leftward dashed arrow key
---  * "↑",   -- kMenuUpArrowDashedGlyph, 0x19, Upward dashed arrow key
---  * "→",   -- kMenuRightArrowDashedGlyph, 0x1A, Rightward dashed arrow key
---  * "⎋",  -- kMenuEscapeGlyph, 0x1B, Escape key
---  * "⌧",  -- kMenuClearGlyph, 0x1C, Clear key
---  * "『",  -- kMenuLeftDoubleQuotesJapaneseGlyph, 0x1D, Unassigned (left double quotes in Japanese)
---  * "』",  -- kMenuRightDoubleQuotesJapaneseGlyph, 0x1E, Unassigned (right double quotes in Japanese)
---  * "␢",   -- kMenuBlankGlyph, 0x61, Blank key
---  * "⇞",   -- kMenuPageUpGlyph, 0x62, Page up key
---  * "⇪",  -- kMenuCapsLockGlyph, 0x63, Caps lock key
---  * "←",  -- kMenuLeftArrowGlyph, 0x64, Left arrow key
---  * "→",   -- kMenuRightArrowGlyph, 0x65, Right arrow key
---  * "↖",  -- kMenuNorthwestArrowGlyph, 0x66, Northwest arrow key
---  * "﹖",  -- kMenuHelpGlyph, 0x67, Help key
---  * "↑",   -- kMenuUpArrowGlyph, 0x68, Up arrow key
---  * "↘",  -- kMenuSoutheastArrowGlyph, 0x69, Southeast arrow key
---  * "↓",   -- kMenuDownArrowGlyph, 0x6A, Down arrow key
---  * "⇟",   -- kMenuPageDownGlyph, 0x6B, Page down key
---  * "",  -- kMenuContextualMenuGlyph, 0x6D, Contextual menu key
---  * "⌽",  -- kMenuPowerGlyph, 0x6E, Power key
---  * "F1",  -- kMenuF1Glyph, 0x6F, F1 key
---  * "F2",  -- kMenuF2Glyph, 0x70, F2 key
---  * "F3",  -- kMenuF3Glyph, 0x71, F3 key
---  * "F4",  -- kMenuF4Glyph, 0x72, F4 key
---  * "F5",  -- kMenuF5Glyph, 0x73, F5 key
---  * "F6",  -- kMenuF6Glyph, 0x74, F6 key
---  * "F7",  -- kMenuF7Glyph, 0x75, F7 key
---  * "F8",  -- kMenuF8Glyph, 0x76, F8 key
---  * "F9",  -- kMenuF9Glyph, 0x77, F9 key
---  * "F10", -- kMenuF10Glyph, 0x78, F10 key
---  * "F11", -- kMenuF11Glyph, 0x79, F11 key
---  * "F12", -- kMenuF12Glyph, 0x7A, F12 key
---  * "F13", -- kMenuF13Glyph, 0x87, F13 key
---  * "F14", -- kMenuF14Glyph, 0x88, F14 key
---  * "F15", -- kMenuF15Glyph, 0x89, F15 key
---  * "⎈",  -- kMenuControlISOGlyph, 0x8A, Control key (ISO standard)
---  * "⏏",   -- kMenuEjectGlyph, 0x8C, Eject key (available on Mac OS X 10.2 and later)
---  * "英数", -- kMenuEisuGlyph, 0x8D, Japanese eisu key (available in Mac OS X 10.4 and later)
---  * "かな", -- kMenuKanaGlyph, 0x8E, Japanese kana key (available in Mac OS X 10.4 and later)
---  * "F16", -- kMenuF16Glyph, 0x8F, F16 key (available in SnowLeopard and later)
---  * "F17", -- kMenuF16Glyph, 0x90, F17 key (available in SnowLeopard and later)
---  * "F18", -- kMenuF16Glyph, 0x91, F18 key (available in SnowLeopard and later)
---  * "F19", -- kMenuF16Glyph, 0x92, F19 key (available in SnowLeopard and later)
---
--- Notes:
---  * a `__tostring` metamethod is provided for this table so you can view its current contents by typing `hs.application.menuGlyphs` into the Hammerspoon console.
---  * This table is provided as a variable so that you can change any representation if you feel you know of a better or more appropriate one for you usage at runtime.
---
---  * The glyphs provided are defined in the Carbon framework headers in the Menus.h file, located (as of 10.11) at /System/Library/Frameworks/Carbon.framework/Frameworks/HIToolbox.framework/Headers/Menus.h.
---  * The following constants are defined in Menus.h, but do not seem to correspond to a visible UTF8 character or well defined representation that I could discover.  If you believe that you know of a (preferably sanctioned by Apple) proper visual representation, please submit an issue detailing it at the Hammerspoon repository on Github.
---    * kMenuNullGlyph, 0x00, Null (always glyph 1)
---    * kMenuNonmarkingReturnGlyph, 0x0D, Nonmarking return key
---    * kMenuParagraphKoreanGlyph, 0x15, Unassigned (paragraph in Korean)
---    * kMenuTrademarkJapaneseGlyph, 0x1F, Unassigned (trademark in Japanese)
---    * kMenuAppleLogoOutlineGlyph, 0x6C, Apple logo key (outline)
application.menuGlyphs = setmetatable({
  [2] = "⇥",     -- kMenuTabRightGlyph, 0x02, Tab to the right key (for left-to-right script systems)
  [3] = "⇤",     -- kMenuTabLeftGlyph, 0x03, Tab to the left key (for right-to-left script systems)
  [4] = "⌤",     -- kMenuEnterGlyph, 0x04, Enter key
  [5] = "⇧",     -- kMenuShiftGlyph, 0x05, Shift key
  [6] = "⌃",     -- kMenuControlGlyph, 0x06, Control key
  [7] = "⌥",     -- kMenuOptionGlyph, 0x07, Option key
  [9] = "␣",      -- kMenuSpaceGlyph, 0x09, Space (always glyph 3) key
  [10] = "⌦",    -- kMenuDeleteRightGlyph, 0x0A, Delete to the right key (for right-to-left script systems)
  [11] = "↩",    -- kMenuReturnGlyph, 0x0B, Return key (for left-to-right script systems)
  [12] = "↪",    -- kMenuReturnR2LGlyph, 0x0C, Return key (for right-to-left script systems)
  [15] = "",    -- kMenuPencilGlyph, 0x0F, Pencil key
  [16] = "↓",     -- kMenuDownwardArrowDashedGlyph, 0x10, Downward dashed arrow key
  [17] = "⌘",    -- kMenuCommandGlyph, 0x11, Command key
  [18] = "✓",     -- kMenuCheckmarkGlyph, 0x12, Checkmark key
  [19] = "◇",     -- kMenuDiamondGlyph, 0x13, Diamond key
  [20] = "",     -- kMenuAppleLogoFilledGlyph, 0x14, Apple logo key (filled)
  [23] = "⌫",    -- kMenuDeleteLeftGlyph, 0x17, Delete to the left key (for left-to-right script systems)
  [24] = "←",    -- kMenuLeftArrowDashedGlyph, 0x18, Leftward dashed arrow key
  [25] = "↑",     -- kMenuUpArrowDashedGlyph, 0x19, Upward dashed arrow key
  [26] = "→",     -- kMenuRightArrowDashedGlyph, 0x1A, Rightward dashed arrow key
  [27] = "⎋",    -- kMenuEscapeGlyph, 0x1B, Escape key
  [28] = "⌧",    -- kMenuClearGlyph, 0x1C, Clear key
  [29] = "『",    -- kMenuLeftDoubleQuotesJapaneseGlyph, 0x1D, Unassigned (left double quotes in Japanese)
  [30] = "』",    -- kMenuRightDoubleQuotesJapaneseGlyph, 0x1E, Unassigned (right double quotes in Japanese)
  [97] = "␢",     -- kMenuBlankGlyph, 0x61, Blank key
  [98] = "⇞",     -- kMenuPageUpGlyph, 0x62, Page up key
  [99] = "⇪",    -- kMenuCapsLockGlyph, 0x63, Caps lock key
  [100] = "←",   -- kMenuLeftArrowGlyph, 0x64, Left arrow key
  [101] = "→",    -- kMenuRightArrowGlyph, 0x65, Right arrow key
  [102] = "↖",   -- kMenuNorthwestArrowGlyph, 0x66, Northwest arrow key
  [103] = "﹖",   -- kMenuHelpGlyph, 0x67, Help key
  [104] = "↑",    -- kMenuUpArrowGlyph, 0x68, Up arrow key
  [105] = "↘",   -- kMenuSoutheastArrowGlyph, 0x69, Southeast arrow key
  [106] = "↓",    -- kMenuDownArrowGlyph, 0x6A, Down arrow key
  [107] = "⇟",    -- kMenuPageDownGlyph, 0x6B, Page down key
  [109] = "",   -- kMenuContextualMenuGlyph, 0x6D, Contextual menu key
  [110] = "⌽",   -- kMenuPowerGlyph, 0x6E, Power key
  [111] = "F1",   -- kMenuF1Glyph, 0x6F, F1 key
  [112] = "F2",   -- kMenuF2Glyph, 0x70, F2 key
  [113] = "F3",   -- kMenuF3Glyph, 0x71, F3 key
  [114] = "F4",   -- kMenuF4Glyph, 0x72, F4 key
  [115] = "F5",   -- kMenuF5Glyph, 0x73, F5 key
  [116] = "F6",   -- kMenuF6Glyph, 0x74, F6 key
  [117] = "F7",   -- kMenuF7Glyph, 0x75, F7 key
  [118] = "F8",   -- kMenuF8Glyph, 0x76, F8 key
  [119] = "F9",   -- kMenuF9Glyph, 0x77, F9 key
  [120] = "F10",  -- kMenuF10Glyph, 0x78, F10 key
  [121] = "F11",  -- kMenuF11Glyph, 0x79, F11 key
  [122] = "F12",  -- kMenuF12Glyph, 0x7A, F12 key
  [135] = "F13",  -- kMenuF13Glyph, 0x87, F13 key
  [136] = "F14",  -- kMenuF14Glyph, 0x88, F14 key
  [137] = "F15",  -- kMenuF15Glyph, 0x89, F15 key
  [138] = "⎈",   -- kMenuControlISOGlyph, 0x8A, Control key (ISO standard)
  [140] = "⏏",   -- kMenuEjectGlyph, 0x8C, Eject key (available on Mac OS X 10.2 and later)
  [141] = "英数", -- kMenuEisuGlyph, 0x8D, Japanese eisu key (available in Mac OS X 10.4 and later)
  [142] = "かな", -- kMenuKanaGlyph, 0x8E, Japanese kana key (available in Mac OS X 10.4 and later)
  [143] = "F16",  -- kMenuF16Glyph, 0x8F, F16 key (available in SnowLeopard and later)
  [144] = "F17",  -- kMenuF16Glyph, 0x90, F17 key (available in SnowLeopard and later)
  [145] = "F18",  -- kMenuF16Glyph, 0x91, F18 key (available in SnowLeopard and later)
  [146] = "F19",  -- kMenuF16Glyph, 0x92, F19 key (available in SnowLeopard and later)
}, {
  __tostring = function(self)
    local result = ""
    for k, v in require("hs.fnutils").sortByKeys(self) do
      result = result..string.format("%4d %s\n", k, v)
    end
    return result
  end,
})

-- handles updates to the alternateNameMap table
local modifyNameMap = function(info, add)
    for _, item in ipairs(info) do
        local applicationName = item.kMDItemFSName
        for __, alt in ipairs(item.kMDItemAlternateNames or {}) do
            alternateNameMap[alt:match("^(.*)%.app$") or alt] = add and applicationName or nil
        end
    end
end

-- local var to hold spotlight query userdata to catch updates
local spotlightWatcher

-- starts the spotlight query to get the alternate names for applications
local buildAlternateNameMap = function()
    if spotlightWatcher then -- force a rebuild if it's already running
        spotlightWatcher:stop()
        spotlightWatcher = nil
        alternateNameMap = {}
        application._alternateNameMap = alternateNameMap
    end
    spotlightWatcher = require"hs.spotlight".new()
    spotlightWatcher:queryString([[ kMDItemContentType = "com.apple.application-bundle" ]])
                    :callbackMessages("didUpdate", "inProgress")
                    :setCallback(function(obj, msg, info)
                        if info then -- shouldn't be nil for didUpdate and inProgress, but check anyways
                            -- all three can occur in either message, so check them all!
                            if info.kMDQueryUpdateAddedItems   then
                                modifyNameMap(info.kMDQueryUpdateAddedItems,   true)
                            end
                            if info.kMDQueryUpdateChangedItems then
                                modifyNameMap(info.kMDQueryUpdateChangedItems, true)
                            end
                            if info.kMDQueryUpdateRemovedItems then
                                modifyNameMap(info.kMDQueryUpdateRemovedItems, false)
                            end
                        end
                    end):start()
end

--- hs.application.enableSpotlightForNameSearches([state]) -> boolean
--- Function
--- Get or set whether Spotlight should be used to find alternate names for applications.
---
--- Parameters:
---  * `state` - an optional boolean specifying whether or not Spotlight should be used to try and determine alternate application names for `hs.application.find` and similar functions.
---
--- Returns:
---  * the current, possibly changed, state
---
--- Notes:
---  * This setting is persistent across reloading and restarting Hammerspoon.
---  * If this was set to true and you set it to true again, it will purge the alternate name map and rebuild it from scratch.
---  * You can disable Spotlight alternate name mapping by setting this value to false or nil. If you set this to false, then the notifications indicating that more results might be possible if Spotlight is enabled will be suppressed.
application.enableSpotlightForNameSearches = function(...)
    local args = table.pack(...)
    if args.n > 0 then
        if args[1] then
            settings.set("HSenableSpotlightForNameSearches", true)
            spotlightEnabled = true
            buildAlternateNameMap()
        else
            settings.set("HSenableSpotlightForNameSearches", args[1])
            spotlightEnabled = args[1]
            if spotlightWatcher then
                spotlightWatcher:stop()
                spotlightWatcher = nil
            end
            alternateNameMap = {}
            application._alternateNameMap = alternateNameMap
        end
    end
    return settings.get("HSenableSpotlightForNameSearches")
end

-- if the setting is set, then go ahead and start the build process
if spotlightEnabled then buildAlternateNameMap() end

do
  local mt=getmetatable(application)
  -- whoever gets it first (window vs application)
  if not mt.__call then mt.__call=function(t,...) return t.find(...) end end
end

application._alternateNameMap = alternateNameMap

return application

redpajama_set_name: RedPajamaGithub


text:
Other titles from University of Arkansas Press
My Father Says Grace: Poems
by Donald Platt
University of Arkansas Press, 2007
Paper: 978-1-55728-837-0 | eISBN: 978-1-61075-271-8
Library of Congress Classification PS3566.L286M95 2007
In his third collection, My Father Says Grace, Donald Platt combines elegy with verse of larger historical allusion and reference. At the center of the book stand poems detailing a father's stroke and slowly developing Alzheimer's disease and how it affects one family. An extended meditation on a mother-in-law's dying provides counterpoint to elegies for more public figures like Walt Whitman and Janis Joplin. The private life in "the valley of the shadow of death" often gets juxtaposed with explicitly political verse. One of these poems records the racially charged conversations in a small southern town's Amazing Grace Beauty Salon. Another describes a Vietnam protestor, famously photographed while sticking flowers in an MP's gun barrel, alongside images from his later life as a transvestite. The poems tend to find themselves in the midst of crisis, historical or personal. They yearn for "transport" and strive "to be 'carried across,' away, out, toward, back into / / some new country / where the soul improvises, croons scat to itself alone."
Donald Platt is an associate professor of English at Purdue University. His previous collections, Fresh Peaches, Fireworks, & Guns and Cloud Atlas, were published by Purdue University Press as winners of the Verna Emery Poetry Prize. He is a recipient of the "Discovery"/The Nation Prize, a fellowship from the National Endowment for the Arts, the Center for Book Arts' Poetry Chapbook Prize, and two Pushcart Prizes. His poems have appeared in many magazines and journals, including The New Republic, Nation, Paris Review, Poetry, Kenyon Review, Georgia Review, Virginia Quarterly Review, Field, Iowa Review, Southwest Review, and Southern Review, and have been anthologized in The Best American Poetry 2000 and 2006. He lives with his wife, the poet Dana Roeser, and their two daughters in West Lafayette, Indiana.
Sizzling Happy Family	000
Joy	000
My Father Says Grace	000
Brother Death, Sister Life	000
Ash Wednesday	000
Summer Arrhythmias	000
Turtle with the World on Its Back	000
Compass Rose	000
Treble and Treble and Back	000
Killing the Minotaur	000
Mirage	000
Victor Talking Machine Co.	000
Sundowning Exit-Seeker	000
Name & Address	000
Walt Whitman Wrestling Naked with the Young Trees	000
After	000
For Janis Joplin with Pink Feather Boa in the Clouds at the Edge of the Atlantic Ocean
Pretty Boy, Rifle Barrels, Carnations	000
Setting Sun	000
Snapshot	000
Andantino Cantabile with Double Rainbow	000
Cartwheels	000
Amazing Grace Beauty Salon	000
Two Poets Meet	000
Red Door	000
Ground Transport	000
See other books on: Poems | Poetry
See other titles from University of Arkansas Press
Nearby on shelf for American literature / Individual authors / 1961-2000:
Paper: 978-1-55728-837-0
eISBN: 978-1-61075-271-8

redpajama_set_name: RedPajamaCommonCrawl


text:
Il Museo diocesano di San Petronio di Bologna è allestito all'interno della basilica di San Petronio, nella navata sinistra.

Il nucleo iniziale della raccolta ospitata nel Museo, citata anche dal Vasari, si costituì tra il XVI e XIX secolo in relazione al problematico completamento della facciata della basilica, anche se il museo vero e proprio fu costituito solo nel 1894, riunendo nello stesso locale varie testimonianze e documenti relativi alla costruzione della basilica con la suppellettile liturgica.

Descrizione
L'itinerario espositivo del museo è suddiviso in due sale.

Sala I
La prima sala ospita le testimonianze della storia della basilica e della sua problematica costruzione, con il mancato completamento della facciata. Infatti, sono qui raccolti i progetti, i disegni ed i modelli per la facciata della basilica di San Petronio realizzati dagli architetti che dal XVI al XIX secolo si avvicendarono nel tentativo di realizzarla. Tra questi si ricordano: Baldassarre Peruzzi, Giulio Romano, Cristoforo Lombardo, Jacopo Barozzi da Vignola, Pellegrino Tibaldi,  Andrea Palladio ed Edoardo Collamarini.

Inoltre, vi sono esposti:
 gli strumenti utilizzati da Giovanni Cassini per costruire (1655 - 1656) la meridiana della basilica;
 alcune formelle marmoree con scene bibliche (prima metà del XVI secolo) realizzate per i portali minori.

Sala II
Nella seconda sala è conservato il Tesoro di San Petronio. Di particolare rilievo:
 le preziose oreficerie del XIII secolo;
 la Pace di san Sebastiano (fine XV secolo), in argento sbalzato e cesellato;
 due cofanetti (XV secolo) realizzati dalla bottega degli Embriachi
 un corale (XV secolo) con tre miniature di Taddeo Crivelli;
 i corali miniati (XV - XVI secolo) eseguiti dai miniatori Martino da Modena e Giovanni Battista Cavalletti;
 la croce astile (1547), in argento sbazato e cesellato, opera del bolognese Giovanni Battista del Gambaro;
 i paramenti sacri, databili dal XVI al XVIII secolo.
 il Reliquiario di sant'Antonio di Padova (nella seconda metà del XVII secolo), proveniente dalla Cappella Cospi, a cui si associa un crocifisso in lapislazzuli, argento e pietre dure.

Bibliografia
 Mario Fanti (a cura di), Il Museo di San Petronio in Bologna, Bologna 2003
 Erminia Giacomini Miari, Paola Mariani, Musei religiosi in Italia, Milano 2005, p. 63

Voci correlate
 Arcidiocesi di Bologna
 Basilica di San Petronio
 Museo Diocesano

Altri progetti

Collegamenti esterni

Musei di Bologna
P
Petronio
Arcidiocesi di Bologna

redpajama_set_name: RedPajamaWikipedia


A method of posting ephemeral posts is disclosed. The method starts with receiving, from a user of a social network, a request to post an ephemeral post, the request including an ephemeral variable associated with a threshold event. The ephemeral post is posted on behalf of the user. Then an occurrence of the threshold event is monitored. When the threshold event has not occurred, the post is allowed to be accessible to at least one viewer other than the user. When the threshold event has occurred, the post is blocked from being accessible by the at least one view other than the user.
The embodiments of the invention are related to the field of Internet messaging. More specifically, the embodiments are related to creating and managing ephemeral posts in a social networking system.
Today the Internet permeates everyday life. While passively viewing online content is still a mainstay of the Internet experience, more and more Internet users are creating contents on the Internet, through webpages and online social networking sites. User generated content has seen exponential growth in recent years, and posting, viewing, and replying to messages on a social network site are growing to become a daily routine of a significant percentage of Internet users. An August 2011 survey by the Pew Internet & American Life Project found that 65% of American online adults use social networking sites, up dramatically from 8% found by the same organization in a February 2005 survey.
Messaging through a social network site allows people to brainstorm ideas, share interests, exchange experiences, and generally "stay in touch" with family, friends, associates, and the world-at-large. Yet, many people remain reluctant to post messages on a social network site. One impediment to more message posting is the inkling that messages posted online are "always out there." Some people are afraid that a spontaneous message posted on a social network site remains indefinitely beyond the poster's control.
The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that different references to "an" or "one" embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
FIG. 1 is a block diagram illustrating a social networking system according to one embodiment of the invention.
FIG. 2 illustrates an example social graph 200 that may be used by a social networking system.
FIG. 3 is a flow diagram illustrating a method of managing ephemeral posts in a social networking system according to one embodiment of the invention.
FIG. 4 is a block diagram illustrating a social networking system managing ephemeral posts according to one embodiment of the invention.
FIG. 5 is a flow diagram illustrating a social networking system managing ephemeral posts according to one embodiment of the invention.
FIG. 6 is a block diagram illustrating an ephemeral variable selection graphic user interface (GUI) of a social networking system according to one embodiment of the invention.
FIG. 7 is a block diagram illustrating a graphic user interface (GUI) used for creating an ephemeral post at a social networking system according to one embodiment of the invention.
FIGS. 8A-B are block diagrams illustrating graphic user interfaces (GUIs) used for ephemeral post at a social networking system according to embodiments of the invention.
FIG. 9 illustrates an embodiment of a user interface for an ephemeral posting application.
FIG. 10 illustrates a computing system in which embodiments may operate, be installed, integrated, or configured.
In the following description, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. It will be appreciated, however, by one skilled in the art that the invention may be practiced without such specific details. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.
References in the specification to "one embodiment," "an embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. In the following description and claims, the terms "coupled" and "connected," along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. "Coupled" is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, co-operate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements that are coupled with each other.
FIG. 1 is a block diagram illustrating a social networking system according to one embodiment of the invention. Referring to FIG. 1, user devices 102 and 122 communicate with social network system 106 through network 104. Network 104 may be any type of network such as a local area network (LAN), a wide area network (WAN) such as Internet, a corporate intranet, a metropolitan area network (MAN), a storage area network (SAN), a bus, or a combination thereof, wired and/or wireless. User devices 102 and 122 may be any device communicatively coupled to network 104, such as computers, mobile devices (cellphones, wearable Internet devices, automobile based Internet devices, etc.), smart TVs/setup boxes, Internet gaming devices, a personal digital assistant (PDA), a Web enabled system, a media player, a "thin" client, etc.
Social networking system 106 operates a social network site, platform, or an online service that facilitates the building of social networks or social relations among people and other entities such as corporations. Social networking system 106 allows users to designate other users or entities as connections, or otherwise connect to, or form relationships with, other users or entities. Additionally, users contribute and interact with their connections, use applications, join groups, list and confirm attendance at events, invite connections, or perform other tasks that facilitate social interaction. External applications also use the services of the social networking system to allow authenticated users to incorporate some of the above social interactions with use of the external applications.
Generally a creator of a typical post in a social networking system has no control over the duration of the post's life on the system. The social networking system may display a posted post indefinitely, which may be long past a useful/desirable period for the creator. Ephemeral posts are different and they may be associated with an ephemeral variable. When the ephemeral variable reaches a certain threshold, an ephemeral post becomes no longer viewable by other users of the social networking system. In other words, ephemeral posts are "perishable." In some embodiments, a user/creator of an ephemeral post specifies the condition(s) of the ephemeral post being blocked from being viewed, forwarded, searched, replied or otherwise accessed. In social networking system 106, post timers 112 may track these specified conditions associated with ephemeral posts stored in post host servers 108.
A social networking system may support a variety of applications, such as photo sharing, on-line calendars and events, gaming, instant messaging, and advertising. For example, the social networking system may also include media sharing capabilities. Also, the social networking system may allow users to post photographs and other multimedia files to a user's profile page (typically known as "wall posts" or "timeline posts") or in a photo album, both of which may be accessible to other users of the social networking system depending upon the user's configured privacy settings. The social networking system may also allow users to configure events. For example, a first user may configure an event with attributes including time and date of the event, location of the event and other users invited to the event. The invited users may receive invitations to the event and respond (such as by accepting the invitation or declining it). Furthermore, the social networking system may allow users to maintain a personal calendar. Similarly to events, the calendar entries may include times, dates, locations and identities of other users.
FIG. 2 illustrates an example social graph 200 that may be used by a social networking system. In the example of FIG. 2, social graph 200 includes user nodes 201, concept nodes 202, and edges 203 between nodes. An edge 203 between a pair of nodes may represent a relationship (or an action) between the pair of nodes. For example, user "G" is a friend of user "B", user "C", and user "E", respectively, as illustrated by the edges between user nodes "G" and "B", between user nodes "G" and "C", and between user nodes "G" and "E." For example, users "C", "E", and G″ watch (or "like") a TV show "American Idol", as illustrated by the edges between the "American Idol" concept node and user nodes "C", "E", and G″, respectively. Similarly, the edge between the user node "B" and the concept node "Palo Alto" may indicate that user "B" declares "Palo Alto" as his or her city of residence. The edge between the user node "B" and the concept node "Macy's" may indicate that user "B" likes the store "Macy's." Of course, social graphs can be much larger than social graph 200 illustrated in FIG. 2, and the number of edges and/or nodes in a social graph may be many orders of magnitude larger than that depicted herein.
As described earlier, an edge between a pair of nodes may indicate a direct relationship between the pair of nodes. An edge may be directed and connect an ordered pair of nodes. For example, an edge connecting a user node corresponding to a user and a concept node corresponding to a city may be directed (i.e., the user lives in the city). An edge may be undirected, as a pair of nodes connected by the edge does not have a particular order. For example, an edge connecting two user nodes can be undirected as the edge indicates a friendship between two users corresponding to the two user nodes. As described earlier herein, a degree of separation between any two nodes is defined as the minimum number of hops required to traverse the social graph from one node to the other. Thus, for user "B", the nodes for users "A", "C", and "G" are all one hop away and are thus users of first-degree and may be described as "connected to" or "friends" of user "B." However, from the standpoint of user "B", the nodes for users "E", "F", "J", and "K" are considered to have a second-degree of separation because the shortest path from user "B" to any of these nodes requires transiting through one other node. Thus, from the standpoint of user "B", users "E", "F", "J", and "K" are deemed "friends of friends." Accordingly, user "B" is either a "friend" or a "friend of a friend" with every other user in the graph except for user "H", as the shortest path between user "B" and user "H" transits through two user nodes.
FIG. 3 is a flow diagram illustrating a method of managing ephemeral posts in a social networking system according to one embodiment of the invention. Method 200 may be performed social networking system 106 in FIG. 1. A post posted to the social network system may contain at least one of a message, a photo, a videos, a tag, location information, sentiment, a text, a hyperlink to a location on the Internet, other structured data, or a combination of two or more types of content. The types of content of an ephemeral post may be as broad as a regular post in the social networking system.
Referring to FIG. 3, at block 301, the social networking system receives a request to post an ephemeral post. The request includes an ephemeral variable associated with a threshold event. The association may be triggered by the user indicating that a to-be-posted post is an ephemeral post in one embodiment. If the user does not specify an ephemeral variable, the social network system may attach a default ephemeral variable to the post. The ephemeral variable may be a time duration in an embodiment, indicating an intent to have the system to block the post from being viewed (i.e., expired) after the post is posted on the social networking site for the specified time duration. The ephemeral variable may be an interaction count in another embodiment, indicating an intent to have the post expire after the post is viewed, commented on, liked, etc. Alternatively, a user may indicate that a post is to expire if the post is not viewed, commented on, liked, etc. for the specified number of times.
The ephemeral variable may also be a combination of both time duration and interaction counts. Interaction counts can be based on a variety of interactions such as user clicks, views, shares, comments, promoting a post, forwarding, "likes", and etc. The threshold event is that a time duration and/or interaction counts reaches the defined setting or settings. As discussed herein, the number of selections of ephemeral variables and combinations/permutations of ephemeral variables containing a threshold event is nearly limitless. The principle is simple: by associating one or more ephemeral variables to a post, the user controls availability of his/her posted post on a social networking system.
In one embodiment, the system provides an indication to notify one or more viewer that the post-creating user has posted an ephemeral post in the social networking system. The notification may be an email or a text message (e.g., a text through short message service (SMS)) to an intended user (e.g., a viewer within the same online community of the post-creating user). In addition, the social networking system may associate an audio/visual symbol with the post-creating user on the social networking site to indicate the existence of such a post.
Referring back to FIG. 3, at block 302, the social network system posts the ephemeral post on behalf of the user. In one embodiment, the user dictates the audience of the post through selecting from a pre-defined list or a privacy setting (e.g., only self, only friends, acquaintances, friends of friends, particular list, particular group, public, etc). In one embodiment, different audiences are given different ephemeral variables. Then the social networking system monitors for an occurrence of the specific threshold event at block 304. The system allows the post to be accessible (e.g., viewable) to at least one viewer other than the user when the monitored threshold event(s) has not occurred at reference 306. In a social networking system, it is not uncommon for a user to make a post viewable only to users in a selected community instead of every user in the system, and a user posting an ephemeral post may do the same and limit viewership of a selected community, as long as the monitored threshold event has not occurred.
At block 308, once a threshold event occurs, the system blocks the post from being accessible. A viewer that otherwise may see the post can no longer access the ephemeral post. The social networking system may still allow the post-creating user to see the post in one embodiment. In another embodiment, the system may remove the post so that even the post-creating user may not see the post again (the post being deleted from the system). The levels of blocking may be numerous: for example, an expired ephemeral post may be moved to a less visible place on the post-creating user's page on the system, it may be retrievable only through an operator of the system, or it may be searchable only for certain group of users. The levels of blocking are user configurable in one embodiment. In one embodiment, the system creates a specific timeline unit for expired ephemeral posts that are only viewed to the posting user.
In one embodiment, the blocking of an expired ephemeral post from being viewed (or otherwise accessed) may not be permanent and a viewer may ask the post-creating user to revive the expired ephemeral post under certain circumstances. In addition, an ephemeral post may become a regular post after certain event. For example, a post-creating user may specify an ephemeral post to be converted to a regular post if it receives a number of interaction data.
In one embodiment, the selected ephemeral variables are collected by the social networking system for analysis so that the system may provide better default ephemeral variables or ranges of ephemeral variables in the future. The selected ephemeral variables are collected, stored, or used in accordance with the local laws and user's privacy settings. For example, if the collected data shows that more users select the maximum interaction count allowed, the system may make the maximum interaction count number higher in the future. In addition, the collected data may include a time period between creating and displaying ephemeral posts, a time period between creating and blocking ephemeral posts, and other data for the social networking system to manage ephemeral posts better or provide a better user experience in using ephemeral posts.
In one embodiment, the social networking system provides a third party data about selected ephemeral variables of ephemeral posts for a certain group of users. A third party may be interested in sponsoring a modification of a counting ephemeral variable associated with certain ephemeral posts. For example, a studio may be willing to ask an ephemeral post-creating user to extend the duration of the ephemeral post if the post contains a favorable view of a TV show the studio is trying to promote. For a studio paid fee splitting between the user and an operator of the system, the user may accept a suggested revision of the ephemeral variable and associated threshold event (e.g., instead of the favorable ephemeral post expiring in 24 hours, the system may change the expiration to 7 days with user's consent).
The associating of an ephemeral post with an ephemeral variable does not necessarily happen solely for new ephemeral posts. In some embodiments, a user may modify an existing post to become an ephemeral one.
As discussed herein above, the associated ephemeral variable of an ephemeral post may be time duration of the post, interactivity count, or a combination. Interaction counts can be based on a variety of interactions such as user clicks, views, shares, comments, promoting a post, forwarding, "likes", and etc. The associated ephemeral variable may depends on the content of the post, location of the post-creating user, selected audience of the post, and other factors. In addition, the starting counting time for any type of ephemeral variables may be delayed by a selectable amount of time. For example, a user may want to start the ephemeral post at 1:00 am of the opening night of the latest installment of a movie, so that other movie goers see it.
In one embodiment, an ephemeral post includes one or more audio/visual indications, such that when a viewer sees the posted ephemeral post, he/she knows that it is ephemeral. The attached audio/visual indication may change as the ongoing post gets closer to the threshold event. For example, a traffic light may be attached to an ephemeral post that goes from green to red. For another example, an ephemeral post may have a colored boarder, or it may wiggle on the screen of the display. In a mobile setting, the existence of ephemeral post may be displayed on a mobile phone or tablet devices in one embodiment.
In one embodiment, the system provides default ephemeral variables to be associated with an ephemeral post. The default ephemeral variables may not be identical for all users and the system may provide a variety of default ephemeral variables depending on a number of factors. For example, the system may provide a default ephemeral variables based on post content—a commentary about global warming may be given a longer posting duration than an inquiry about going shopping. The system may also provide a default ephemeral variable based on demographic information it knows about the user—being more self-conscious, a teenager may prefer using interactivity count instead of post posting duration as the associated ephemeral variables. In addition, the default ephemeral variable can be based on audience of a post, e.g., a close friend with a high coefficient or affinity can have a longer time than other users. The default ephemeral variables may also be based on the user's physical location. For example, an ephemeral post posted from a bar may be given shorter default posting duration than an ephemeral post posted from a university library.
In one embodiment, the system provides a range of ephemeral variables depending on a number of factors. For example, based on content of posts, some contents are given a wider range of time or activity count than others.
Note the variety of embodiments discussed herein above is not meant to be an exhaustive list of possible embodiments, and they are only illustrations of the underlying principle.
FIG. 4 is a block diagram illustrating a social networking system managing ephemeral posts according to one embodiment of the invention. Social networking system 406 is similar to social networking system 106 of FIG. 1 and the same or similar references indicate elements or components having the same or similar functionalities. In addition to social networking system 406, user devices 402 is used by a user to create ephemeral posts while user devices 422 is used by another user to review the created ephemeral posts. Both user devices 402 and 422 are communicatively coupled to social networking system 406.
Social networking system 406 contains post host server 408 and post timers 412. In one embodiment, post timers 412 is implemented within post host server 408 instead of being communicatively coupled to post host server 408 as shown in FIG. 4.
Post timers 412 may contain a variety of ephemeral variable selections supported by social networking system 406 as detailed above. Post timers 412 perform ephemeral variable measuring and monitor expiration of the ephemeral variables associated with ephemeral posts. Post timers 412 notify post host server 408 to display or block an ephemeral post depending on the status of its associated ephemeral variable.
In one embodiment, post host server 408 contains post creator module 452, post displayer module 454, user data module 456, sponsor data module 458, post statistics collector module 462, and ephemeral post database 480. Note some modules within post host server 408 may be integrated together, and some modules may not be implemented within post host server 408 and are implemented as standalone entities that communicatively coupled to post host server 408. Also, when social networking system 406 supports only a subset of features of ephemeral posting, some modules illustrated in FIG. 4 may not be implemented.
Post creator 452 coordinates posting an ephemeral post to the social networking system 406. Post creator 452 interacts with a post-creating user or a post modifying user and receives user selections of an ephemeral post. The received user selections are then fed to post host server 408 to create an ephemeral post. Post creator 452 may collect data related to the ephemeral post and store them to post statistics collector 462 for analysis and fine tuning the performance of social networking system 306. The data related to ephemeral post are collected, stored, or used in accordance with the local laws and user's privacy settings. Post creator 452 may apply default selections for an ephemeral post when a post-creating user has not made a proper selection, or when the social networking system 406 considers overwriting a user selection necessary. Note post creator 452 may be able to create regular posts as well as ephemeral posts.
Post displayer 454 coordinates display and otherwise makes accessible of an ephemeral post on the social networking system 406. The displaying may include showing the ephemeral post on a social networking site on the Internet or on an application of a user device through "pushing" the data to the user device. Post displayer 454 may block an ephemeral post from being viewed by one group of users but allow access to another group. For example, it may allow the post-creating user to see an expired ephemeral post while other users are blocked. Post displayer 454 coordinates with post timers 412 to determine how long to display an ephemeral post and to which user(s) to display to.
User data 456 stores user related data including user demographics, user locations, user activities, and other user profiling data on the social networking site. The data is useful for social networking system 406 to set default ephemeral variables associating with an ephemeral post when a user fails to create an ephemeral variable. The data may also be useful for data analysis of user behavior in using an ephemeral post. By correlating user-profiling data with a user's selection of ephemeral posts (duration, type of ephemeral variables, and etc.), the social networking system learns preferences of ephemeral variables of ephemeral posts of the user and his/her type of users, and that knowledge may be used to further improve the user experience in using ephemeral posts. In addition, the knowledge may be monetized by the social networking system in targeted advertisement. For example, if an ephemeral post asks about the best bargain in a shopping mall and the ephemeral post is set to expire by the end of upcoming weekend, a vendor in the shopping mall may generate a promotion that is good for the upcoming Saturday morning only to be attached to the post or displayed along with the post on the message posting page displaying the post.
Sponsor data 458 stores data related to third party sponsors of ephemeral posts. A third party sponsor may have a certain criteria for targeted advertisement relating to ephemeral posting, and the criteria may be stored in sponsor data 458. In addition, a third party sponsor may prefer to prolong or shorten an ephemeral variable associated with ephemeral posts, and sponsor data 458 may store the third party sponsor's criteria of modifying ephemeral variable associated with ephemeral posts. Social networking system 406 may take ephemeral variable-modifying criteria stored in sponsor data 458 and revise the ephemeral variable associated with existing ephemeral posts or suggest ephemeral variables associating with to-be-created posts. A third party sponsor may pay a fee for the service.
Post statistics collector 462 collects statistics associated with ephemeral posts. For example, the collected statistics may include selected ephemeral variables associated with various content and user with various profiles, the time period between creating and displaying ephemeral posts, and a time period between creating and blocking ephemeral posts. In one embodiment, the system provides a view solely for a post-creating user of the social networking system through retrieving data from post statistics collector 462. The user then may view his/her past ephemeral posts and interactivity/time duration statistics. These and other collected statistics may help social networking system 406 to fine-tune its operations in supporting ephemeral posts. The collected statistics may also be provided to a third party that is interested in user behaviors.
Ephemeral post database 480 stores ephemeral posts posted in social networking system 406. Various ephemeral variables associated with ephemeral posts may be stored with these posts as well. In one embodiment, ephemeral post database is only a subset of a database storing all posts posted in social networking system 406. In another embodiment, ephemeral post database 480 is a standalone entity outside of post host server 408.
FIG. 5 is a flow diagram illustrating a social networking system managing ephemeral posts according to one embodiment of the invention. At reference 502, the social networking system provides a selection of ephemeral variables to a post-creating user when the user creates a post. The ephemeral variables may include time duration, viewership counts, or a combination thereof. At reference 504, the social networking system provides a selection of when the selected ephemeral variable or ephemeral variables start as the system may allow a user to set a starting time after the post is posted. When a user selection includes a timer duration, the method 500 goes to reference 506, where the system provides a selection of duration of the timer. If the user selection includes an interactivity counts, method 500 goes to reference 508, where the system provides a selection of interactivity counts. Note that a user may select multiple ephemeral variables combining both time duration and interactivity counts.
At reference 510, the system provides a selection of conditions to disable the ephemeral variable counting, that is, the selection of conditions that the user may specify to disassociate the selected ephemeral variables with the ephemeral post. As discussed herein above, in one embodiment, the system allows a user to specify under what condition to re-categorize an ephemeral post to a regular post. References 502-510 may be performed by post creator 452 in coordination with post timers 412 and other modules in FIG. 4. Note the user may specify no condition to disassociate the selected ephemeral variables with the ephemeral post. In that case, the system provides a default post timer or inactivity count based on inference on post content, post audience, location of the user at the time of posting (e.g., a post from created from the user's classroom may have a shorter timer than a post from the same user's expedition at Mount Everest), and other factors. In addition, the system may prompt a question to make an ephemeral post permanent when default post timer or inactivity count is about to expire.
At reference 512, the system may collect user selection information as the user selects ephemeral variables associating with the post. The system may continue to collect data about the ephemeral post after its creation and until the post expires or converts to a regular post. For example, the collected data includes the time period between the time the ephemeral post is posted and the time the ephemeral post is disassociated with any ephemeral variable (thus no longer ephemeral), in addition to the ephemeral variables the user initially selected. Reference 512 may be performed by post statistics collector 462 in coordination with post timers 412 and other modules in FIG. 4.
At reference 515 of FIG. 5, the system may allow a third party sponsor to revise one or more of the selected ephemeral variables by the post-creating user. A third party sponsor may revise ephemeral variables to promote its commercial interests. Reference 515 may be performed by sponsor data 456 in coordination with other modules in FIG. 4.
Note the order of method 500 may differ in different embodiments. For example, collecting user selection information may occur after allowing a sponsor to revise a selected ephemeral variable. Also, user may make no decision with respect to ephemeral variables, and the system may attach one or more default ephemeral variables to an ephemeral post base on a variety of factors as discussed herein above.
A number of graphic user interfaces may be deployed by a social networking system to create or modify an ephemeral post. FIG. 6 is a block diagram illustrating an ephemeral variable selection graphic user interface (GUI) of a social networking system according to one embodiment of the invention. The GUI may be a pop-up box for a user to create an ephemeral post. The GUI includes a duration setting at reference 604. The setting has a range and a user may select a value within the range so that a created ephemeral post will be associated with the selected value (i.e., a threshold being reached once a timer starts counting). The GUI may also include an interactivity count setting at reference 602. The interactivity count setting has a selectable range.
FIG. 7 is a block diagram illustrating a graphic user interface (GUI) used for creating an ephemeral post at a social networking system according to one embodiment of the invention. The post creating GUI has a layout similar to regular post. For example, it includes "Update Status" and "Add Photos/Videos" options at the top of the GUI. However, at the side of the type pad, a timer scrollbar at reference 702 is provided. The timer scrollbar has a post duration range and a post-creating user may select a value within the range by sliding the bar within the scrollbar. The hourglass at reference 704 indicates a duration of an ephemeral post.
FIGS. 8A-B are block diagrams illustrating graphic user interfaces (GUIs) used for ephemeral post at a social networking system according to embodiments of the invention. FIG. 8A is a GUI for viewing a posted ephemeral post. The layout is similar to a regular posted post except for the inclusion of a visual timer indication symbol at reference 802. The symbol at reference 802 reminds a viewer that the post is ephemeral and it may not be viewable after a certain event. Note that in one embodiment, the system may not let viewers know that a post is ephemeral thus the GUI for an ephemeral post is indistinguishable from the GUI for a regular post in this embodiment.
FIG. 8B is a GUI for viewing an ephemeral reply to a posted post. The layout for the reply is similar to a regular reply to a posted post except for an audio/visual timer indication at reference 804.
FIG. 9 illustrates an embodiment of a user interface for an ephemeral posting application. In this particular example, this is a user interface for a standalone application to be run on a device such as a smartphone or tablet. This user interface displays both received and sent ephemeral posts for a user of the social network. Through this user interface a user may send and receive posts in the form of text, pictures, pokes, and/or video. In some embodiments, only users of the social network may use this application and each user's username is associated with their respective posts.
Typically, to view a post in this application, the user presses the screen where the post is until the content of the post appears on the screen. A countdown will also appear on the screen to indicate to the user how long he/she has to view the post. In some embodiments, the countdown will halt when the user releases the screen.
The user interface indicates how long ago a post was sent or received as shown in 901. The user interface also displays how long ago a post was opened as shown in 903. The user interface may also indicate when a receiving user has taken a screenshot of the ephemeral post as shown in 905.
In some embodiments, the application allows a user to have a post disappear from the after a user set period of time regardless of if the post was viewed by the recipient.
FIG. 10 illustrates, in block diagram form, an exemplary computing system 1000 in accordance with which embodiments may operate, be installed, integrated, or configured. The computing system 1000 includes one or more microprocessors 1005 and connected system components (e.g., multiple connected chips). Alternatively, the computing system 1000 is a system on a chip.
The computing system 1000 includes memory 1010, which is coupled to the microprocessor(s) 1005. The memory 1010 may be used for storing data, metadata, and programs for execution by the microprocessor(s) 1005. The memory 1010 may include one or more of volatile and non-volatile memories, such as Random Access Memory ("RAM"), Read Only Memory ("ROM"), a solid state disk ("SSD"), Flash, Phase Change Memory ("PCM"), or other types of data storage. The memory 1010 may be internal or distributed memory.
The computing system 1000 also includes an audio input/output subsystem 1015 which may include a microphone and/or a speaker for, for example, playing back music or other audio, receiving voice instructions to be executed by the microprocessor(s) 1005, playing audio notifications, etc.
A display controller and display device 1020 provides a visual user interface for the user. In an embodiment where the computing system 1000 is an exemplary representation of the user device 102 of FIG. 1, the display device 1020 may display the GUI windows illustrated in FIGS. 6, 7, and 8A-B.
The computing system 1000 also includes one or more input or output ("I/O") devices and interfaces 1025, which are provided to allow a user to provide input to, receive output from, and otherwise transfer data to and from the system. These I/O devices 1025 may include a mouse, keypad or a keyboard, a touch panel or a multi-touch input panel, camera, optical scanner, network interface, modem, other known I/O devices or a combination of such I/O devices. The touch input panel may be a single touch input panel which is activated with a stylus or a finger or a multi-touch input panel which is activated by one finger or a stylus or multiple fingers, and the panel is capable of distinguishing between one or two or three or more touches and is capable of providing inputs derived from those touches to the computing system 1000.
The I/O devices and interfaces 1025 may also include a connector for a dock or a connector for a USB interface, FireWire, Thunderbolt, Ethernet, etc. to connect the computing system 1000 with another device, external component, or a network. Exemplary I/O devices and interfaces 1025 also include wireless transceivers, such as an IEEE 802.11 transceiver, an infrared transceiver, a Bluetooth transceiver, a wireless cellular telephony transceiver (e.g., 2G, 3G, 4G), or another wireless protocol to connect the computing system 1000 with another device, external component, or a network and receive stored instructions, data, tokens, etc.
It will be appreciated that one or more buses, may be used to interconnect the various components shown in FIG. 10.
In one embodiment, the computing system 1000 is an exemplary representation of the user device 102 of FIG. 1. The computing system 1000 may be a personal computer, tablet-style device, a personal digital assistant (PDA), a cellular telephone with PDA-like functionality, a Wi-Fi based telephone, a handheld computer which includes a cellular telephone, a media player, an entertainment system, or devices which combine aspects or functions of these devices, such as a media player combined with a PDA and a cellular telephone in one device. In another embodiment, the computing system 1000 is an exemplary representation of a server computer in the social networking system 106 of FIG. 1. In other embodiments, the computing system 1000 may be a network computer, server, or an embedded processing device within another device or consumer electronic product. As used herein, the terms computer, system, device, processing device, and "apparatus comprising a processing device" may be used interchangeably with the computing system 1000 and include the above-listed exemplary embodiments.
It will be appreciated that additional components, not shown, may also be part of the computing system 1000, and, in certain embodiments, fewer components than that shown in FIG. 10 may also be used in a computing system 1000. It will be apparent from this description that aspects of the inventions may be embodied, at least in part, in software. That is, computer-implemented methods may be carried out in a computer system or other data processing system in response to its processor or processing system executing sequences of instructions contained in a memory, such as memory 1010 or other non-transitory machine-readable storage medium. The software may further be transmitted or received over a network (not shown) via a network interface device 1025. In various embodiments, hardwired circuitry may be used in combination with the software instructions to implement the present embodiments. Thus, the techniques are not limited to any specific combination of hardware circuitry and software, or to any particular source for the instructions executed by the computing system 1000.
An article of manufacture may be used to store program code providing at least some of the functionality of the embodiments described above. Additionally, an article of manufacture may be used to store program code created using at least some of the functionality of the embodiments described above. An article of manufacture that stores program code may be embodied as, but is not limited to, one or more memories (e.g., one or more flash memories, random access memories—static, dynamic, or other), optical disks, CD-ROMs, DVD-ROMs, EPROMs, EEPROMs, magnetic or optical cards or other type of non-transitory machine-readable media suitable for storing electronic instructions. Additionally, embodiments of the invention may be implemented in, but not limited to, hardware or firmware utilizing an FPGA, ASIC, a processor, a computer, or a computer system including a network. Modules and components of hardware or software implementations can be divided or combined without significantly altering embodiments of the invention.
Different embodiments of the invention may be implemented using different combinations of software, firmware, and/or hardware. Thus, the techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end system, a network element). Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer-readable media, such as non-transitory computer-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer-readable transmission media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals). In addition, such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine-readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections. The coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers). Thus, the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device.
While the flow diagrams in the figures herein above show a particular order of operations performed by certain embodiments of the invention, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).
blocking the ephemeral post from being accessible by the plurality of viewers other than the first user when the first threshold event has occurred, wherein the first threshold event is a plurality of user interactions with the ephemeral post since the posting.
2. The computer-implemented method of claim 1, wherein the ephemeral post is blocked from being accessible by at least one of the plurality of viewers in response to an expiration of a time period for viewing.
blocking the ephemeral post from being accessible by the at least one viewer other than the first user when the second threshold event has occurred.
4. The computer-implemented method of claim 1, wherein the the indication is at least one of a visual and an audio indication.
5. The computer-implemented method of claim 1, wherein the plurality of user interactions is defined by an ephemeral variable, and wherein the first user sets the ephemeral variable using a scrollbar.
indicating an existence of the ephemeral post to at least one of the plurality of viewers when the first threshold event has not occurred before displaying the ephemeral post to the viewer.
removing the ephemeral post from the social network after the first threshold event occurs.
collecting at least one ephemeral variable associated with the ephemeral post, a time period between creating and displaying the ephemeral post, and a time period between creating and blocking the ephemeral post, wherein the collected data is used to adjust the ephemeral variable to associate with a future post.
10. The non-transitory computer-readable storage medium of claim 9, wherein the ephemeral post is blocked from being accessible by at least one of the plurality of viewers in response to an expiration of a time period for viewing.
12. The non-transitory computer-readable storage medium of claim 9, wherein the plurality of user interactions is defined by an ephemeral variable, and wherein the first user sets the ephemeral variable using a scrollbar.
block the ephemeral post from being accessible by the plurality of viewers other than the first user when the first threshold event has occurred, wherein the first threshold event is a plurality of user interactions with the ephemeral post since the posting.
16. The social networking system of claim 15, wherein the ephemeral post is blocked from being accessible by at least one of the plurality of viewers in response to an expiration of a time period for viewing set by the ephemeral variable.
17. The social networking system of claim 15, wherein the instructions further cause the processor to collect the ephemeral variable associated with the post, a time period between creating and displaying the post, and a time period between creating and blocking the post, wherein the collected data is used to adjust the ephemeral variable to associate with a future post.
18. The social networking system of claim 15, wherein the the indication is at least one of a visual and an audio indication.
Office Action from U.S. Appl. No. 13/915,592, mailed Jul. 29, 2014, 13 pages.


This air-conditioned boutique hotel is an old Athenian mansion, converted in 2002 into a small, elegant hotel. It comprises a total of 19 guest rooms. Facilities on offer include an entrance hall with a 24-hour reception and check-out service, lift access, a restaurant, room and laundry services and ample parking for those arriving by car.


text:
Akces (łac. accessus) – dawniej procedura stosowana podczas wyboru papieża na konklawe. Jeśli w pisemnym głosowaniu (scrutinium) żaden z kandydatów nie uzyskał wymaganej większości 2/3 (ewentualnie jeśli kardynałowie chcieli uczynić dokonany już wybór jednomyślnym), dopuszczano zmianę preferencji wyborczych przez głosujących kardynałów poprzez "przejście" (accessus) na innego kandydata, niż głosowali (najczęściej na tego, który uzyskał najwięcej głosów). Wyniki takiego kandydata ze scrutinium i akcesu się sumowało. Do XVII wieku akces przeprowadzano ustnie, poprzez publiczną deklarację kardynała "accedo domino Cardinali ....", jednak w 1621 Grzegorz XV zarządził, że procedura akcesu także powinna być pisemna.

Charakter tej procedury wiązał się z koniecznością podpisywania kartek do głosowania, tak, aby można było zweryfikować, czy elektor nie "przechodzi" na tego samego kandydata, na którego głosował podczas scrutinium.

Po raz ostatni do wyboru papieża przez akces doszło na konklawe 1878 przy wyborze Leona XIII. Papież Pius X w 1904 roku zakazał stosowania tej procedury. Również obecne regulacje zawarte w konstytucji Jana Pawła II "Universi Dominici Gregis" z 1996 roku nie przewidują jej stosowania, gdyż jest niemożliwa do pogodzenia z zasadą tajności głosowania.

Bibliografia
 A. Piazzoni "Historia wyboru papieży", Kraków 2003

Zobacz też

Konklawe


This soup was like a creamy, cheesey potato soup. It is very hearty and even the pickest of eaters will enjoy it. Serve it with a crusty bread to have a perfect comfort food meal.
Serve with crumbled back and sour cream if desired.
1. Brown the ground beef or veggie crumbles. If using ground beef drain and set aside.
2. In a large saucepan add 1 T butter and add onion, carrots, parsley flakes, basil and celery. We doubled the carrots instead of using the celery. Saute until tender.
3. Add the broth, potatoes and beef/veggie crumbles and bring to a boil. Reduce heat, cover and simmer 10-12 minutes or until potatoes are tender.
5. Stir in the cheese, milk, salt and pepper. Cook and stir until cheese melts.
What a fun sounding soup!
Wow ! You make me feel like eating my computer !!!
YUM! Have never heard or tried this before! I must!
interesting.. should give it a try!
Definitely hearty and perfect for a cold winter day!


Stylo shoes for girls 2017 winter collection has launched before few days. Stylish pumps in amazing colors are shown below. It is latest collection by Pakistani famous brand of foot wears. It provides shoes for both male and female persons. It designs satisfy everyone therefore it is called one of the best brands. A good designer knows the nature of his/her customers. Stylo shoes have an ability to change your personality. Its new winter collection of boots 2017 is available in stores. It is an art or talent to create new designs every year. Everyone cannot achieve this ability easily. This company is also making special shoes for mature women. They like to wear soft and flat footwears mostly. On the other hand young ladies prefer high heels with creative style. You can see the images of pumps and sandals that are given below. Hope you will love them and want to wear them in this season.
Every woman waits for this brand's arrival because she loves its quality. So I want to inform them that go and get her favorite pump quickly. The outlets of this company are established in almost all big cities of Pakistan. High heels are favorable for fancy events such as parties, festivals and wedding. These styles are perfect for teenagers specially. They can wear them in schools, colleges and universities. Teachers and professionals women can wear them in their offices. Here I have posted pictures of all Stylo Shoes winter designs 2017.
The colors are stunning and according to the choice of girls. Sincerity is very important for fame or popularity. Through Stylo you can remain in touch with latest fashion. The footwears are perfect with casual as well as formal dresses. In this collection you will find slippers in all shades. First image is black heel looking stylish and gorgeous. Pakistani Stylo Shoes collection for winter is pure and valuable. Girls also wear fashionable sneakers these days. The classic styles are presented here for fashion lovers. All the pumps are flat but some have very short heel. They are made with printed fabric and decorated with ribbons. It is the favorite brand of all the models and actresses of showbiz. Here you will see different pumps in different colors such as pink, brown, black, white, blue etc. Increase your beauty with famous Stylo Shoes styles of winter 2017.


Niantic Inc. the developer behind the successful Pokemon GO mobile game is releasing a new update for the aforementioned title, on both Android and iOS platforms. Said update includes a new but expected feature which has already been confirmed by the developers last week, some quality of life improvements, as well as a handful of specified and unspecified bug fixes.
As readers might recall, earlier this month Niantic Inc. has confirmed that a new "catch bonus" mechanic will be implemented to Pokemon GO in a future update, and sure enough the software package in question is now distributed to all Pokemon GO players on both iOS and Android platforms. Following the update, trainers will now earn a catch bonus when capturing more of a specific Pokemon type, so for example, capturing Abra multiple times will now increase your chances of encountering the rarer, evolved Kadabra. Furthermore, the update introduces new changes to Gym Training, and trainers will now be able to bring six Pokemon to do battle at friendly Gyms. It's worth noting that the CP of the Pokemon fought by trainers may be "temporarily adjusted lower for your training session". Aside from these new additions to the augmented world of Pokemon GO, the update also includes a quality of life improvement for the Egg and Incubator screens. These menus will now periodically update the distance walked without trainers having to close and reopen the said menus, which should definitely save players some hassle. Along with these changes, Niantic's newest update fixes several audio issues, it decreases the evolution animation time, and includes other, unspecified minor bug fixes.
The latest Pokemon GO update for Android bumps the app's version in the Google Play Store to 0.41.2, and pushes the iOS build to version 1.11.2, but as far as availability is concerned, keep in mind that the update might become available sooner in some regions than others. With that being said, make sure you check the Play Store on your own device to determine whether the update has reached your region yet, and otherwise, keep a close eye on the application version in the Play Store.


One Alberta labour group says it doesn't believe the provincial finance minister when it comes to CPP.
In a letter published in a Charlottetown newspaper Sunday, Gil McGowan with the Alberta Federation of Labour says Ted Morton does not speak for most Albertans, who want pension reform.
He says only 33 per cent of Albertans are covered by a pension plan, less than the national rate of 38 per cent.


15 questions linked to/from How do I troubleshoot Emacs problems?
Every time I open a new file in emacs, hl-line-mode is enabled. I have put (global-hl-line-mode -1) (hl-line-mode -1) in my init.el, but to no avail. What am I doing wrong???
How to fix reftex-toc numbering?