sonalder

joined 4 years ago
[–] sonalder@lemmy.ml 2 points 2 days ago

Makes sense as in the capitalist vision of the world, women become ressources for producing workforce(men).

[–] sonalder@lemmy.ml 2 points 2 days ago

The sad truth is that Apple Silicon, especially Ultra chip are champion of local inference. Using oMLX instead of ollama take the most out of it.

In my region older Mac Studio are hard to find but maybe you will be more lucky than I am.

[–] sonalder@lemmy.ml 1 points 3 days ago

No, there are libraries to talk to the Meshtastic firmware

Great!

I don't think so. I think only Meshtastic uses portnums.

That's what I meant when I said "adapted"

[–] sonalder@lemmy.ml 2 points 4 days ago

It's in the name :D Micro Apps.

But yes Reticulum might be more suitable for many things but the barrier of entry is bigger (as of today) as Meshtastic which is almost getting mainstream. I have people I would never thought would be into these that heard of it and are somewhat interested in it.

[–] sonalder@lemmy.ml 0 points 4 days ago (2 children)

Yes the BitMesh app uses the Meshtastic Android app to broadcast to the LoRa mesh network.

Would talking directly to the device would require some custom firmware?

Reticulum is very interesting I will check the portnum you mentionned. Also if I did understood correctly I think that MAM, despite having Meshtastic in its name, could easily be adapted to any other LoRa based mesh network.

 

So I was digging around AlternativeTo.net and Meshtastic-related Android apps called Bitmesh came across. And buried in the doc in the GitLab repo is a protocol spec the author seems to have wroten called MAM: Micro Apps over Meshtastic. It's not really talked about anywhere I could find, which seems like a shame as I think it deserves way more attention than it's getting.

The core idea is simple but kind of elegant: right now if you want to build a third-party app on top of Meshtastic, you're basically stuck fighting over the radio with everyone else, with no clean way to share the channel between multiple independent apps. MAM is a small framing layer that sits on top of Meshtastic's PRIVATE_APP portnum and lets completely different apps coexist on the same channel without stepping on each other.

Concretely, here's what it does:

  • A 4-byte header + MessagePack payload per packet
  • App multiplexing via a 16-bit message ID (so multiple apps share one channel cleanly)
  • Reassembly for messages that span multiple packets (up to 16 chunks × 236 bytes = ~3.7 KB)
  • A defined handshake with the local node over BLE (ToRadio / FromRadio)
  • Honest, explicit security posture: the PSK is public, it's a namespace token, not actual security, that's each app's problem to solve

What struck me reading it is how general-purpose it feels. The spec is very deliberate about what it does and doesn't cover things like reliability, encryption, and app-level schemas are explicitly left to each app to figure out. It's just the transport plumbing, nothing more. There's even a registered vs experimental app ID split built in, which reads like the author was thinking about other people building on top of it, not just their own use case.

I'll be honest, some of the finer technical details go a bit over my head. But the overall design feels solid and the spec is short enough to read in one sitting. I'd be curious what people who've actually built things on Meshtastic think. Does this solve a real problem? Is there something else already doing this that I missed? Does the spec have obvious holes? Is anyone aware of other apps implementing it?

[–] sonalder@lemmy.ml 0 points 3 weeks ago (1 children)

They try to be competitive on pricing while being more fair on the whole process chain. If they didn't cheap out on hardware by using recent SoC and latest and greatest component, the FP would be probably more than twice the price.

[–] sonalder@lemmy.ml 1 points 1 month ago
[–] sonalder@lemmy.ml 14 points 9 months ago (1 children)

As there is (prove me if I'm wrong) no current way to dump and decrypt Switch2 games this is a highly probable hoax. I wouldn't consider this to be true and be extermely careful.

[–] sonalder@lemmy.ml 1 points 9 months ago

I would suggest you to choose a lightweight DE, in simpler word everything but GNOME. On my machine GNOME was eating ressources resulting in less FPS around roughly 10%-20% performance loss. But from a distro to another one I haven't seen major gap in my benchmarks. Desktop Envrionement had much more impact

[–] sonalder@lemmy.ml 3 points 9 months ago (1 children)

Nobara but considering other option such as Bazzite and GLFOS.

[–] sonalder@lemmy.ml 3 points 9 months ago (1 children)

Nostr and Fediverse are not incompatible, one exemple is what soapbox are doing.

  • this is a lemmy community about F-Droid
[–] sonalder@lemmy.ml 1 points 10 months ago

These are minimalist dumphone-like launchers

 

Lemmy devs asking for money and added a crypto option on https://join-lemmy.org/donate with BTC, ETH and XMR !

Nice.

 

La surveillance des télécommunications ne peut fonctionner sans la collaboration des entreprises de la branche. La loi sur la surveillance de la correspondance par poste et télécommunication (LSCPT) prévoit différentes obligations selon le type de services que les entreprises proposent et elle classe les personnes obligées de collaborer dans différentes catégories. La compétence d'imposer des obligations supplémentaires ou d'accorder des dispenses pour certaines d'entre elles revient au Conseil fédéral, qui fixe les critères à ces fins.

L'ordonnance sur la surveillance de la correspondance par poste et télécommunication (OSCPT) classe les fournisseurs de services de télécommunication (FST) dans deux sous-catégories : les FST ayant des obligations complètes et les FST ayant des obligations restreintes. Les fournisseurs de services de communication dérivés (FSCD), quant à eux, sont désormais rangés dans trois sous-catégories, selon le niveau de leurs obligations, qui peuvent être minimales, restreintes ou complètes. Ces distinctions doivent permettre une gradation plus équilibrée des obligations et un rapprochement entre les FST et les FSCD de taille et d'importance économique comparables. Un FSCD ayant des obligations complètes doit réaliser au moins cent millions de francs de chiffre d'affaires et/ou avoir plus d'un million d'utilisateurs. Nouveaux types de renseignements - suppression des chiffrements

Trois types de renseignements et deux types de surveillance sont par ailleurs créés à la faveur de cette révision. L'objectif est d'une part de standardiser certains renseignements et surveillances rétroactives servant à l'identification d'utilisateurs et qui étaient jusqu'ici traités comme des cas spéciaux et, d'autre part, de créer la possibilité de ne surveiller qu'une partie des données de contenus lors de surveillances en temps réel.

Un nouveau type de renseignements permet la constitution d'intersections des résultats de l'identification des utilisateurs de deux connexions internet ou davantage. Les autres concernent la livraison d'indications sur le dernier accès à un service de courrier électronique ou à un autre service de télécommunication ou service de communication dérivé.

Un nouveau type de surveillance a pour objet la surveillance en temps réel de données secondaires et du contenu tronqué de services d'accès au réseau, tandis qu'un autre est prévu pour la surveillance rétroactive aux fins de l'identification des utilisateurs de connexions à l'internet.

L'OSCPT précise par ailleurs l'obligation légale pour les fournisseurs de supprimer les chiffrements qu'ils ont opérés. Cette obligation concerne tous les fournisseurs (FST et FSCD) ayant des obligations restreintes ou complètes. Les chiffrements de bout en bout - par exemple dans les services de messagerie - ne sont explicitement pas concernés.

Certaines dispositions de l'ordonnance du DFJP sur la mise en œuvre de la surveillance de la correspondance par poste et télécommunication (OME-SCPT) doivent également être modifiées. Les délais de traitement doivent ainsi être adaptés pour prendre en compte les nouveaux types de renseignements dans l'OSCPT. Pour le reste, les modifications sont d'ordre rédactionnel.

La consultation dure jusqu'au 6 mai 2025.

 

I tried to make a list on AlternativeTo that has all the apps you ever needs. I tried to avoid services and stick with apps, however there is a few services like Cloud-sync Notes, Password manager, E-mail aliases and a few others. I tried to stick with Free (as in free beer) Apps and when there is great options Free (as in Freedom) and open source.

Do you have any recommandations so I can improve that list without bloating it too much ?

 

I don't use Google account on most of my devices. I have an older phone on LineageOS 22.1 that I use mainly to test apps. It has GApps installed but I never sign in. I have faced a couple apps that on startup are launching the PlayStore app and ask me to sign in, I guess for "security". Is there a way to bypass that ? I don't want to link my Google profile and would love to use this app offline like I should.

Is this something that could be done with LuckyPatcher ? Is there easier methods ?

 

I have been using ChimeraOS on my living room PC and it has worked well most of the time without issues. Recently I had audio stuttering on a new game and fixed it by using an older Proton build. But then I started a game that I have played many hours on this machine without any issue and suddenly had audio stuttering again on this title that previously had no audio issue with. Then I realized it is a problem with most of my library... This is really annoying for some title.

Anyone experienced something similar recently ? I have updated ChimeraOS twice since and updated the Proton Experimental build etc... Don't know if it is related to Proton, to a driver, to Chimera... How could I debug this ?

 

Pretty much the title. I installed my GOG games through Lutris and wanted to rapidly import them to Steam. Same for emulated ROM. Do you have advices ?

 

Would like to see open source client such as Infinity, Stealth, RedReader, etc... going to lemmy.

The best case scenario would be all reddit client including Apollo, Boost, etc... supporting the transition to lemmy but this is quite unlikely unfortunately...

 

SimpleMobileTools are making simple yet great open source android apps. No ads, no trackers, cheap price or even free. I personnaly love Simple Gallery Pro and have a lot of respect for the devs, I would like to donate since they accept cryptos... unfortunately only BTC, ETH and LTC. Let them heard of the benefits of Monero so I (and maybe you) could donate to them for their work !

 

I recently discover NowPayments which looks like a cool services but does not suit well with a Monero mindset. I understand that it will have some compromises for using a service like that no matter how serious the ones running it are. I was just wondering if their was a simple way for a commerce to be paid in euro/dollar or whatever currency is prefered and that the customer uses XMR without comprimising any information on his/her side.

 

Often people tend to say due to the lack of funding open source apps have bad UI and also sometimes terrible UX. While it’s not entierly false I’ve found myself some beautifuly designed apps and wanted to share them here.

view more: next ›