• 4 Posts
  • 1.03K Comments
Joined 4 years ago
cake
Cake day: June 28th, 2020

help-circle





  • Motal is participating in GSoC this year to get some new features too.

    But this is a wider issue that developing free software for Apple products is way too expensive (time & money) to be feasible while also going against the general free software ethos. It should be no surprise the walled garden of a proprietary OS that charges you to publish to their store has a severe lack of free or otherwise ethical software (which is important for security for something as important as a messaging app full of private data).


  • XMPP clients are fine albeit it all, as many as they are, slightly different as is the nature of the protocol. This just means there is value in contributing to existing clients, creating new clients, or embracing progressive enhancement (which most do for example with emoji reactions just being a quoted text reply & so on) & complete feature parity is a fool’s errand if you want an exensible protocol with diversity & experimentation in the community. With the broad exception of the Conversations Compliance, there isn’t a flagship client & instead the best ideas come to the most used or most innovative clients. I use Cheogram, Profanity, Gajim, Dino, Movim at different times (& would love to create my own). The protocol is stable, healthy, & ready for proposals for improvement.

    If I compare this to the more-expensive-by-all-metrics-to-run Matrix, if it ain’t Element, you gotta problem since a vast majority of users are on it & using all of its features & no other client has anything near parity but are expected to have parity instead of allowing things to sometimes be gracefully missed or shown in a less than ideal manner as acceptable. This hurts experimentation. Good luck trying anything similar to GDPR when all nodes are design & required to duplicate all messages & attachments for all users to every server anyone in it comes from.

    The only real gotcha is the same gotcha as Matrix when using multiple clients with double-ratchet encryption (ala Signal) is that clients will expire keys that haven’t been seen in a while & is hard to get both devices retrusting one another. Turning it off & on again rarely works & requires fiddling on both ends sometimes. I really should just use PGP for encryption more often…


  • toastal@lemmy.mltoMemes@lemmy.mlI hate the IRS 😡😡😡
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    12 hours ago

    Baby. Bathwater.

    Not all of the cryptocurrency behave as a Ponzi scheme even if many do. It also happens to be the most convenient way to transfer money between myself & the foreign friends I have—especially with Monero & Zcash hiding the transaction like cash would. I mostly use cash daily but if I have to do it digitally, I would rather it not be logged thru the government, some US-based tech firm, & all their third-party advertizing affiliates as is the case with credit cards and other mobile apps.


  • I got locked out my seldom-used PayPal account a few years ago. They decided to arbitrarily remove Google Voice as an SMS 2FA option (I want to say TOTP wasn’t supported when I signed up). I went to find out who to contact about authentication issues, but support, chicken-&-egg-style, requires authentication—even for auth issues—with no support@ email. I used the worst-case-scenario support option of Twitter but that support team banned me for messaging them about auth. Since I couldn’t get back into my account + the sheer incompetence of the support system, I never used & refused to use PayPal ever since. I am happy that my country prefers cash transactions & I can’t believe in the past I used a major bank credit card + major corp digital payment option for almost all purchases. Long live cash (& Monero/Zcash).







  • Git is distributed but still centralized. D in DVCS is distributed. Downvoters likely have never used a non-Git VCS, let alone a non-snapshot-based VCS. But fanboys will fanboy.

    Pijul & Darcs are based on Patch Theory which make the conflicts of different patch order a non-issue so long as the apply cleanly (such as working on different ports of the code base). Patch A then patch B ≡ patch B then patch A; this will be a needless merge conflict in Git since the order matters. (& no, Jujutsu isn’t the solution still shackled to the limitations of Git as a back-end while claiming to do what Pijul does—but doesn’t).