I’m working on open source projects :)
🔗 Links:
GitHub |
---|
🍪 Get me a cookie:
Go to Ko-fi | GitHub Sponsor |
---|
I think it’s about IO interrupts?
https://www.geeksforgeeks.org/interrupts-in-8086-microprocessor/
I was chatting with a friend, and she mentioned how she tries to at least set up a README, which includes her vision for the project and her plan for the implementation, design, and goals.
Best case scenario is that the planning helps her complete the project herself. Worst case scenario, someone else can pick up where she left off and use her considerations for the project.
I’m thinking of doing that for future projects too
That t-shirt would be cool, but don’t have time to properly test our extension before then
I’m looking forward to December when I’ll have time to work on it. I’ll try to attend some office hours, I didn’t know that was an option
Sorry for the delay
Yes it does search from the title/user, but I’m planning to switch to resolve_object in a future update: https://github.com/cynber/lemmy-instance-assistant/issues/52#issue-1934318266
For smaller extensions, you can start by looking at the manifest.json
as this file is the entry point. You can see which part of the code needs access to ‘everything’ and go from there.
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json
For example, with Instance Assistant for Lemmy, you need to give access to all sites because it needs to run on any Lemmy site and that’s not something you can hardcode in.
Good to know, could you share what website you were trying to post from?
I think one thing I should implement is a little toast message that explains what went wrong (ex. No title contents found)
Sorry to those that have already seen this. I’m trying to space out the posts so it’s not in a large clump in your feeds. People have different subscription lists, so I’m trying to reach those that haven’t seen it yet.
These are the last 4 posts :)
Sorry to those that have already seen this. I’m trying to space out the posts so it’s not in a large clump in your feeds. People have different subscription lists, so I’m trying to reach those that haven’t seen it yet.
These are the last 4 posts :)
From what I’ve experienced with my extension, every update has to go through a review process. Firefox is pretty fast, chrome takes a few days and edge takes a while (opera hasn’t finished reviewing my first version, so I stopped trying with them).
The only time I failed a review was early on when my build script choked and I submitted an empty file to Chrome (whoops). So I can’t really tell how good those reviews are, but I’m not planning on testing them. I just know that they exist
Thank you for putting all this together!
Potential conflict of interest: I help with !instance_assistant@lemmy.ca
Having a separate list for extensions would work nicely, although I think it fits to have the extensions listed here. There are few actual browser extensions for Lemmy/Kbin/Mastodon. There are a lot of scripts, and we were working on incorporating the better scripts into the extension for the same reasons you mentioned above. Scripts are harder to manage and review
My thoughts on the questions.