♻️ @grahamdowns@mastodon.africa Smartphones are very expensive in #Africa. In South Africa specifically, lots…
Smartphones are very expensive in #Africa. In South Africa specifically, lots of people still use feature phones. In fact, some companies are producing NEW feature phones. Some of them run #Android, some run completely home-grown operating systems, but most have no touch screens and you're stuck with traditional [1-9]#* keypads where you press and hold a number to get letters, remember those?
Browsing the #Internet on those devices is painful, to say the least.
Oh, people have data. Data's coming down in price nicely. I mean, it could be better, and it probably will get better, but for the most part, Internet access is fairly easy to come by.
It's the devices required to make use of the Internet which are beyond the reach of many people on this continent.
https://techcentral.co.za/africa-has-a-feature-phone-problem/235714/?utm_source=Mastodon
Disappointed that I can't follow #lemmy users/communites from #GNUsocial nor follow GS #groups from #lemmy. I think #kbin may work, but it's really unstable so it's hard to tell. !sns
I meant to respond to this directly, sorry for the late response. I think that there should be an option for both long-term retaining of data and index-ability by search engines.
For fedi to be a replacement of certain microblogging 'dot-cons' I think it needs to provide the above as options, via admin approval. I feel that instructing people to setup a #microblogging site is counter-productive, does fedi a disservice, and raises barriers for people to engage with there community, both local and global. I understand that maybe not all user will be granted such privileges (I am thinking shitposters, frequent image posters, and for-profits that don't donate) but there should be an option for storage and for search engine index-ability (understanding that all servers are fallible and to backup your data for extreme cases of server going offline).
It should however be up to the admin to grant such privileges, we also don't want bad-faith actors having that capability for /obvious/ reasons, but it is needed in GNUSocial, in the long-term.
on my personal #GNUsocial server, @i@gnu.jimfulner.com, I try to reset my password, but the recovery email is so slower that by the time I get it, the token has already expired. Anone have a recommendation? @gnusocialjp@administrator @lnxw48a1@nu.federati.net @lxo
@fu From #GNU_social, I only see a few of your posts in the thread. As you may know, #Diaspora's protocol is different from #OStatus, so the D* posts do not cross over.
But there's more going on. Years ago, when I hosted a #Friendica instance, posts from ~F to OStatus appeared natively. Now they don't. For example, almost never will a mention or reply from ~F to GS appear in the recipient's replies stream. This doesn't only happen on GS, though.
On Pleroma instances, ~F posts (at least from #libranet.de) appear with delays of 2-12 hours or more, sometimes out of context, usually out of order. They also sometimes change the scope when they reply to a scope limited post.
I have a ~Friendica account on libranet.de, but I barely ever use it because _everything_ seems to be broken and it frustrates me every time I try to use it. I should probably close it and check to see whether the issues are local to libranet.de or something common to all Friendica instances.
In the beginning, there was Laconica, which later became known as StatusNet. A massive amount of the work that went into this is due to Evan Prodromou ( @evan ) , who is now spearheading an effort to standardize work on a communication protocol with the W3C Social Working Group.
As a networking project, it was the first public implementation of the communication protocol known as OpenMicroBlogging, which later evolved into the OStatus protocol. These technologies provided a significant building block for future federated networking projects to study and reference.
In terms of how StatusNet was used, it resembled an early version of Twitter, with the added benefit of group functionality. What made it unique is that users on one Laconica server could communicate with users on completely different servers.
Getting to know the #gnusocial internals was fun. I managed to get composer autoloading (PSR-4), active orm and a cli pysch powered REPL. I think it would be easier to start from scratch than bring gnusocial into the modern php era.
IMHO #Mastodon is the least user friendly and has the fewest featues, except maybe for #Honk but it specifically has a goal of having near 0 features, always purple, and always stable. Try out https://fe.soapbox.pub and you log in with your mastodon account!