Skip to content
This repository has been archived by the owner on Jul 7, 2022. It is now read-only.

Make pushbullet.py great again #152

Open
6 of 14 tasks
rbrcsk opened this issue Oct 20, 2020 · 3 comments
Open
6 of 14 tasks

Make pushbullet.py great again #152

rbrcsk opened this issue Oct 20, 2020 · 3 comments

Comments

@rbrcsk
Copy link
Collaborator

rbrcsk commented Oct 20, 2020

Hello to everyone reading this,

I've originally created this package in 2013 for my personal pushing needs and decided to open source it as practice. Sometime later, I stopped using it, and also no longer had time to maintain it, so I ghosted the project.
For a while it seemed that even pushbullet is dead, so I completely let the project go in my mind.

However a few days ago, a new personal project came up, and I needed to somehow push stuff to my phone. I looked around, and saw that the Pushbullet team is working on it again! But unfortunately they removed the iOS app, so I can't use it anymore. 😥
After looking at alternatives, I've decided to go with Pushover. They have a sustainable and fair pricing structure, apps for iOS and Android, and an extensive api.

Since - to my surprise - there are still quite a few users of this library, I've decided to, I've decided to upgrade and modernise this library instead of using an existing one for pushover.

So here're my plans!

  • Triage all open issues
  • Review all pull requests
  • Publish
  • Increase test coverage
  • Set up test runner for PRs
  • Set up a Github Action to auto publish from master (in progress)
  • Set up linting, auto code formatting rules (in progress)
  • Remove Python 2.x support
  • Modernise codebase (Type hints, Python 3 only features)
  • Add pushover support
  • Update to match new pushbullett API calls
  • Find a new name (since it'll be no longer pushbullet only)
  • Maybe: move to an organization (to encourage contributions)
  • Send PRs to consumers, updating to new version

If you're interested in helping out with any of these, or have a naming idea, feel free to reply here!

@rbrcsk rbrcsk pinned this issue Oct 20, 2020
@troeggla
Copy link
Collaborator

Hey, great to hear from you! I was one of the contributors that you gave access to the project when you decided to step down.

To be honest, I also stopped using Pushbullet, so this repository gradually slipped my mind. I was encouraged to start working on it again by a pull request a while ago. I was just about to look at it properly and lo, you're back! 😅

Sounds like a solid plan, I think this package is in need of a bit of an overhaul! I'd be willing to lend my assistance if needed!

@benh57
Copy link

benh57 commented Nov 2, 2020

Also using the library recently. Thanks for maintaining it!

@johncblacker
Copy link

Would love to see a micropython (or circuitpython) version of this package. Just started looking at it so don't know how much work might be involved...I would think people doing their own IoT program development would be interested in something like this and I, myself, decided to look at it because I'd rather not have to go through IFTTT because it seems that webhooks complicates the interface more than necessary. A little disappointed in the pushbullet API as I've developed an application running on the ESP32-BASED board (Pycom WiPy) and am able to push notes, but it took too damn long to develop because of all the erroneous info out on the web and the pushbullet examples are basically for devices that have a cURL implementation...which most microcomputer os's don't have and the one's that do have little to no doc and their implementation of cURL differs from the general cURL doc (don't ask me why it's so). Anyway, like what you did with this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants