The investigative newsroom I work for, @ProPublica, is raising money right now.
Uncategorized
2
Posts
2
Posters
19
Views
-
The investigative newsroom I work for, @ProPublica, is raising money right now. This is the last few days of our pledge drive.
We report on abuses of power in the public interest. We reported on who works for DOGE and revealed Clarence Thomas’s conflicts of interest.
It was the first outlet to win a Pulitzer for web-first journalism. And if you donate through this link, you'll let our team know the fediverse is an audience to pay attention to: https://give.propublica.org/give/346528/#!/donation/checkout?c_src=ben_mstdn #journalism #fediverse
-
undefined evan@cosocial.ca shared this topic on
-
The investigative newsroom I work for, @ProPublica, is raising money right now. This is the last few days of our pledge drive.
We report on abuses of power in the public interest. We reported on who works for DOGE and revealed Clarence Thomas’s conflicts of interest.
It was the first outlet to win a Pulitzer for web-first journalism. And if you donate through this link, you'll let our team know the fediverse is an audience to pay attention to: https://give.propublica.org/give/346528/#!/donation/checkout?c_src=ben_mstdn #journalism #fediverse
@ben @ProPublica thanks for all you do!
-
undefined oblomov@sociale.network shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Comunque oggi a pranzo c'era del guacamole.
-
-
-
@bart@floss.social Spot on. The vendor lock-in is exactly what's holding me back from moving to Codeberg. It's frustrating that standard security features like OIDC publishing are becoming a golden cage that keeps us tied to big platforms. I'd love to see npm support OIDC from Forgejo/Gitea, but it feels like we're still a long way from a truly forge-agnostic ecosystem. 2FA tokens for life, I guess? 🥲
-
@ChieseBrutte stavo per votare la seconda (astronave aliena camuffata da chiesa), ma poi ho visto la quarta che è davvero più brutta anche della Multipla (e dovrebbe avere diritto alla copertina del calendario, amen).
-
It looks like it is time once again to fast-forward through a full year of Hubzilla development!
Over the past year, we have delivered a lot of improvements and new features, including:
New Features
Introduced conversation containers Added on-demand loading of comments, replies and reactions to enhance performance Implemented threaded conversation view Enabled direct linking to calendar views via URL fragments Introduced custom site emojis Added support for Geo URIs Implemented FEP-e232 object links Implemented inbound RFC9421 HTTP signatures
Improvements
Added AVIF image support Reduced dependency on jQuery Extended automated test coverage Improved Diaspora profile import functionality Enhanced background fetching of replies collections Extended content filtering capabilities Improved notifications widget Numerous bug fixes and general stability improvements
Addons
Refactored the photocache addon Full rewrite of the flashcards addon Enhanced the superblock addon with admin-level site blocking capabilities
Did i forget something? Probably...
What a wild ride it has been! Now full steam ahead towards Hubzilla 11
-
@hongminhee It's just early days I think. Another limitation is that it is tied to GitHub/GitLab.
-
Is it just me, or is #npm's trusted publishing unnecessarily rigid? Only one workflow filename allowed per package. It's like they never imagined a project having multiple release branches or evolving CI structures. Moving from build.yaml to publish.yaml shouldn't be this annoying. 😩
