AboutFtDesktop

This page is primarily about the collection of function I maintain, not the use of third party solutions like Skype or Zoom, which I use as an ordinary free level user.

Desktop Sharing Major Function

Guacamole, the Apache desktop server is the default and only fully integrated backend for this major function. If an SAR session is active, clicking the desktop link on the doorbell should go to the guac server instead of this article. A VT common carriers' version may be used instead if supported, eg. Skype or Zoom, if it is free and works well. In the case of offers of service at S class, guacamole from the doorbell is only support path.

Tips

The following can make for a smoother sharing experience. At least token entitlement will be necessary before any service can proceed.

Choose mode of interaction

Ft Doorbell

The Ft doorbell fronts the selected VT provider and is the default means of live interaction. For authenticated SAR (single authentication realm) users, the smart doorbell operates by analogy with a physical one.

Text

While I may answer the doorbell with video enabled, the default is voice plus text with video by mutual agreement. Just being developed, the conversational agents, mixing streams of my live and automated consciousness, will later be the main service channel.

Face-to-Face

Jitsi is provided free from these domains. A professional services clients VT provider is acceptable but I don't keep any 3rd party VT running so it needs to be arranged.

Phone

Like most people by now I don't answer calls on my phone(s) from unknown callers so let me know if that is your preferred mode. A version of the doorbell is embedded in the DS smartphone app.

Have hosting authentication ready

In PWYWGs ...

You shouldn't share your hosting and other service provider login info but have it ready to use on your side of things or use it before or outside screen sharing.

In a regular biz case ...

Your F class capitation includes provisioning at the system limits. For over these quotas you can either use your AWS, Azure, GCP or Linode accounts or be billed monthly. Information needed to act as your proxy in the first case is stored encrypted in your DCMS profile and is not known in plaintext only to us to common usage with passwords. The order in which I am implementing cloud vendor support is Linode, AWS, GCP and Azure.

Be at an actual desktop

Tablets such as iPad Pro may be supported later but for now an actual Linux, Mac, or Windows desktop is required.

Close pornhub tabs

Just kidding, but you may want to check if anything sensitive on the desktop needs to be adjusted for the session.

---

Ft Common Carrier

Tele is marque for the bundling of videotelephony (VT) and screen sharing as the Ft major function, commonly embedded in the domains CMS and domain space generally.

With origins going back past the Flash Red5 ofla stuff to more recent Skype and lately with Jitsi as default VT/desktop sharing, the first commercial platform target, Ft is simply a marque for streaming I use when developing that function. In the current usage, Red5 (no longer supported ofc) would be the Common Carrier for the VT major function. The other major function of Ft is desktop sharing. Ft abstracts these major functions to support various backends.

Jitsi is currently used for the videotelephony function provided by me and is therefore the default.

Secure Connections

Your connection is secure, only SAR users can connect to the guacamole server or use the doorbell.

Registration with Google or Apple from the app is free. Manual registration is deprecated but there is a path to it from devops1.