Skip to content

Tags: tesaguri/pipitor

Tags

v0.3.0-alpha.9.4+build1

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
Version 0.3.0-alpha-9.4+build1

### Changed

- Make release binary not dynamically link against OpenSSL 1.

v0.3.0-alpha.9.4

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
Version 0.3.0-alpha.9.4

### Fixed

- Fixed issue where the bot considered `201 Created` responses as
  failure

v0.3.0-alpha.9.3

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
Version 0.3.0-alpha.9.3

### Fixed

- Fix authorization against Twitter

v0.3.0-alpha.9.2

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
Version 0.3.0-alpha.9.2

### Added

- Bring back `pipitor twitter-login` command

### Fixed

- Fix an authorization issue against Twitter

v0.3.0-alpha.9.1

Unverified

This tag is not signed, but one or more authors requires that any tag attributed to them is signed.
Version 0.3.0-alpha.9.1: Live in Disgrace, Done Dirty

This is a hotfix to v0.3.0-alpha.9 (which is the latest _working_
release; the later releases have issues serious enough to make them
unusable at all) for those who need to keep the bots operational under
the new access tiers for Twitter API.

The release only supports Tweeting WebSub entries via the write-only
Free tier access, meaning that it cannot fetch Tweets nor Retweet them.

Support for the Basic+ tiers is not planned, partly because API v2 lacks
important features (e.g. `GET /2/lists/:id/tweets` does not have an
equivalent of the `since_id` parameter, required for keeping the Tweet
cap usage optimal. There is a related [topic] on Twitter Developers
community, which unsurprisingly remains neglected), and most
importantly, I have lost the enthusiasm for the platform after all the
dramas. Now, I even find myself feeling indignified writing code for the
platform. Let alone paying $100/mo. for it.

[topic]: <https://twittercommunity.com/t/support-for-a-since-id-parameter-for-list-tweets-lookup-endpoint/177662>

This is intended to be a dirty hotfix made just to keep existing bots
operating for the time being. I hope there will be a proper release from
the main branch, fixing all the issues and maybe completely removing the
Twitter inbox support. However, the project is now undergoing a major
refactoring process and that release may not be very soon.

dhall-package-v0.3.0-alpha.15

Verified

This tag was signed with the committer’s verified signature.
tesaguri Daiki Mizukami

    

v0.3.0-alpha.15

Verified

This tag was signed with the committer’s verified signature.
tesaguri Daiki Mizukami
Version 0.3.0-alpha.15

### Added

- Use `media:description` in feeds.

### Fixed

- Improve handling of database

v0.3.0-alpha.14

Verified

This tag was signed with the committer’s verified signature.
tesaguri Daiki Mizukami
Version 0.3.0-alpha.14

### Added

- Add `winsqlite3` feature
- Check for feed entries upon launch/reload and topic discovery
- Support `br` Accept-Encoding

dhall-package-v0.3.0-alpha.14

Verified

This tag was signed with the committer’s verified signature.
tesaguri Daiki Mizukami

    

v0.3.0-alpha.13

Verified

This tag was signed with the committer’s verified signature.
tesaguri Daiki Mizukami
Version 0.3.0-alpha.13

### Changed

- Fix an issue where `since_id` was not set properly in Twitter List API
requests
- Optimize network usage of Twitter List API requests