Who Should Pay For Source Code Availability?

[kristoff]

One important thing is that Forgejo’s federation features are about making it more seamless to search / get notifications across instances and do other social stuff with a bit less friction than normal. This doesn’t address resilience/availability of repositories in any way.

[KilianHanich]

@Sze

If your users are complete novices, there is also the option of building a report feedback form directly into your application and have it send the report to a self-build/hosted issue tracker via some api. At least for some apps that would work.
(And you could either have that use decentralized or a centralized system based on what you want to support for that (basically it could be a freenet private river-chat-room between the user and developer built into your application))

This would make it difficult to actually communicate with them for follow up questions, but maybe this would work? Not sure about that, but I guess it depends on the implementation.

@Sze

Also I think if you push the user knowledge/familiarity-level towards zero you can always argue against any kind of newish solution.

This has nothing to do with familiarity level, only user knowledge level.
Just so that we are on the same page, I am speaking about the type of user who call a simple monitor a computer because they don’t know the difference. Their tech literacy is straight up non-existent.
Telling them that they need to Radicle instance before they can create an issue is just a too high bar.

[Nae]

@KilianHanich

This would make it difficult to actually communicate with them for follow up questions, but maybe this would work? Not sure about that, but I guess it depends on the implementation.

Put an optional email in the in-app feedback form. It’s non-trivial to tie up the email communication with Radicle, but the centralized/distributed nature of the system doesn’t alter the problem in a major way: the in-app feedback is basically interacting with backend server that interacts with a well-known Radicle node (probably on the same VM) that create/update issue on the behalf of the app user.

@KilianHanich

Their tech literacy is straight up non-existent.

With that knowledge level, I guess you’re dealing with a very niche domain where you want feedback from sophisticated user that know about the domain, but might be programming illiterate. I think email based communication would closes the gap.