I write bugs and sometimes features! I’m also @CoderKat@kbin.social.

  • 3 Posts
  • 48 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle
  • CoderKat@lemm.eetoPrivacy@lemmy.mlWhat the actual fuck?!
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 year ago

    Yeah. There’s literally nothing you can put on a prompt that will truly work. It’s still a good idea to prompt cause it will reduce how many people approve the prompt, but there is a significant number of people who don’t read prompts at all and just insta-confirm.

    At best, I think you could design it so there’s no way for an app to request certain permissions themselves. They’d have to be opted in from the system settings and apps could only tell you how to do it. But that’s a usability nightmare that is quite frustrating for legitimate usages. There’s already some super sensitive permissions that do this. I think the ability to install apps, ability to display over other apps, and password managers for android.




  • CoderKat@lemm.eetoFediverse@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 year ago

    Yeah. I don’t know what these “just post” types think it’s like. I tried making some relatively niche posts early on, trying to spark discussion in communities for some games I was playing. Got a single digit number of comments at most. Sometimes none. Small communities don’t get seen and niche posts in bigger communities are less likely to get votes. It feels very discouraging if you spend 30 minutes to make a post that seemingly nobody even sees.

    Some folks here don’t seem to want to hear it because they badly want Lemmy to be better (and I kinda get that), but where niche communities are concerned, Reddit is unfortunately better.

    Also, the “jUsT PoSt” replies are acting like everyone wants to post. Not everyone does and we shouldn’t be acting like they’re idiots because they don’t want to be the one to make the posts. It’s perfectly valid to want to read other people’s posts. There’s also some stuff you just can’t post and expect it to work. Eg, I read episode discussions on Reddit. Those can really only take off if you post them immediately when the episode airs. It feels like only Star Trek has those here. For every other show, I just go back to Reddit.



  • There’s a lot of common patterns, but you have to understand how URLs work. You have to recognize which URL parameters are tracking ones or even just might be tracking. And that means you have to know how they work and that takes a moment.

    In brief, URL parameters start after a ? in the URL and are formatted like key1=values&key2=value2. You can’t usually remove all parameters because not all are tracking. To further complicate things, URLs can also have an anchor starting with a # character which will be after the URL parameters. You often don’t want to remove that (though theoretically the anchor could in fact contain tracking details).

    It’s often trial and error to see which parameters you can remove. I do this a lot since I write a lot of technical documentation. Clean URLs make the documentation more compact and less likely to break. It’s not just tracking stuff, but sometimes you need to remove temporal data that makes a page display data from a specific time when you want it to just default to the current time (etc).







  • Also, if OP is new, they may not yet be aware of aliases and functions. Generally you’d out those in a ~/.bashrc file that gets automatically executed when a terminal starts. They’ll allow you to save a more complex command as a really simple one. And particularly can be useful when things you want to run are in unusual directories. Eg, maybe you have a git repo somewhere that contains some project you spend most of your time on, so you could have an alias that just cd’s you to it’s directory. Git also has its own way of doing aliases and that’s really nifty for the more complicated git commands (or the more commonly used, like st for status).





  • I mean, yes, it’s a little more effort, but I think you’re over playing how much effort is required. Writing a half decent readme is vastly easier than frankly any feature or bug fix. Taking a couple of notable screenshots is super easy. Writing docs is hard (I’ve written tons for large and complicated projects), but readmes are the easiest and including screenshots is really quite easy.

    Everywhere supports markdown in readmes now. Literally everywhere I’ve ever hosted code. And markdown with links to images is perfectly fine even if viewed in plain text mode. They’ll just click the link and view the image standalone. I’ve done that plenty of times, too. Every editor (plus in-browser code hosts in plain text mode) makes it easy.


  • Yes. Git can store binary files fine. It’s not the most efficient for storing them, but it works, especially for a small number of screenshots. For updating and theme, that’s entirely up to you. It’s all a judgement call. If you want to show off your functionality (like a dark mode), I encourage you to include screenshots of it. If you substantially change your UI, update the images.

    You don’t have to update for every new button you add. It’s more about giving a general impression of the UI. Is it minimalist? Is it a chaotic mess? Does it look like it fits in naturally with whatever OS appears to have been used? Does it look like any thought was put into UI and UX? Those are the kinds of things you’re trying to answer.


  • I think that doesn’t work for most smaller projects. That’ll work for something like Firefox, but there’s little reason for random, unheard of tools to have an image on the web. Plus the naming of some projects is super generic, which can make it hard to find correct images.

    Some software changes appearance often, too, and google is bad at knowing what up to date is. It can be really easy to find wildly out of date images as the top results.