Sur d’autres sites (8940)

• Podcast Producer 2 REST api

  11 septembre 2009

  I’ve been working on documenting the REST api that PCP2 uses for client server communication as part of a new project. I thought it might be useful to other folks. Consider this a work in progress - I’ve only documented the workflow for doing a multisource recording so far. Follow the job for the info.

  Each section gives a sample command and a sample response.

  All pages are behind basic HTTP auth.

  General sequence of events

  * get workflow list
  * get cameras
  * request status for camera (including thumbnail)
  * start cameras
  * create recording enclosure
  * stop cameras, provide submission_UUID returned by above step, include title

  ---

  *URL : https://pcpserver:8170/podcastproducer/info

  *Type : GET

  *Content : version=2

  *Response :
  <pre>
  <podcast_producer_result>
  <action>index</action>
  <status>success</status>
  <plist version="1.0">
  <dict>
  <key>server_version</key>
  <string>2.0</string>
  <key>http_auth_type</key>
  <array>
  <string>basic</string>
  <string>digest</string>
  <string>kerberos</string>
  </array>
  <key>krb_service_principals</key>
  <array>
  <string>pcast/x101-186-103-dhcp.cla.umn.edu@X101-186-103-DHCP.CLA.UMN.EDU</string>
  </array>
  <key>server_uuid</key>
  <string>DB31DA49-10AE-472C-B3B9-86A8F8112399</string>
  <key>cluster_members</key>
  <dict>
  <key>F1021B98-7E7E-44FB-8EB1-E0DA1885D5BA</key>
  <dict>
  <key>date_added</key>
  <string>Tue Sep 01 10:23:49 -0500 2009</string>
  <key>last_update</key>
  <string>Tue Sep 08 10:35:17 -0500 2009</string>
  <key>server_host</key>
  <string>x101-186-103-dhcp.cla.umn.edu</string>
  <key>server_port</key>
  <string>8170</string>
  <key>tunnel_agent_host</key>
  <string>x101-186-103-dhcp.cla.umn.edu</string>
  <key>tunnel_agent_port</key>
  <string>8175</string>
  <key>network_addrs</key>
  <array>
  <string>128.101.186.103</string>
  </array>
  </dict>
  </dict>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/workflows
  * Type : GET
  * Content : version=2&language=en
  * Response :
  <pre>
  <podcast_producer_result>
  <action>index</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>user_fullname</key>
  <string>podcast</string>
  <key>user_shortname</key>
  <string>podcast</string>
  <key>workflows</key>
  <array>
  <dict>
  <key>name</key>
  <string>Montage</string>
  <key>title</key>
  <string>Montage</string>
  <key>description</key>
  <string>Montage workflow</string>
  <key>uuid</key>
  <string>F797D54D-1539-42AA-B6AC-3CB3A4C15EF5</string>
  <key>version</key>
  <string>2.0</string>
  <key>editor</key>
  <string>Podcast Composer</string>
  <key>sources</key>
  <array>
  <dict>
  <key>contentTypes</key>
  <array>
  <string>com.apple.quicktime-movie</string>
  <string>com.adobe.pdf</string>
  <string>com.apple.iwork.keynote.key</string>
  <string>com.apple.iwork.pages.pages</string>
  <string>org.openxmlformats.wordprocessingml.document</string>
  <string>com.microsoft.word.doc</string>
  <string>org.openxmlformats.presentationml.presentation</string>
  <string>com.microsoft.powerpoint.ppt</string>
  <string>com.microsoft.bmp</string>
  <string>com.compuserve.gif</string>
  <string>public.jpeg-2000</string>
  <string>public.jpeg</string>
  <string>com.adobe.pdf</string>
  <string>com.apple.pict</string>
  <string>public.png</string>
  <string>com.adobe.photoshop-image</string>
  <string>com.sgi.sgi-image</string>
  <string>com.truevision.tga-image</string>
  <string>public.tiff</string>
  </array>
  <key>description</key>
  <string>Any Document</string>
  <key>isFolder</key>
  <true/>
  <key>isOptional</key>
  <false/>
  <key>sourceTypes</key>
  <array>
  <string>File</string>
  </array>
  </dict>
  </array>
  <key>user_requirements</key>
  <array>
  <string>Title</string>
  <string>Description</string>
  </array>
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  <dict>
  <key>name</key>
  <string>Single Source</string>
  <key>title</key>
  <string>Single Source</string>
  <key>description</key>
  <string>Single Source workflow</string>
  <key>uuid</key>
  <string>DEFA1587-A650-426E-92DA-01C5EB811705</string>
  <key>version</key>
  <string>2.0</string>
  <key>editor</key>
  <string>Podcast Composer</string>
  <key>sources</key>
  <array>
  <dict>
  <key>contentTypes</key>
  <array>
  <string>com.apple.quicktime-movie</string>
  </array>
  <key>description</key>
  <string>Any Video</string>
  <key>isFolder</key>
  <false/>
  <key>isOptional</key>
  <false/>
  <key>sourceTypes</key>
  <array>
  <string>Video</string>
  <string>Screen</string>
  <string>Audio</string>
  <string>File</string>
  </array>
  </dict>
  </array>
  <key>user_requirements</key>
  <array>
  <string>Title</string>
  <string>Description</string>
  </array>
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  </array>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>
  ----

  * URL : https://pcpserver:8170/podcastproducer/cameras
  * Type : GET
  * Content : version=2
  * Response :
  <pre>
  <podcast_producer_result>
  <action>index</action>
  <status>success</status>
  <plist version="1.0">
  <dict>
  <key>cameras</key>
  <array>
  <dict>
  <key>name</key>
  <string>150-A Camera</string>
  <key>uuid</key>
  <string>307682A5-B552-4AFA-B7E2-3811D772C9A1</string>
  <key>connected_to_member_uuid</key>
  <string>F1021B98-7E7E-44FB-8EB1-E0DA1885D5BA</string>
  <key>in_use</key>
  <string>false</string>
  <key>recording_status</key>
  <string>online</string>
  <key>preview_url</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/307682A5-B552-4AFA-B7E2-3811D772C9A1.jpg</string> ;
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  <dict>
  <key>name</key>
  <string>150-A Epiphan</string>
  <key>uuid</key>
  <string>CE610AB0-CA50-49EB-8FFE-78E57CDCA550</string>
  <key>connected_to_member_uuid</key>
  <string>F1021B98-7E7E-44FB-8EB1-E0DA1885D5BA</string>
  <key>in_use</key>
  <string>false</string>
  <key>recording_status</key>
  <string>online</string>
  <key>preview_url</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/CE610AB0-CA50-49EB-8FFE-78E57CDCA550.jpg</string> ;
  <key>access_control_entries</key>
  <array>
  </array>
  </dict>
  </array>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/start
  * Type : POST
  * Content : action=pause&version=2&camera_name=150-A%20Camera&controller=cameras
  * Response :
  <pre>
  <podcast_producer_result>
  <action>start</action>
  <status>success</status>
  <results>OK</results>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/status
  * Type : POST
  * Content : delay=0&action=start&version=2&camera_name=150-A%20Epiphan&controller=cameras
  * Response :
  <pre><podcast_producer_result>
  <action>status</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>preview</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/307682A5-B552-4AFA-B7E2-3811D772C9A1.jpg</string> ;
  <key>preview_image_data</key>
  <string>RAW JPEG DATA RAW JPEG DATA RAW JPEG DATA RAW JPEG DATA RAW JPEG DATA</string>
  <key>recording_status</key>
  <string>online</string>
  <key>started_at</key>
  <string>Tue Sep 08 09:31:40 -0500 2009</string>
  <key>stopped_at</key>
  <string>Tue Sep 08 09:32:10 -0500 2009</string>
  <key>elapsed</key>
  <string>41</string>
  <key>last_error</key>
  <string>805306368</string>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/pause
  * Type : POST
  * Content : action=pause&version=2&camera_name=150-A%20Camera&controller=cameras
  * Response :
  <pre><podcast_producer_result>
  <action>status</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>preview</key>
  <string>https://x101-186-103-dhcp.cla.umn.edu:8170/podcastproducer/previews/307682A5-B552-4AFA-B7E2-3811D772C9A1.jpg</string> ;
  <key>recording_status</key>
  <string>online</string>
  <key>started_at</key>
  <string>Tue Sep 08 09:31:40 -0500 2009</string>
  <key>stopped_at</key>
  <string>Tue Sep 08 09:32:10 -0500 2009</string>
  <key>elapsed</key>
  <string>41</string>
  <key>last_error</key>
  <string>805306368</string>
  </dict>
  </plist>
  </podcast_producer_result></pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/cameras/stop
  * Type : POST
  * Content : workflow_name=&UserMetadata_Description=&submission_uuid=7497E3AC-0A75-4C7C-8C66-26294C9274FE&action=stop&version=2&camera_name=150-A%20Epiphan&controller=cameras&UserMetadata_Title=Test123
  * Response :
  <pre><podcast_producer_result>
  <action>stop</action>
  <status>success</status>
  <results>OK</results>
  </podcast_producer_result>
  </pre>

  ---

  * URL : https://pcpserver:8170/podcastproducer/recordings/create
  * Type : POST
  * Content : version=2&workflow_uuid=C6EF52A7-04E3-477D-9F38-6B61F108D7B9
  * Response :
  <pre>
  <podcast_producer_result>
  <action>create</action>
  <status>success</status>
  <results>OK</results>
  <plist version="1.0">
  <dict>
  <key>workflow_uuid</key>
  <string>C6EF52A7-04E3-477D-9F38-6B61F108D7B9</string>
  <key>recording_uuid</key>
  <string>FD5A1459-F7CE-41FA-8155-049DF774298B</string>
  <key>submission_uuids</key>
  <array>
  <string>A626D8E4-E439-4E57-9982-DB4BD035CB41</string>
  <string>CFBCCB74-A41F-42D3-BEAA-58165B1116C6</string>
  </array>
  </dict>
  </plist>
  </podcast_producer_result>
  </pre>

• Q&A : An interview with Matomo founder, Matthieu Aubry

  20 novembre 2018, par Joselyn Khor — About, Community

  Hey everyone ! Joselyn here. As always the views of our community remain top of mind. So to make sure you guys know the thinking behind these new projects, we reached out to Matomo’s founder, Matthieu, to ask questions you might want answered. Please check it out below !

  Hi guys, it’s Matthieu ! Here to answer some questions about the rebrand and the future of Matomo and Innocraft.

  What’s upcoming ?

  We’ve been busy implementing our rebrand into all aspects of Matomo and there’s also our new website, which is launching today ! The new website will help people better understand what Matomo is and how they can benefit from using modern web analytics.

  Why was Matomo and Innocraft brought onto one website ?

  In the past the separation caused a bit of confusion so we’re taking this as a chance to unite both the business brand, Innocraft and community brand, Matomo, on one website. Putting our focus on one brand, Matomo, makes it easier for people to see us with fresh eyes. We have a community side as well as a business side and while the community is still incredibly important to us, we find we have a powerful analytics tool that is capable of helping businesses too.

  Is Matomo becoming commercial or turning corporate ?

  No. nothing is changing. Matomo is still an open-source project and community. Although we’ll have a pricing page and “start free trial” on the new website brought over from Innocraft.cloud, the Matomo community will still play the biggest part on the Matomo website. We have dedicated sections focused on Community and On-Premise.

  The rebrand exercise helped us gain a refreshed perspective. After reflecting on how far we’ve come, we can feel more confident about Matomo Analytics itself as a platform. We believe it’s a great chance to bring that confidence into the brand and vision. We are proud that it’s an awesome open-source platform and at the same time it’s also powerful as a tool for businesses.

  Why is there no ‘download for free’ button on the homepage ?

   

  
  We feel many users coming to the site will get confused about our hosting options (Cloud and On-Premise) which is something you don’t usually consider when choosing an analytics tool.

  The reason for us to not have that button is when people see a “download for free” button on the homepage next to a “try it for free” button, it creates confusion. For those who do choose to download Matomo often become confused when they are left with a .zip file unaware how to install it and the technical requirements of self-hosting. We feel presenting our users with the simplest installation option first will give them the best chance possible to try Matomo to its full potential, without cost.

  And you can still find the link to Download Matomo in the footer of each page.
  

   

  Is Matomo still free to download and have forever ?

  Absolutely. The free open-source download can be found on the On-Premise section of the website, or download Matomo here.

  Why is it important to have a business behind the project ?

  There’s the reality that we have to make money in order for the Matomo project to survive … and thrive. The reason we still need a business side (Innocraft) is to fund and sustain the Matomo project. Whenever people purchase premium features, this helps finance the development of Matomo for our community.

  Because of the business we’re able to continually maintain and develop Matomo for you guys as well as future users. For example, the next release Matomo 3.8.0 is already mostly developed and will bring lots of interesting features too, like the two-factor authentication, Brute Force Protection, failed tracking requests reporting, lots of JavaScript tracker improvements, a new total summary row below reports, and many more security fixes, bug fixes, and other new features.

  So we see a business being very helpful in supporting our open-source community. Without a business side, our free, open-source project would not be able to survive.

  How will you protect the Matomo project ?

  We’ve ensured the Matomo project will be protected for the future as we wish to turn it into a not-for-profit foundation.

  We’ve also got a safeguard where the open-source code will stay under a GPL license forever. This is so we can guarantee, that no matter what happens, the Matomo project itself will stay completely free software.

  Is there a way for people to help ?

  There are heaps of ways to help ! You can help other Matomo users in the forums, contribute to fixes on GitHub, leave a great review (e.g. alternativeTo), help look for bugs with our Security Bounty Programme or participate and spread the word about Matomo in our community social media pages – Mastodon, Facebook, Twitter. Telling your friends about us would be very helpful too !

  What’s planned for the future ?
  We’ve worked hard to become the #1 open-source analytics platform (1.4 million websites use Matomo today), but now we need to empower even more individuals and businesses to take back control of their own data.

  Showing our community that we have a powerful platform is crucial, but alongside that our values are what define us. User privacy is still of utmost importance and we’re here to make it known that power needs to rest in the hands of people and not large corporations.

  You can rest easy knowing you’re doing your part in using trustworthy and dependable tools. By joining many other companies who are growing this movement to decentralise the Internet, we can build a safer, online world together.

  Join this analytics revolution and let us know what you think about Matomo !

• Nexus One

  19 mars 2010, par Mans — Uncategorized

  I have had a Nexus One for about a week (thanks Google), and naturally I have an opinion or two about it.
  

  Hardware

  With the front side dominated by a touch-screen and a lone, round button, the Nexus One appearance is similar to that of most contemporary smartphones. The reverse sports a 5 megapixel camera with LED flash, a Google logo, and a smaller HTC logo. Power button, volume control, and headphone and micro-USB sockets are found along the edges. It is with appreciation I note the lack of a front-facing camera ; the silly idea of video calls is finally put to rest.

  Powering up the phone (I’m beginning to question the applicability of that word), I am immediately enamoured with the display. At 800×480 pixels, the AMOLED display is crystal-clear and easily viewable even in bright light. In a darker environment, the display automatically dims. The display does have one quirk in that the subpixel pattern doesn’t actually have a full RGB triplet for each pixel. The close-up photo below shows the pattern seen when displaying a solid white colour.

  

  The result of this is that fine vertical lines, particularly red or blue ones, look a bit jagged. Most of the time this is not much of a problem, and I find it an acceptable compromise for the higher effective resolution it provides.

  Basic interaction

  The Android system is by now familiar, and the Nexus offers no surprises in basic usage. All the usual applications come pre-installed : browser, email, calendar, contacts, maps, and even voice calls. Many of the applications integrate with a Google account, which is nice. Calendar entries, map placemarks, etc. are automatically shared between desktop and mobile. Gone is the need for the bug-ridden custom synchronisation software with which mobile phones of the past were plagued.

  Launching applications is mostly speedy, and recently used apps are kept loaded as long as memory needs allow. Although this garbage-collection-style of application management, where you are never quite sure whether an app is still running, takes a few moments of acclimatisation, it works reasonably well in day to day use. Most of the applications are well-behaved and save their data before terminating.

  Email

  Two email applications are included out of the box : one generic and one Gmail-only. As I do not use Gmail, I cannot comment on this application. The generic email client supports IMAP, but is rather limited in functionality. Fortunately, a much-enhanced version, K-9, is available for download. The main feature I find lacking here is threaded message view.

  The features, or lack thereof, in the email applications is not, however, of huge importance, as composing email, or any longer piece of text, is something one rather avoids on a system like this. The on-screen keyboard, while falling among the better of its kind, is still slow to use. Lack of tactile feedback means accidentally tapping the wrong key is easily done, and entering numbers or punctuation is an outright chore.

  Browser

  Whatever the Nexus lacks in email abilities, it makes up for with the browser. Surfing the web on a phone has never been this pleasant. Page rendering is quick, and zooming is fast and simple. Even pages not designed for mobile viewing are easy to read with smart reformatting almost entirely eliminating the sideways scrolling which hampered many a mobile browser of old.

  Calls and messaging

  Being a phone, the Nexus One is obviously able to make and receive calls, and it does so with ease. Entering a number or locating a stored contact are both straight-forward operations. During a call, audio is clear and of adequate loudness, although I have yet to use the phone in really noisy surroundings.

  The other traditional task of a mobile phone, messaging, is also well-supported. There isn’t really much to say about this.

  Multimedia

  Having a bit of an interest in most things multimedia, I obviously tested the capabilities of the Nexus by throwing some assorted samples at it, revealing ample space for improvement. With video limited to H.264 and MPEG4, and the only supported audio codecs being AAC, MP3, Vorbis, and AMR, there are many files which will not play.

  To make matters worse, only selected combinations of audio and video will play together. Several video files I tested played without sound, yet when presented with the very same audio data alone, it was correctly decoded. As for container formats, it appears restricted to MP4/MOV, and Ogg (for Vorbis). AVI files are recognised as media files, but I was unable to find an AVI file which would play.

  With a device clearly capable of so much more, the poor multimedia support is nothing short of embarrassing.

  The Market

  Much of the hype surrounding Android revolves around the Market, Google’s virtual marketplace for app authors to sell or give away their creations. The thousands of available applications are broadly categorised, and a search function is available.

  The categorised lists are divided into free and paid sections, while search results, disappointingly, are not. To aid the decision, ratings and comments are displayed alongside the summary and screenshots of each application. Overall, the process of finding and installing an application is mostly painless. While it could certainly be improved, it could also have been much worse.

  The applications themselves are, as hinted above, beyond numerous. Sadly, quality does not quite match up to quantity. The vast majority of the apps are pointless, though occasionally mildly amusing, gimmicks of no practical value. The really good ones, and they do exist, are very hard to find unless one knows precisely what to look for.

  Battery

  Packing great performance into a pocket-size device comes with a price in battery life. The battery in the Nexus lasts considerably shorter time than that in my older, less feature-packed Nokia phone. To some extent this is probably a result of me actually using it a lot more, yet the end result is the same : more frequent recharging. I should probably get used to the idea of recharging the phone every other night.

  Verdict

  The Nexus One is a capable hardware platform running an OS with plenty of potential. The applications are still somewhat lacking (or very hard to find), although the basic features work reasonably well. Hopefully future Android updates will see more and better core applications integrated, and I imagine that over time, I will find third-party apps to solve my problems in a way I like. I am not putting this phone on the shelf just yet.