Mathstodon

2 posts2 participants0 posts today

KMJ 🇦🇹It feels good in the curent situation to be fully free of any proprietary solution.<a href="https://mastodon.ctseuro.com/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://mastodon.ctseuro.com/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> <a href="https://mastodon.ctseuro.com/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeBSD</a> on all systems only, own <a href="https://mastodon.ctseuro.com/tags/public" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#public</a> <a href="https://mastodon.ctseuro.com/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> servers on own systems including management. <a href="https://mastodon.ctseuro.com/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mastodon</a>, <a href="https://mastodon.ctseuro.com/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matrix</a> , <a href="https://mastodon.ctseuro.com/tags/Bridges" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bridges</a> , <a href="https://mastodon.ctseuro.com/tags/Email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Email</a> , <a href="https://mastodon.ctseuro.com/tags/SOGo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SOGo</a> <a href="https://mastodon.ctseuro.com/tags/Nextcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nextcloud</a> <a href="https://mastodon.ctseuro.com/tags/Owncloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Owncloud</a> <a href="https://mastodon.ctseuro.com/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> <a href="https://mastodon.ctseuro.com/tags/ntfy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntfy</a> <a href="https://mastodon.ctseuro.com/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HomeAssistant</a> <a href="https://mastodon.ctseuro.com/tags/WebSites" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebSites</a> mostly done with <a href="https://mastodon.ctseuro.com/tags/Hugo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hugo</a>, and far more all self hosted on own systems in the basement or in our housing rack.Mobiles <a href="https://mastodon.ctseuro.com/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GrapheneOS</a> and <a href="https://mastodon.ctseuro.com/tags/LineageOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LineageOS</a> Whatever <a href="https://mastodon.ctseuro.com/tags/Trump" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Trump</a> <a href="https://mastodon.ctseuro.com/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> aso does i dont care

SES<a href="https://fosstodon.org/@davx5app" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@davx5app</a> Really wonderful approach which I just learned about today. I'd really like to use <a href="https://social.tchncs.de/tags/Davx5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Davx5</a> <a href="https://social.tchncs.de/tags/unifiedpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unifiedpush</a> with my <a href="https://social.tchncs.de/tags/nextcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nextcloud</a> instance and <a href="https://social.tchncs.de/tags/nextpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nextpush</a>. However, the <a href="https://social.tchncs.de/tags/davpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#davpush</a> app seems not to be compatible with NC v31 yet. And in the bug tracker I read about possible incompabilities with upcoming v32. So will this likely continue to be an issue that I won't be able to use it on the newest NC version for a while? Or are you guys maybe even working on an integrated solution?

Sandro SantilliIs it expected for <a href="https://floss.social/tags/Tusky" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tusky</a> to use more than a single <a href="https://floss.social/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> channel ? For comparison, <a href="https://floss.social/tags/FluffyChat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FluffyChat</a> uses a single one, despite managing multiple accounts..<a href="https://chaos.social/@ConnyDuck" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ConnyDuck</a>

ChristophMy second <a href="https://social.shtrophic.net?t=openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> <a href="https://social.shtrophic.net?t=port" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#port</a> that got merged into the <a href="https://social.shtrophic.net?t=ports" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ports</a> tree: MollySocket [1] Mollysocket is for every <a href="https://social.shtrophic.net?t=signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Signal</a> user that wants to ditch Google-dependent notifications. Together with <a href="https://social.shtrophic.net?t=molly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Molly</a> [2] you can be sure that notifications will only be routed over systems that you choose, using <a href="https://social.shtrophic.net?t=unifiedpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a>. This OpenBSD port in particular comes with a useful README that should help you to get started quickly. Let's hope that it makes it into 7.7-release :) See: <a href="https://cvsweb.openbsd.org/ports/net/mollysocket/" rel="nofollow noopener noreferrer" target="_blank">https://cvsweb.openbsd.org/ports/net/mollysocket/</a> [1] <a href="https://github.com/mollyim/mollysocket" rel="nofollow noopener noreferrer" target="_blank">https://github.com/mollyim/mollysocket</a> [2] <a href="https://molly.im/" rel="nofollow noopener noreferrer" target="_blank">https://molly.im/</a>

F-Droid<a href="https://fe.disroot.org/users/bshankar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bshankar</a> Depends on the actual NEED. There are 3-4 common paths that we see: 1. Remove the NEED, maybe it wasn't that important anyway 2. Replace Google Push with <a href="https://floss.social/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> 3. Replace Play Services with <a href="https://floss.social/tags/microG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#microG</a> 4. Replace the camera/QR lib with a FOSS one.

Andromxda 🇺🇦🇵🇸🇹🇼<a href="https://mammut.gogreenit.net/@chewie" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@chewie</a> By using Signal-FOSS or Molly-FOSS you just force the Signal app to use its WebSockets-based notification fallback mechanism. But if you have Play services installed and have granted them network permissions, you might as well just use FCM for notifications. It saves battery life compared to each app maintaining its own background network connection.If you're using <a href="https://fosstodon.org/@mollyim" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mollyim</a> you also have a third option for receiving notifications: <a href="https://fosstodon.org/@unifiedpush" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@unifiedpush</a> But since Signal doesn't support it natively, you need a <a href="https://github.com/mollyim/mollysocket" rel="nofollow noopener noreferrer" target="_blank">mollysocket</a> server that receives the Signal notifications and translates them into UnifiedPush format. The mollysocket server is connected to your Signal account as a linked device, but it does not have your decryption keys. There are public instances of mollysocket like <code>mollysocket.adminforge.de</code>The easiest and best way to get started with <a href="https://unifiedpush.org/" rel="nofollow noopener noreferrer" target="_blank">UnifiedPush</a> (IMO) is the recently released <a href="https://codeberg.org/Sunup/android" rel="nofollow noopener noreferrer" target="_blank">Sunup</a> distributor app.<a href="https://infosec.exchange/tags/signal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#signal</a> <a href="https://infosec.exchange/tags/signalapp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#signalapp</a> <a href="https://infosec.exchange/tags/molly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#molly</a> <a href="https://infosec.exchange/tags/mollyim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mollyim</a> <a href="https://infosec.exchange/tags/unifiedpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unifiedpush</a> <a href="https://infosec.exchange/tags/mollysocket" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mollysocket</a>

ghose ⁂ 👣Hi <a href="https://gts.superseriousbusiness.org/@gotosocial" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gotosocial</a>FYI I've tested my <a href="https://gts.xmgz.eu/tags/nextpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nextpush</a> server with <a href="https://mastodon.social/@Tusky" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Tusky</a> and <a href="https://gts.xmgz.eu/tags/gotosocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gotosocial</a> account for <a href="https://gts.xmgz.eu/tags/unifiedpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unifiedpush</a> notifications and it works as expected :festasloth:I report this because release notes from «Scroingly Sloth» read<blockquote>(And if you're using Tusky, make sure you've got ntfy installed).</blockquote>«or nextpush conected to a nextcloud server with a running unifiedpush app» (or something similar)<a href="https://gts.xmgz.eu/tags/nextcloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nextcloud</a>

Bhavani Shankar 💭TIL <a class="hashtag" href="https://fe.disroot.org/tag/conversations" rel="nofollow noopener noreferrer" target="_blank">#conversations</a> is not just an end to encrypted, federated messenger, it can also send notifications to your apps through <a class="hashtag" href="https://fe.disroot.org/tag/unifiedpush" rel="nofollow noopener noreferrer" target="_blank">#unifiedpush</a> <a class="hashtag" href="https://fe.disroot.org/tag/xmpp" rel="nofollow noopener noreferrer" target="_blank">#xmpp</a> <a class="hashtag" href="https://fe.disroot.org/tag/android" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a class="hashtag" href="https://fe.disroot.org/tag/e2ee" rel="nofollow noopener noreferrer" target="_blank">#e2ee</a> <a class="hashtag" href="https://fe.disroot.org/tag/decentralised" rel="nofollow noopener noreferrer" target="_blank">#decentralised</a>

Radasbona<a href="https://chaos.social/@delta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@delta</a> to bring push notification also to the fdroid installations <a href="https://social.vivaldi.net/tags/chatmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chatmail</a> server should support <a href="https://social.vivaldi.net/tags/unifiedpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unifiedpush</a>.

PureTryOut<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> <a href="https://social.treehouse.systems/@cas" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cas</a> <a href="https://207.social/@jawsh" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jawsh</a> Then again push notifications (the ones you receive when the app is not running) should be handled through a dedicated daemon, not the app itself. <a href="https://mastodon.fam-ribbers.com/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> for example.

Tobias SchmidlIch hab da einen lokalen Server, der nicht wirklich gut Mails verschicken kann. Trotzdem möchte ich benachrichtigt werden, wenn ein `unattended-upgrade`schiefgeht. Die Lösung: nen Webhook auf das <a href="https://augsburg.social/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> von meiner <a href="https://augsburg.social/tags/NextCloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NextCloud</a>:``` watchmedo shell-command -W --command 'curl -d "$(echo p | mail)" <a href="https://cloud.schmidl.dev/index.php/apps/uppush/push/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://cloud.schmidl.dev/index.php/apps/uppush/push/</a><langes Token aus NextPush>' /var/mail/schtobia ```<a href="https://augsburg.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a>

Blort™ 🐀Ⓥ🥋☣️<a href="https://mastodon.matrix.org/@element" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@element</a> Notification of calls on Android phones using <a href="https://social.tchncs.de/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> , seem to have been completely broken for many (all?) people since the move from version 1.5.28 to 1.5.30.A bug was filed over a year ago. A number of people there say they can't get calls at all and even offer money for bugfix dev work, but so far no one from the team has even commented on it.<a href="https://github.com/element-hq/element-android/issues/8761" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/element-hq/element-android/issues/8761</a>What info would help or can you recommend a dev to pay to work on this?<a href="https://social.tchncs.de/tags/Matrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matrix</a> <a href="https://social.tchncs.de/tags/Element" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Element</a>

Łukasz HorodeckiHej fedisie z Androidem. Których UnifiedPush distributors używacie? I jak właściwie się po naszemu mówi na te zunifikowane dystrybutory popchnięć? xD<a href="https://pol.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://pol.social/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> <a href="https://pol.social/tags/powiadomienia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#powiadomienia</a> <a href="https://pol.social/tags/DrogieFedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DrogieFedi</a> <a href="https://pol.social/tags/DrogiBlipie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DrogiBlipie</a>

Gytis RepečkaIt would be great if <a href="https://fosstodon.org/@briar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@briar</a> could do push notifications via UnifiedPush instead of sitting in the background :ablobcatcoffee:Quite cool seeing more apps in ntfy :ablobcatattention:<a href="https://social.gyt.is/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a href="https://social.gyt.is/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://social.gyt.is/tags/push" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#push</a> <a href="https://social.gyt.is/tags/unifiedpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unifiedpush</a>

Hraban (fiëé visuëlle)<a href="https://fosstodon.org/@mollyim" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mollyim</a> I was using <a href="https://literatur.social/tags/Molly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Molly</a> FOSS UP with <a href="https://literatur.social/tags/NextPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NextPush</a>. Current Molly FOSS insists to scan a QR code for <a href="https://literatur.social/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> setup, but NextPush doesn’t provide one. Do I really need MollySocket? The old version worked well without another service.

UnifiedPush**Push notifications for decentralized services**How mobile push notifications currently bring centralization to decentralized services, and how we can avoid it, even for mainstream configurations.<a href="https://unifiedpush.org/news/20250131_push_for_decentralized/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://unifiedpush.org/news/20250131_push_for_decentralized/</a><a href="https://fosstodon.org/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> <a href="https://fosstodon.org/tags/Webpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Webpush</a> <a href="https://fosstodon.org/tags/decentralization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decentralization</a>

distributed<a href="https://hachyderm.io/@Unlogic" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Unlogic</a> yep, love the customization and side loading of apps via different marketplaces like <a href="https://mastodon.sdf.org/tags/accrescent" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#accrescent</a> and <a href="https://mastodon.sdf.org/tags/fdroid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fdroid</a>. Just set up <a href="https://mastodon.sdf.org/tags/unifiedpush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unifiedpush</a> over the past few days for <a href="https://mastodon.sdf.org/tags/moshtidon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moshtidon</a> and a handful of my other <a href="https://mastodon.sdf.org/tags/foss" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#foss</a> apps. Gives me a lot more peace of mind than using proprietary black box systems. Have fun tinkering!

S1mThe last version of gCompat-Up, the <a href="https://infosec.exchange/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> distributor that uses Google services (mostly useful to do some tests) is now fully FOSS ✌

DanI'm working on being able to set up <a href="https://mastodon.social/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a> on <a href="https://floss.social/@sandstorm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@sandstorm</a> with the <a href="https://mastodon.social/tags/ntfy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ntfy</a> app (Note that this is *experimental*, not production ready yet):<a href="https://apps.sandstorm.io/app/pxm3ugzn7sfhtw4kz9ktdfkyphdq0qa1y2n1g0yfnzkn0mqcszhh?experimental=true" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://apps.sandstorm.io/app/pxm3ugzn7sfhtw4kz9ktdfkyphdq0qa1y2n1g0yfnzkn0mqcszhh?experimental=true</a>Sandstorm makes it really easy to install web apps, but it adds some challenges and limitations. I'm also learning about ntfy as I go. But, in principle it works; I am successfully using it right now for Tusky.I'd love to get feedback from anyone familiar with ntfy who is interested in seeing it on a new platform.

distributed<a href="https://mastodon.social/@DrPen" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@DrPen</a> have you tried with <a href="https://mastodon.sdf.org/tags/UnifiedPush" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnifiedPush</a>?

Recent searches

Search options

Administered by:

Server stats:

#UnifiedPush