The latest #CryptPad release is now available for everyone.
Uncategorized
7
Posts
4
Posters
13
Views
-
The latest #CryptPad release is now available for everyone. đ„ł Featuring a lot of fixes, new icons and refreshed loading screens.
https://github.com/cryptpad/cryptpad/releases/tag/2025.9.0 -
The latest #CryptPad release is now available for everyone. đ„ł Featuring a lot of fixes, new icons and refreshed loading screens.
https://github.com/cryptpad/cryptpad/releases/tag/2025.9.0@cryptgoat Has anyone managed to use the new version of #CryptPad with #Ironfox?
-
undefined oblomov@sociale.network shared this topic on
-
@cryptgoat Has anyone managed to use the new version of #CryptPad with #Ironfox?
@switchingsoftware Seems broken for me too â not sure if it is related to the #IronFox 144.x releases or the new #CryptPad release.
@celenity @CryptPad You might want to take a look at this. Only getting script errors when loading/creating documents or timeouts.
-
@switchingsoftware Seems broken for me too â not sure if it is related to the #IronFox 144.x releases or the new #CryptPad release.
@celenity @CryptPad You might want to take a look at this. Only getting script errors when loading/creating documents or timeouts.
@cryptgoat hello!
As replied on our Matrix space where you asked this as well:
We do not test CryptPad against IronFox, nor do anything specific in our source code to limit or block its usage. If it isn't working as expected we would suggest reporting it to its developers.
1/2
-
@cryptgoat hello!
As replied on our Matrix space where you asked this as well:
We do not test CryptPad against IronFox, nor do anything specific in our source code to limit or block its usage. If it isn't working as expected we would suggest reporting it to its developers.
1/2
@cryptgoat that being said it's not uncommon that third-party web browsers, especially the ones with "security" customizations ends up breaking CryptPad.
We leverage proven web standards to build CryptPad. Many of them (web workers, shared workers, local storage, content security policies, iframes...) are required to make it work as intended.
2/2
-
@cryptgoat that being said it's not uncommon that third-party web browsers, especially the ones with "security" customizations ends up breaking CryptPad.
We leverage proven web standards to build CryptPad. Many of them (web workers, shared workers, local storage, content security policies, iframes...) are required to make it work as intended.
2/2
@CryptPad @cryptgoat @switchingsoftware unclear what you mean by âthird-partyâ web browser here - wouldnât every web browser not operated by you be considered âthird-partyâ?
also not sure why the âsecurityâ in quotes - we make a significant effort to meaningfully improve privacy and security for users, and i think weâre effective at doing that. our changes are carefully considered, and we do also go to a great extent to balance privacy and security with compatibility. in general, we go out of our way to fix issues with websites - i think we probably do more in that regard than most other browsers out there with similar goals tbh.
-
@CryptPad @cryptgoat @switchingsoftware unclear what you mean by âthird-partyâ web browser here - wouldnât every web browser not operated by you be considered âthird-partyâ?
also not sure why the âsecurityâ in quotes - we make a significant effort to meaningfully improve privacy and security for users, and i think weâre effective at doing that. our changes are carefully considered, and we do also go to a great extent to balance privacy and security with compatibility. in general, we go out of our way to fix issues with websites - i think we probably do more in that regard than most other browsers out there with similar goals tbh.
@celenity sorry for the confusion, by "third-party" we mean the ones we aren't able to test against CryptPad. We maintain a "Common issues" section in our documentation FAQ due to how often our users face issues with web browser customizations: https://docs.cryptpad.org/en/FAQ.html#common-issues
1/2
-
undefined filobus@sociale.network shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@Gina Theoretically, AI may be able to better identify women's health issues than some rando doctor, but as a Americanâą the whole idea of giving all my medical information to a company that's more than likely to turn around and sell it to the highest bidder creeps me the hell out. Especially since those companies could very well be health insurance companies that could decide to deny me coverage based on conditions I may or may not even have. And that's assuming the "AI" is not some random LLM.
-
@mike "OpenAI's new 'dedicated experience' that taps into your medical records..." What could go wrong đ
On the other hand, as a womanâą I'm actually kind of excited for the advanced pattern recognition that AI could bring. It might help with better identifying women's health issues.
-
@eriol @informapirata Il problema di personaggi famosi e politici Ăš proprio questo: influenzano, e hanno i soldi per farlo.
Poi nel caso specifico delle persone trans, la stessa scienza ha conoscenze relativamente recenti e neanche tutte. Le persone in questione sono poche, e allora ci si sente in diritto di sminuirle. O peggio.
-
@eniko so, disclaimer, I don't know if this is useful advice to your situation, but I found these to be handy on a project I worked on a while back:
https://lxjk.github.io/2018/03/25/Improve-Tile-based-Light-Culling-with-Spherical-sliced-Cone.html
https://wickedengine.net/2018/01/optimizing-tile-based-light-culling/
iirc we used a modified version of the spherical-sliced cone test combined with the tile depth bitmask strat for dealing with depth discontinuity. this was for culling reflection probes though, not objects.
-
Ooof. This sounds like the worst idea I've heard of for a while. I don't feel like this should need to be said, but don't trust an LLM for medical advice. Seriously.
-
@eniko
So the obvious performance hack is to set your game in the 1870's and the player character is a horse wearing blinders.
-
@eniko is there a reason why you're not using the typical hierarchical z buffer approach?
-
@evan a simple but effective way to avoid pile-ons is to not display the number of likes/dislikes. Whether I like something or not shouldnât depend on others views so showing that stat seems unnecessary.
Of course, thatâs predicated on the assumption that using the like button actually means I like it. I use it for a variety of reasons ranging from âI agreeâ to âI saw this response but have nothing to add.â
