!developers In the last release, the old API became worse again. The api/friendica/notification is not existing anymore despite being in the documentation. The API /conversation/show have in_reply_to_I'd which make not sense. In the API /statuses/friends_timeline the news have three user objects which are all the same, even for reposts. For posts with embedded content the images are not in the attachments as was the case in earlier versions.
All this leads me to the conclusion, that these APIs are not in the developers focus, are not tested afterbchanges and degrade over time.
Are App developers required to use the Mastodon API?
Cheers, Marco
Kann mich nur aufregen über den Unsinn, den Tim Pritlove verbreitet...
Logbuch:Netzpolitik: LNP420 Digitalisierungsfehler logbuch-netzpolitik.de/lnp420-…
Nice podcast with a deep dive into Akonadi: GNU World Order Linux Cast: gnuWorldOrder_443
gnuworldorder.info//audiophile…
@KDE
Purism, whats wrong with your build process? The name of the program is gnome 42 (as required by apt), not gnome 46... ☟
that package is part of a meta package called: librem5-base, that pulls default packages to be installed on a pureOS image for a Librem 5. And also sets some default configs.
It's not a gnome package per se.
Some of the packages that are installed using that metapackage are from gnome yes, but not all.
And that meta package; since it is not a gnome package, follows it's own version scheme.
Wieso ist der Hub auch wieder nur auf Github? So kann ich meine APP weder auf Flathub noch auf AppimageHub veröffentlichen. Zum Glück kann man auch dezentrale Repos hosten. Aber ohne Microsoft-/Github-Account hat man keinen Zugang zu den zentralen Repositories...
AppImageHub appimage.github.io/apps/
Windows 11 blocks Edge browser competitors from opening links
Wenn die Gesundheitsämter offenbar die Nachverfolgung wegen Überlastung aufgeben, können wir dann auch bitte das Theater mit der Luca-App sein lassen und stattdessen die Verwendung der CWA/CCTG verpflichten? Diese braucht nicht das Nadelöhr Gesundheitsamt...
Land of the free, home of the brave:
Gunshot Victims Wait as Horse Dewormer Overdoses Overwhelm Hospitals - Rolling Stone: rollingstone.com/politics/poli…
Hi there,
I just uploaded a new version of Friendiqa to my private Fdroid repo at ma-nic.de/fdroid/repo and to the Playstore at play.google.com/store/apps/det…
Most important changes is the ability to follow/unfollow contacts isnide the app due to the new APIs in Friendica 2021.07.
Unfortunately I had to hand over my signing key to Google due to the new App Bundle requirement in the Playstore. In theory Google can now install a changed version on your device without you knowing from the changed signing key.
The version in the Fdroid has the same signing key.
Müssen die Friendica Admins in Zukunft auch erst mit Usern diskutieren, bevor sie sie löschen?
Retrouve la Chose tout au long de l'été de l'est à l'ouest dans différents lieux et dates.
Nous présenterons la Chose qui porte une critique de l’ordre électrique et de la transition énergétique. Ce sera l'occasion de raconter qui on est, d'où on vient et ce que l'on fait. Ça se passera au camp les Rayonnantes.
Savez-vous comment les personnes handicapées naviguent-elles sur les sites web ?
Avez-vous vu le bouton "Contact accessibilité" en haut du site Mobilizon ? Savez-vous à quoi il correspond ?
Les questions autour de l'accessibilité numérique vous intéressent-elles ?
Savez-vous comment rendre des sites accessibles ?
Pour parler accessibilité numérique, venez découvrir le nouveau projet de Koena en partenariat avec Framasoft !
Il suffit de cliquer sur ce lien pour accéder au webinaire !
NB. Si vous avez des besoin spécifiques ou si vous avez des soucis avec la visio, vous pouvez appeler Koena sur le +33 (0)9 72 63 21 28
Il s'agit d'une plateforme de médiation, accessible via les sites Mobilizon.fr, Keskonfai et Colibris. Cette plateforme est en phase d'expérimentation jusqu'au mois de septembre, c'est donc le moment de la tester !
Pendant ce webinaire, des membres de l'équipe Koena et Mobilizon, feront des démos de leurs sites respectifs.
Vous aurez également la chance de tester la plateforme de médiation avec l'aide de l'équipe Koena.
Si le créneau horaire 9h - 9h30 ne vous convient pas, vous trouverez d'autres créneaux :
Nous avons hâte d'échanger avec vous sur l'accessibilité et l'inclusion numérique !
Wie geil ist das denn? 280.000 für die PARTEI!
Deutscher Bundestag - Parteispenden über 50.000 € - Jahr 2021 bundestag.de/parlament/praesid…
I just published a Flatpak of the Friendiqa client at friendiqa.ma-nic.de/Desktop.ht…
You can test it and give me feedback.
In the last version we transformed the coding for the Twitter API and rebuilt them in the new class structure. I tested each endpoint as far as it was possible, but of course problems can occur.
Please report any issues.
Concerning the future: Currently the Mastodon- and the Twitter-API are using different id values for the items. This will eventually change. Then it will make sense to use all API flavours in a wild mix. It is not planned to deprecate the Twitter API. The opposite is true. It should be now possible to register via OAuth and to use any part of the API.
I am not on github and cannot open issues there. In the current state of the API it does not make sense to publish a new version of Friendiqa with the Twitter API.
But honestly, does it make sense to support so many different APIs with the limited developer ressources that Friendica has? In my opinion it would make sense to support only one set (probably the more advanced Mastodon set for messages with additional options like permissions) and an additional set for Friendica specific things like groups, photos, events,... I experienced difficulties with APIs after almost every release in the past, because the APIs are not in the developers focus.
Further update: Most issues should be resolved now, please have a look here: github.com/friendica/friendica…
Concerning the bookmark functionality, please have a look at the endpoints of the Mastodon API. There we have the endpoints
POST /api/v1/statuses/:id/bookmark
andPOST /api/v1/statuses/:id/unbookmark
. The API endpoints are now interchangeable concerning the item id.Please have in mind that you have to remove and re-add the account since the item id has changed.