[–] 1 point 4 months ago

Idk maybe I’m wrong, but this feels like more of a hiring issue than AI. You should still be hiring good engineers, and you shouldn’t incentivize them to go so fast that they have to vibe code everything. Let good engineers use AI if they want, and not use it if they don’t want to. If their code is bad, it’s their fault, not the tools they are using.

  • source
  • [–] 3 points 7 months ago (1 child)

    Blorp dev here. I'm copying the thumbnail url into the post url, but perhaps that's incorrect. I'm open to suggestions. Again, not confident I'm handling this correctly, but one advantage of setting post.url is cross posts are compared via url, so setting that url would allow Lemmy to associate cross posts of the same image.

    On the rendering side, Blorp scans post.url and if it's an image (e.g. ends in .png), it renders it as an image post. But perhaps not all clients do that.

  • source
  • parent
  • context
  • submitted 11 months ago by [M] to c/blorp@lemmy.ml
     

    I think I’m going to migrate this community to Lemmy.world or Lemmy.zip. I love PieFed, but I’d rather wait until things are a little more stable before I consider PieFed.social.

    I think world and zip are both fantastic options. Lemm.ee leaves me a little worried that any instance can shut down at any point. I’d prefer to pick whatever instance is least likely to shut down. I do think Lemmy.ml is pretty safe from shutdown, since it’s run by Lemmy maintainers, but I’m worried I’m reducing my audience since many people block ml.

    Any thoughts?

    submitted 11 months ago* by [M] to c/blorp@lemmy.ml
     

    v1.9.13 fix PieFed

    PieFed was broken if you

    • Block a person
    • Block a community
    • Moderate a community

    That has all been fixes in v1.9.13

    Next up!

    Give those a try, and let me know if you like seeing early previews like that.

    I’m trying to formulate a long term plan

    • Lemmy V1 is going to ship later this year. I suspect a lot of clients that aren’t maintained are going to break. I would like to get Blorp to a place where I can be a home for all those new users.
    • Anyone here who’s first language isn’t English? Interested in Blorp being translated into your language?
    • I have no idea how to market this app. I’m estimating I may have 400ish users. I honestly have no idea. Could be much higher or much lower. My marketing mostly consists of me annoying people on Lemmy into using Blorp. At least that’s how I percieve it, and I cring a little at myself.
    • I have no idea how to build out a team, but if you have any skills that you feel could contriute to this project, please don’t be shy. I would like Blorp to be bigge than myself.
    submitted 11 months ago* (last edited 11 months ago) by [M] to c/blorp@lemmy.ml
     

    After submitting this to the App Store, I somehow managed to corrupt my installation of the app. I’m rushing a bit to lock down security, and I’m sorry if I corrupt anyone’s installation in the process. A reinstall will fix it.

    I’m not able to corrupt the local database a second time, so I’m hoping it’s a one time fluke. I’m constantly switching between dev and production builds. I’m also running iOS26 which is a bit unstable.

    I don’t think reinstalling the app is a huge deal, unless you use user tags, which I do. Then it kinda sucks. I clearly need some sort of backup feature.

    I still have the ability to cancel v1.9.12 to iOS if anyone else notices an issue. If you’re in TestFlight, please let me know if v1.9.12 is working.

    submitted 11 months ago* by [M] to c/blorp@lemmy.ml
     

    Reposting this comment here for transparency

    What Blorp stores:

    • Unless using the website, all the code is stored locally on your device
    • On login, we send your username/password to Lemmy/PieFed
    • The API responds with a JSON Web Token (JWT)
    • This JWT can be used to update, vote, post, etc on your account. It cannot be used to delete your account.
    • We only ever store the JWT, so it's actually impossible for Blorp to delete your account

    The bad news:

    • MacOS stores the JTW locally as plain text. After reviewing this, I'm unhappy about this.
    • iOS also stores the JTW in plain text, but has some pretty strict app sandboxing as far as I know. I'm not to worried here.
    • I think Android also sandboxes, but I'm not 100% sure.
    • Web stores the JTW in plain text, but this is pretty standard. The web enforces pretty good sandboxing between websites, and I don't run any code that isn't bundled into my app. I'm also not worried about this one.

    I'm working on a rapid security update:

    • This update will encrypt the iOS, Android, and MacOS databases on initial launch. Any unencrypted data will be destroyed immediately.
    • I'm really sorry I wasn't more careful here.
    • I also wouldn't panic as an app would have to know what file to look for, how to parse that file for the JWT, what instance the JWT belongs to.
    • This update will be v1.9.12, and will be rolled out as soon as I'm done testing

    TL;DR, MacOS is probably fine, but concerning me a little. This rapid update will bring encryption to iOS, Android, and MacOS.

     

    Following up to this post https://lemmy.ml/post/31598540

    A number of people asked for F-Droid support when I posted about my Lemmy client, and it’s here!

    Get Blorp on F-Droid

    I didn’t notice the scope of some of the app permissions until now, but half of those are unnecessary. I’ll be reducing the scope in the next release to avoid any confusion.

    submitted 11 months ago* (last edited 11 months ago) by [M] to c/blorp@lemmy.ml
     

    Someone raised an issue with login, but I’m not sure if it’s login in general or to their specific instance. Anyone noticing any issues on version 1.9.11?

    I’m not personally seeing an issue with login, but logout seems to crash the app. But I’m more concerned about login.

    Regardless, this makes me think the next version should be purely focused on bug fixes and stability with no new features.

    Edit: the bug only seems to happen when logging into a PieFed account with an unverified email address.

    submitted 11 months ago* by [M] to c/blorp@lemmy.ml
     

    In this release:

    • New way to browse posts. Just click on an image in the feed. I’m calling this the light box feed. ALSO you can zoom into photos from this view.
    • User tagging
    • Lots of bug fixes

    Lightbox feed

    • Zoom into photos!
    • Yes you can use vim h/j/k/l to navigate. Finally a sophisticated way to browse Lemmy
    • As of right now, this feed makes it slightly more difficult to engage with the comments.
      • If you click the comment button (to the left of the voting buttons) you can see the full posts
      • Eventually I’m going to make it so you can swipe up when browsing via the light box feed to view comments

    User tagging

    • As of right now there is no way to backup or export your tagged users. I’m planning on adding a way to export data from the app

    Upcoming

    • It’s not looking too promising, but I’m experimenting with MBin support
    • F-Droid!
    view more: next ›