Ricardo @rmdes@mstdn.social

Une enfance sous emprise, témoignage de moi-même et mon amie Sophie dans le #Podcast LouieMedia / Passages

Acast : https://play.acast.com/s/a7277f6f-bb0c-49df-ac44-80cf3167a59b/beb5a4da-fb85-4cf8-a12c-a6c49cc1c1d6

Spotify : https://open.spotify.com/episode/1AapoMDiApd4xNFxJiqVMM?si=1In1ppo4Tt2LYiCrV3VENg&nd=1

Mise à jour : affaire toujours en cours, appel en cassation en Belgique et nouvelle instruction en France.

To the Death!

#sectes #dérives #metoo #OKC #RobertSpatz

✨ Discover
✨ Drawer navigation

A few improvements to our #pixelfedApp before the upcoming beta release! 🚀

Truth Social costing $320k per month to host is wild, and hilarious. I’m curious to see the breakdown of how that’s possible.

We could eliminate most fediverse spam with sms registration at the expense of early adopters who disproportionately despise it.

Do we sacrifice growth for "UX" or take advantage of established anti-spam measures?

This is the million dollar question for every #activityPub project. What do you think? #fediverse #spam

How should I distinguish remote accounts from local in this context where we want to avoid using the full webfinger identifier?

I don't want users to be confused between local/remote accounts but I also don't want to have a domain prepended to every remote account.

Thoughts? #pixeldev

https://amplifyukraine.eu/%f0%9f%94%b5%f0%9f%9f%a1-severodonetsk-graves-of-civilians-just-in-the-yards-the-ruins-of-high-rise-buildings-and-deserted-streets-severodonetsk-stoprussia-%f0%9f%87%ba%f0%9f%87%a6/

One more thing...

I want to make the mobile app dynamic in the sense that instance admins can determine feature availability.

Examples:
- Local timeline
- Network timeline
- Stories
- Live streaming
- Hiding public like/share counts

This would empower instance admins, though at the expense of a unified experience. We can solve the unified experience issue by improving onboarding and explain why X feature is missing.

Thoughts? #pixelfed

I have been testing for the past few days three replacements for #Google's #Firebase notifications: #ntfy, #Gotify and #NextCloud's Unified Push project. A few observations after a bit of tinkering:

1. The idea behind #UnifiedPush is amazing. An open protocol to share push notifications over any asynchronous channel (websocket, Redis, MQTT etc.) is what open-source apps have needed for years. Sure, there will always be those who say "push notifications are a distraction, and I'm happy to ditch them". But individual choices/behaviors shouldn't shape the development of a technology - especially when people want a genuine open alternative to something that they like/need to use.

2. UnifiedPush support from individual apps is still scarce. So far I've only found the NextCloud app itself (which only supports UP-NextPush), #Fedilab and #Element. Support on #Tusky has allegedly been implemented in the latest release, but I haven't yet managed to make it work. Let's roll up our sleeves and make sure that more and more of the apps that we like support open notification services!

3. The notification providers' client apps themselves are still quite buggy, and documentation still very sparse. I have used UP-Example from F-Droid to test the UP services. Only ntfy managed to deliver notifications end-to-end to my devices. Gotify reported an "unknown error" without many details from the logs. UP-NextPush is still very unstable both on the client and server side and I couldn't manage to deliver any notifications.

4. The protocol (and the apps that implement it) needs to slowly be extended to cover as many as possible of the features that have been implemented in the past decade. Action buttons, icons from URLs, custom background images, updates to existing notifications etc.: a couple of these features have been (partly) implemented by 1-2 providers, but we need open standards (especially for action buttons and gestures) if we want to ensure inter-compatibility.

https://amplifyukraine.eu/at-least-two-arrivals-are-known-submit-news-%f0%9f%91%89-niko9_bot%f0%9f%91%89-subscribe-%d0%bd%d0%be%d0%b2%d0%be%d1%81%d1%82%d0%b8-%d0%bd%d0%b8%d0%ba%d0%be%d0%bb%d0%b0%d0%b5%d0%b2%d0%b0-%d1%83-5/

Our project is funded by people like you, and we need about $130 USD for an Apple developer account and Google Play Store account to publish the Live app (and eventually the main app!)

Will you help us reach that goal? The preferred donation method is our PayPal, https://paypal.me/dansup but you can also donate via https://www.patreon.com/dansup or https://liberapay.com/pixelfed

Boosts appreciated, and thank you for supporting us ❤️ #pixelfed #communityFunded

A sneak peak of the Pixelfed Live web player 👀

- Real time comments across web and mobile apps
- Delete messages or ban users from your streams
- Pin any chat message
- Real time viewer count
- Public live streams anyone can view (without the app or an account)

#pixelfed #pixelfedLive #liveStreaming

A nice side effect of Live is websocket support, now we can implement real time timelines and notifications in the web UI 😉 #pixeldev