Don't mine, I just need a place to publish a #Retribute video
Retribute Profiles, second draft, request for comments
#Retribute Profiles are the second thing we need to standardize, and I've put some effort lately to come up with a basic spec draft to start a discussion.
The idea is to standardize how Retribute information is embedded and extracted from creators websites and profiles, before being displayed to contributors.
- Human readable version: https://dev.funkwhale.audio/retribute.me/spec/blob/profiles-spec/specs/retribute-profiles-format.md
- Merge request (for inline comments, review, etc.)
- Forum thread (for discussion if you don't want to use Gitlab): https://governance.funkwhale.audio/d/cN3fYvL8/retribute-profiles-specification
I'm looking for people to read, review and submit feedback regarding this document. Is it understandable? Is it readable? Does it look realistic from your point of view? Does it leaves unanswered questions? Etc.
I haven't been posting much about #Retribute lately. But the project is still there and running.
We have text meetings every week on https://riot.im/app/#/room/#retribute:matrix.org.
The current milestone is to design and launch a small website by the end of september to introduce the project and formalize a bit more the main concepts and goals of the project.
The first spec (Suggestions Feed) is still open for review and we had some interesting discussions already.
So we're making progress, but it's not easy to see right now if you're not in the loop ;)
So this brings me to the next part of this post: if you want to be in the loop, you can! And we need you!
Either on Matrix (https://riot.im/app/#/room/#retribute:matrix.org) or on our forum (https://governance.funkwhale.audio/g/L4AfDozC/funkwhale-retribute).
Or both, if you're feeling adventurous ;)
Retribute, Suggestions Feed Spec initial draft, request for comments
This is nowhere near ready for production, but I needed to get this out of my system to eventually start a discussion and iterate from there.
The Merge Requests (if you want to post review comments there):
This first spec targets the interactions between clients and content platforms.
The idea is that #Retribute
clients (such as https://app.retribute.me) need to retrieve data from content platforms (Mastodon, Funkwhale, etc.), and we can't build a connector for each service out here.
That's were the Suggestions Feed Spec come in, to provide common ground and bring compatibility between all content platforms and Retribute clients implementing it.
This is like, my first spec ever, so I'm sure I got a lot of things wrong. But I'm confident you'll point things to me ;)
The thing is technical but not at a really low level (we're mainly talking about JSON and a bit of HTTP). And since the goal is to have something understandable and implementable by as much people and software as possible, getting diverse input will be helpful!
If you think your feedback or questions are dumb, well, they're not!
Retribute update, itch.io, profile debugger
I've managed to work a few hours on #Retribute this evening, and here is a quick (non-technical) changelog!
# Application Footer
I've added a footer at the bottom of all the pages to ensure people can find their way to our forums/source code/issue tracker/chat.
Nothing big, but still useful ;)
# itch.io support
Retribute will now successfully parse links to itch.io profiles, which will probably please our fellow game devs
Thanks to @firstname.lastname@example.org for the idea and follow-up!
# Profile debugger
As a creator, it's common to want to know what information Retribute will extract from your profile.
https://app.retribute.me/debug now offers a simple form to check what links are extracted by Retribute and hopefully help you detect potential issues.
# Cache busting
Since Retribute keeps profile data in cache for a few hours, following a discussion with @emsenn and in preparation for pinned toot support, checks done via the profile debugger also refresh any stale data we may have in cache.
All these changes are showcased in the video below, and deployed live on https://app.retribute.me
Retribute app, question for fedi users
Currentily, #Retribute extract the list of contribution platforms (patreon, etc.) from Mastodon bios and profile metadata.
I'm thinking about extending this to pinned toots, because I've seen people using them for such info too.
What's your opinion on this? If you think this is a bad idea, can you please elaborate a bit in the comments?
Retribute, the forum
Discussing on fedi is nice. But sometimes we need more than that.
That's why we're launching a dedicated Loomio group to discuss about it, structure our discussions, leverage advanced decision tools and, hopefully, move to the next steps together!
And we're doing this on top of #Funkwhale's existing infrastructure ❤️
You can of course continue to follow me, read my blog or check the #Retribute hashtag from time to time, but joining and watching this group will be easier:
See you there!
Retribute, technical blog post
#Retribute's technical overview/architecture is now described at https://eliotberriot.com/2019/06/16/retribute-technical-architecture.html
It will probably evolve with the specification effort, but should nonetheless give you a better overview of the involved components, services, entities and their interactions!
Retribute, organization poll
I'm starting to think about our community organization for Retribute. Doing it early is important.
It means we can use Funkwhale GitLab, Loomio server, pads, etc. And benefit from the existing community structure (non-profit, CoC, moderation, etc.).
It would spare us _months_ of work.
What's your opinion on building Retribute under the Funkwhale umbrella?
Retribute, technical blog post, help wanted
I'm not especially happy with this blog post, but I'm bad at technical writing anyway, so I guess it makes sense to gather feedback early :D
What do you think of this? https://pad.funkwhale.audio/retribute-technical-1
Does it gives a clear overview of the technical challenges faced by Retribute? And the potential solutions?
What's missing/not clear/weirdly put?
At the moment, #Retribute supports a dozen of retribution platforms.
But any URL found in creators profiles with a ?retribute query parameter will be collected and displayed as well.
As a creator, you can leverage this feature to advertise custom retribution platforms, e.g your personal e-shop, or your Amazon wishlist.
The about page was updated this morning to reflect this change:
Thanks @lila_bliblu for the beta-testing!
Retribute, PeerTube support
It will use your viewing history to extract donation links from channels description and support fields, as well as channel owners bio.
#Funkwhale support should be good too now (but your instance needs to be running on develop for better performance though)
If you want to learn more about #Retribute, I recommend you read this blog post I published this morning about the problems the project aims to solve and how.
It's non-technical and focuses on the bigger picture, more technical writings will come afterwards.
Retribute, first blog post, proofreading
Tonight, I've been writing a non-technical blog post about #Retribute.
Hopefully, it will shed some light on the project: how it works, why it works that way, what comes next…
If you are fluent in English or interested in the matter, would you mind proofreading it?
I'm sure there are some typos, syntax and grammar mistakes, and the copy itself could be improved!
You can edit directly on the pad at
Python, programmation asynchrone
je commence vraiment à aimer ça.
Jusqu'à maintenant, j'y avais touché que sur des applis non web (genre https://dev.funkwhale.audio/funkwhale/archiveorg-dl), mais avec #retribute, j'ai commencé à faire du web avec
C'est quand même super cool de pouvoir paralléliser les IO pour avoir un endpoint d'API que répond en 1s au lieu de 20 !
Et d'avoir un serveur beaucoup moins gourmand dans l'ensemble (car un seul worker peut traiter beaucoup plus de requêtes en parallèle)
The first iteration of the #retribute app is now officially ready 🎉
It's a web application that connect to your Mastodon account(s) and suggest you creators to tip based on your activity.
If you enjoy the concept or have some feedback, please let me know!
You can also find more about the app and how it works on the about page: https://app.retribute.me/about
Retribute, Initial Proof of Concept
You may remember I talked about automating the act of supporting creators on the fediverse, and elsewhere, a while ago (https://eliotberriot.com/blog/2018/05/11/funkwhale-content-monetization-trust/)
The video below features a basic proof of concept that uses #Mastodon profiles and favorites to suggest you creators to tip.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!