#Tag
This week in #FDroid (TWIF) is live too:
* More #NGI #NLnet#Mobifree funded projects
* More ways to shape #EU #DMA legislation
* #ExodusPrivacy might need a hand
* #Syncthing #SyncthingFork v2 on Android, backup and import your settings
+ 2 new apps
& 164 more updates
- 2 archived apps
On your marks, get set, Sync: https://f-droid.org/2025/09/11/twif.html
We were turned down repeatedly for all 3 projects by #Nlnet#NGI, do you think it's worth applying agen, if we do how can we shift this #blocking? Supporting Native Grassroots Projects in the Fediverse https://hamishcampbell.com/supporting-native-grassroots-projects-in-the-fediverse/
Should we apply again?
Yes, not because they’ll suddenly “get it,” but because persistence itself is part of the composting, a record, a point of pressure.
Apply and simultaneously build a parallel path of community support, donations, partnerships, volunteer time. That way, the inevitable #NLnet rejection doesn’t kill all the momentum.
Shifting the blocking? Maybe translate native ideas into their language. Bureaucracies like “deliverables,” “impact metrics,” “alignment with EU digital policy.” Wrap your radical #4opens core in a frame they can recognise: resilience, digital sovereignty, anti-disinformation, democratic participation. That’s harder for them to ignore and strengthens the “native” path.
Expose the bias. Not in a bitter way, but in a constructive one: point out the repeated rejection of grassroots-native projects while funding flows to #geekproblem/NGOs. This pressure helps them re-balance (and others will maybe notice).
If you want to help, share the 3 projects ( #MakingHistory, #IndymediaBack, #OGB) in #Fediverse channels. Frame this positively: “If we want a living #openweb, we need to fund and support native projects, not just corporate/NGO clones.” make it harder for them to keep sidelining.
Should we apply again?
Yes, not because they’ll suddenly “get it,” but because persistence itself is part of the composting, a record, a point of pressure.
Apply and simultaneously build a parallel path of community support, donations, partnerships, volunteer time. That way, the inevitable #NLnet rejection doesn’t kill all the momentum.
Shifting the blocking? Maybe translate native ideas into their language. Bureaucracies like “deliverables,” “impact metrics,” “alignment with EU digital policy.” Wrap your radical #4opens core in a frame they can recognise: resilience, digital sovereignty, anti-disinformation, democratic participation. That’s harder for them to ignore and strengthens the “native” path.
Expose the bias. Not in a bitter way, but in a constructive one: point out the repeated rejection of grassroots-native projects while funding flows to #geekproblem/NGOs. This pressure helps them re-balance (and others will maybe notice).
If you want to help, share the 3 projects ( #MakingHistory, #IndymediaBack, #OGB) in #Fediverse channels. Frame this positively: “If we want a living #openweb, we need to fund and support native projects, not just corporate/NGO clones.” make it harder for them to keep sidelining.
We were turned down repeatedly for all 3 projects by #Nlnet#NGI, do you think it's worth applying agen, if we do how can we shift this #blocking? Supporting Native Grassroots Projects in the Fediverse https://hamishcampbell.com/supporting-native-grassroots-projects-in-the-fediverse/
Hooray! It is now official: We have been granted funding by NLnet to support the realisation the vision we outlined in our last post.
Events are at the heart of social life and deserve to be treated accordingly in the Fediverse. […]
In addition, we will also investigate the Fediverse Auxiliary Service Provider Specifications (FASPs) for discoverability and filtering of public events.
I wonder if this is now better or worst? The problem we face with funding – #nlnethttps://hamishcampbell.com/the-problem-we-face-with-funding/
I wonder if this is now better or worst? The problem we face with funding – #nlnethttps://hamishcampbell.com/the-problem-we-face-with-funding/
The #Forgejo monthly report was published ✨
Forgejo v12.0 branch was cut on 25 June, for a planned release on 17 July. Forgejo v11.0.2 was released on 18 June, addressing several bugs. Forgejo Runner v6.4.0 introduced offline caching support.
The minimum required Git version has been bumped and the search has been improved.
There is strong enthusiasm for translating Forgejo.
User following with #ActivityPub has progressed and a new #NLnet grant has been accepted.
The #Forgejo monthly report was published ✨
Forgejo v12.0 branch was cut on 25 June, for a planned release on 17 July. Forgejo v11.0.2 was released on 18 June, addressing several bugs. Forgejo Runner v6.4.0 introduced offline caching support.
The minimum required Git version has been bumped and the search has been improved.
There is strong enthusiasm for translating Forgejo.
User following with #ActivityPub has progressed and a new #NLnet grant has been accepted.
There’s an old rot in the heart of European tech policy – and it’s not just from the corporate lobbies. Composting the EU Tech Mess: From #NLnet to #Eurostackhttps://hamishcampbell.com/composting-the-eu-tech-mess-from-nlnet-to-eurostack/
There’s an old rot in the heart of European tech policy – and it’s not just from the corporate lobbies. Composting the EU Tech Mess: From #NLnet to #Eurostackhttps://hamishcampbell.com/composting-the-eu-tech-mess-from-nlnet-to-eurostack/
Hooray! It is now official: We have been granted funding by NLnet to support the realisation the vision we outlined in our last post.
Events are at the heart of social life and deserve to be treated accordingly in the Fediverse. […]
In addition, we will also investigate the Fediverse Auxiliary Service Provider Specifications (FASPs) for discoverability and filtering of public events.
A space for Bonfire maintainers and contributors to communicate
