A service very much like Instagram, but federated. There seems to be quite some enthusiasm around ActivityPub-based projects in general, also including Prismo, Anfora and Funkwhale.
Best posts made by yusf
playSMS — Free and Open Source SMS Gateway
A flexible Web-based mobile portal system that it can be made to fit to various services such as an SMS gateway, bulk SMS provider, personal messaging system, corporate and group communication tools
There’s a maintained Dockerfile already.
Feature Highlights (brace yourself!)
- Multiple database engine supported (through PHP PEAR DB, included in this package)
- Send SMS to single mobile phone
- Send SMS broadcasted to a group of mobile phones, or SMS bulk
- Support sending text, flash and unicode messages
- Capable of handling large amount of SMS
- Receive private SMS to Inbox and forward it to email (mobile2web) and user’s mobile phone
- Forward single SMS from mobile to a group of mobile phones
- Provides SMS to email and email to SMS by polling mailbox
- SMS autoreply, for easy autoreplying formatted incoming SMS
- SMS board, forward received SMS to email, export output in JSON and a few other formats
- SMS command, execute server side shell script using SMS
- SMS custom, forward incoming SMS to custom apps, locally or hosted on external URL
- SMS poll, manage polling system using SMS, export output in graph, JSON and other formats
- SMS quiz, serve quizzes on SMS
- SMS subscribe, manage user subscribes to a service using SMS
- SMS sync to utilize SMSSync app
- Blacklist, stoplist and firewall plugin for SMS services protections
- Create your own features, tools, themes and gateway modules as a plugin
- Supports software gateway such as Gammu, Jasmin, Kannel and SMS Server Tools 3
- Supports bulk SMS providers such as Nexmo, Twilio and other SMS service providers
- Supports many other bulk SMS providers using Generic gateway plugin
- Supports sending/receiving SMS via another playSMS using Planet or Uplink gateway plugin
- Supports simulation gateway for testing incoming and outgoing SMS
- Supports multiple active SMSC
- Route outgoing SMS by prefix
- Route outgoing SMS per user
- Webservices for sending SMS, retrieving delivery reports, checking credits and more
- Long SMS support, length of text is configurable
- Rate SMS by destination prefix
- SMS credit system per user
- Multiple SMSC activated and routable
- Timezone settings
- Multi-language user interface (English, French, Bahasa Indonesia, Russian and a few others)
- Easily add new language for user interface
- Web-based interface
- Android app for playSMS is available, with source codes
- Multi-domain from single playSMS installation with site branding for reseller supports
RE: What's coming in 4.4
real support for federation. Imagine Cloudron being a painless way to deploy federated apps, a million Cloudrons out there all linking together
Wholeheartedly supporting this and would be willing to help out testing etc.
RE: n8n.io - Zappier, IFTTT, Integromat alternative
Though not made with exactly the same approach there's a popular request for Huginn as well.
Serve federated apps from root domain
I've written about this issue in various topics where related but now want to distill those thoughts in a dedicated one.
Various services that are federated in one way or another typically serve from the root domain. A few examples:
- Matrix, a popular federated chat service. (1 587 public servers with ∞ users)
- Mastodon, a very popular federated microblog service. (2 744 public servers with 2 270 595 users)
- PeerTube, a somewhat popular federated video streaming service with peer-to-peer content distribution. (340 public servers with 23 164 users)
- PixelFed, an emerging federated Instagram-like image service. (107 public servers with 15 966 users)
- WriteFreely, an emerging federated blogging platform. (199 public servers with 5 490 users)
- IRC, a well established chat service. (∞ public servers with ∞ users)
- Email (∞ servers with ∞ users)
Regardless of what subdomain these services are served from technically, they all require some routing via the root domain to work properly. Sure, some can be served from a subdomain but it's bad practice.
In Cloudron, support for this type of routing is currently absent except for email (which is obviously because it makes up such a central component of the Cloudron system). The routing required for federated services typically means forwarding a port or two towards the true location of the service.
The solution I imagine is that apps requiring this routing registers extra ports in their app manifests that then targets the root domain, which should still be open to serve a completely different app on that location as well. Just like email works right now alongside whatever is installed on the root domain.
Now, if Cloudron were to accomodate for this type of root domain routing then the system would be quite ideal for hosting not only the typical web apps already possible, but the whole plethora of emerging federated services as well. The numbers shows a pretty good interest in these types of services.
Let's hear it
I'd hereby like to initiate a solution oriented discussion on this topic. I would especially appreciate the views of @girish and @nebulon, but of course community members like @msbt, @murgero, @kasini and @october as well.
Latest posts made by yusf
RE: Grav CMS
Hi, I get this when trying to install a plugin:
Unable to move the library files to /app/data/user/plugins/get-id3/library/ Files are missing from the getID3 library. Please see the grav log files for more information Please manually download the library from http://www.getid3.org/ and follow the installation instructions in the README.md file for this plugin.
Grav log file only says:
[2019-12-20 23:39:44] grav.INFO: Unable to move the library files to /app/data/user/plugins/get-id3/library/  
Not sure if Cloudron related though, but it sounds like a directory permissions issue.
RE: Cloudron running low on resources.... memory - I have 20GB of ram free though
Is it taking into account the RAM requirements for each installed app which would total 29.5GB? Is this why I get this warning?
Yes. Each app all have generous amounts of dedicated memory assigned to them. I read in the docs that each app is/should be configured for around 50 concurrent users.