I like FOSS (free and open source software). Have contributed bug reports and feature suggestions to open source projects that got accepted (e.g. the ability to block instances on lemmy). Check out my github if you’re into that kind of stuff.

  • 50 Posts
  • 75 Comments
Joined 6 years ago
cake
Cake day: August 3rd, 2020

help-circle


  • You approved the Lemmy login once it redirected to Github right?

    yep

    aybe try going into your Github settings and removing Voyager entry, then try again

    done

    And try a different browser, or disabling privacy plugins.

    switched from firefox to chrome and disabled extensions, still fails.

    Also check the browser console for any errors

    I am getting a bunch of them, here is a copy paste:

    callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 [unlazy] Missing data-src or data-srcset attribute <img class=​"overflow-hidden pictrs-image object-fit-cover img-icon me-1" src=​"https:​/​/​voyager.lemmy.ml/​api/​v4/​image/​a32c32b6-c8c3-4d17-ab40-46c4ca518868.webp?max_size=96" alt title loading=​"lazy" width=​"96" height=​"96">​ (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 requestAnimationFrame (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 (anonymous) @ callback?code=3ed55281d78996fe5c2f&state=82f04f1d-37b2-42fd-b9ae-459081aa151a:9 9046.client.js:2 Bad element for masonry: .post-listings-grid l @ 9046.client.js:2 i @ 9046.client.js:2 y @ client.js:2 await in y onLoad @ client.js:2 client.js:2 POST https://voyager.lemmy.ml/api/v4/oauth/authenticate 400 (Bad Request) wrapper @ client.js:2 authenticateWithOAuth @ client.js:2 doLogin @ client.js:2 componentDidMount @ client.js:2 (anonymous) @ client.js:2 u @ client.js:2 d @ client.js:2 await in d (anonymous) @ client.js:2 (anonymous) @ client.js:2 3585 @ client.js:2 n @ client.js:2 (anonymous) @ client.js:2 (anonymous) @ client.js:2 client.js:2 Request error while calling POST /oauth/authenticate with {“code”:“3ed55281d78996fe5c2f”,“oauth_provider_id”:1,“redirect_uri”:“https://voyager.lemmy.ml/oauth/callback”} wrapper @ client.js:2 await in wrapper authenticateWithOAuth @ client.js:2 doLogin @ client.js:2 componentDidMount @ client.js:2 (anonymous) @ client.js:2 u @ client.js:2 d @ client.js:2 await in d (anonymous) @ client.js:2 (anonymous) @ client.js:2 3585 @ client.js:2 n @ client.js:2 (anonymous) @ client.js:2 (anonymous) @ client.js:2


  • And you should care what people you don’t know on the internet think because… ?

    social media is not a reliable source. it can expose you to new information, but it is not reliable .

    Feedback is how you learn. how you find out what works and just as importantly what don’t work.

    i think there was a study that showed that people that take a course on decision making have lower anxiety. it makes sense, once you do a risk-reward analysis and consider alternatives it makes you accept the risk and act despite it. realizing the anxiety is unhelpful or ineffective repeatedly leads to Desensitization and eventually reduces it.

    with that said, there might be some underlining issue and you need to work on self regulation skills. using stuff like CBT/ACT/NSDR/meditation/stoicism. there is a open source test for the big five personality test. if you score high on neuroticism, it might indicate you should work on it.




  • wiki_me@lemmy.mltoLinux@lemmy.mlRTFM
    link
    fedilink
    English
    arrow-up
    3
    ·
    4 months ago

    it’s just that it doesn’t work efficiently enough.

    Yeah, but we live in a world of limited resources. in particular labor and specifically knowledgeable linux nerds willing to answers questions for free. If everyone will have that mindset there won’t be a lot of time left to answer the difficult questions .

    With that said i agree that occasionally if its done its probably no big deal, there is also linux 4 noobs for those who want to ask some questions to help getting started with linux.


  • TBH i think you’re overthinking it, funding software development and running businesses like open source software development is often driven by self interest (even if it’s not easy to accept) . Like in software development part of it is throwing stuff at the wall and seeing what sticks. So trying to transition to more closed model is expected (some of the projects you mentioned went back to being open source).

    Sure i have my opinions about software licensing but for me open source is good enough. if something like that will happen and the software is good a fork will be made. That is a acceptable risk-reward calculation to me.



  • The website is already linking to google play store and apple store. right now apps that are purely web don’t have a platform to read reviews on . plus neodb lib.reviews are open source although they might not yet be ready for the task yet.

    Besides Lemmy mainly gets promoted by word of mouth (eg people recommending it on Reddit)

    I doubt that, any data? similarweb shows the top referring site for now is openalternative.co (although at least one of the referring sites mentioned doesn’t seem to make sense for me ).

    If people want to review Lemmy communities, it would make more sense to make a Lemmy community for that purpose.

    I think people would want to see average ratings. reading a community page means you only read 1-3 reviews and that sample size is too small and potentially biased. you could just run into people who hate a instance for some particular reason (and it’s not hard for me to think of reasons like that).





  • We have lemmy apps that still aren’t supporting API changes added over a year ago. We even had one such case last week.

    That sounds like something could be improve. is there some sort of warning mechanism in place?

    Say when using a lemmy client. the client either specifies its a production build. or if its not then the lemmy server reports where deprecated API’s are used.


  • Not sure that is the correct approach. break frequently break often seems better (that’s what PHP and java seem to do as far as i can tell, unlike python 3 which caused a lot of drama).

    notify a API is deprecated. give some time for users to update to the new API (1 year?) and then remove it.

    Of course after version 1.0 there might be less breakage so it won’t be a be problem.



  • This isn’t what i had in mind. i meant more like changing the line to something like:

    We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, donating money and helping find and fix bugs.

    With “donating money” maybe replaced with “funding”.