Punch nazis, trebuchet TERFs.

I am building Voyager, a client for lemmy!

I mainly post under @aeharding@vger.social now.

  • 1 Post
  • 56 Comments
Joined 1 year ago
Cake day: June 13th, 2023
  • aeharding@lemmy.worldtoTechnology@lemmy.world•In-app browsers still a privacy, security, and choice issueEnglish
    5·
    3 months ago

    It’s crazy that the in-app browser isn’t an OS-level overlay that the app can’t influence or look at what the user is doing in it.

    Android and iOS both have apis for in app browsers that are secure by design. Voyager for Lemmy uses this. Mastodon uses this. Last I checked even Twitter used this. However Facebook does not.

    these platforms also offer lower level APIs to build custom interface which are more powerful and flexible (but can be abused). This isn’t necessarily a problem. Custom browser apps need that functionality, and apps sometimes display their own content with web views.

    The problem is that app stores allow slapping a skin on this more powerful API and treating it like an in app browser to connect to arbitrary sites. Dumb imo. If you offer an in app browser, it should be required to use the platforms secure in app browser API.

    More powerful APIs should only be available to browser apps and displaying your own content in a web view.

  • aeharding@lemmy.worldtoFediverse@lemmy.world•The perfect Lemmy app?English
    4·
    4 months ago

    Yeah, this. Remark, the markdown library Voyager uses, is very powerful but also extremely complex (it has to be, to deal with Markdown edge cases).

    I made a bit of progress last week on a custom plugin but it’s a lot of work. There’s like 4 layers of parsing required.

    I wish Lemmy used GFM spoilers, which just uses normal details and summary html tags. But alas.

    It’s really annoying there’s no standard markdown syntax in common mark.

  • aeharding@lemmy.worldtoTechnology@lemmy.world•Bluesky federation goes liveEnglish
    83·
    4 months ago

    We had a thing a while back on Lemmy where a bunch of semi-popular instances (including lemmy.world, though they seem to have rolled that back) all defederated from instances that mentioned piracy. I don’t have a problem with piracy. I want to talk about piracy.

    To me, that is a feature, too. The admin team made a decision, and the community engaged, the topic was discussed, and the decision was changed. To me that’s a very healthy process. The only thing I would’ve changed would be LW engaging the community before defederating, but they were understandably worried about legal implications.

    Even if LW didn’t reverse this decision, you can change instances. Lemmy 0.19 makes this easier with import/export, but I would argue it should be even easier. Ultimately though this is a lemmy implementation detail, and not an activitypub problem.