no longer supports StatusNet API, support self-hosted instances

Bug #1239900 reported by Mikael Nordfeldth on 2013-10-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)

Bug Description

Recently the service has changed software altogether, from StatusNet to

The federated community using the StatusNet software are still alive and well and not centralised around (anymore) - so instead of using the gwibber-service-identica, Online Accounts should present a way to create an account with the gwibber-service-statusnet package that allows to specify the server which runs a user's service instead of hard-coding it to a specific one.

Making anything work for the current service is an entirely different issue which I don't believe has been reported yet.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gwibber 3.7.0bzr13.04.05-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic
Uname: Linux 3.8.0-31-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Tue Oct 15 03:45:18 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-07-29 (77 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: all
 PATH=(custom, no user)
SourcePackage: gwibber
UpgradeStatus: No upgrade log present (probably fresh install)

Mikael Nordfeldth (mmn) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers