Follow pnut updates via RSS.

Changes

2017-03-14 v0.4.5b

This is a minor feature update to pnut.io.

Features
  • "Support Us" page has basic stats
  • New "Activity" account page, which shows the last 10 significant actions made in your account (logins, password changes, etc.)

2017-03-03 v0.4.5

This is a minor feature update to pnut.io.

Features
  • Invites are now created automatically
  • Each app in the directory now has its own simple page, with expanded description
  • Can hide posts directed at people you do not follow
  • Can hide "copy mentions" on the mentions endpoint
  • New Explore streams for posts that are Conversations, Trending, and Photos
  • New endpoint /users/me/channels/existing_pm retrieves a channel between a given set of users, if it exists
  • The subscribed channels endpoint (/users/me/channels/subscribed) includes count for unread PMs in the meta field
  • Can now add "notes" to unused invites, to easily track what you're doing with them
Changes
  • PM notifications are strictly indicators that you have unread PMs, and no longer contain the text of the messages
  • Better HTML version of the mention notification E-mail
  • Underscores now allowed in tags
  • Small improvement to threads and user profiles on pnut.io
  • Clients now require approval before being published to the app directory
Fixes
  • Deauthorizing a client that doesn't have any tokens now deauthorizes its scopes properly
  • Deleted posts should no longer show up in older threads/streams (as well as other bleeding possibilities)
  • Channels were showing up multiple times (a subscription bug) on the subscribed channels endpoint
  • count=-n now works as expected on post streams
  • Text with E-mail addresses in it should not be parsed as links or mentions

2017-02-04 v0.4.4

This is a minor update to pnut.io.

Features
  • All non-developers now have the ability to create one client that only they can authorize
  • Users who reposted or bookmarked posts can be included by including query parameters include_reposted_by and include_bookmarked_by
  • Basic view of tags at https://pnut.io/tags/tag and RSS for them at https://pnut.io/feed/rss/posts/tags/tag
Changes
  • Non-markdown non-client-supplied links are restricted to known TLDs
  • Mentions are allowed at the end of word breaks (think: "@, '@, (@)
  • Improved pnut.io user profiles and threads
Fixes
  • Suspended and deleted accounts no longer retrievable from pnut.io
  • public_messages and messages being authorized could result in only public_messages access
  • User RSS handles reposts properly

2017-01-25 v0.4.3

This is a minor update to pnut.io.

Features
  • include_marker=1 option available on all stream marker-capable endpoints
Changes
  • "-" was not handled correctly in link entities
  • Mutes were making messages and post actions appear multiple times

2017-01-23 v0.4.2

This is a minor update to pnut.io.

Features
  • Submitting entities.links on posts, messages, and users works (it is incongruously entities.links on posts and messages, but content.entities.links on users)
  • Markers are always included on GET /channels/{channel_id}/messages and can be included on GET /channels/{channel_id} with include_marker=1 in the query
Changes
  • Deactivating accounts is more straight-forward and consistent
Fixes
  • Unicode pos and len on entities was not handled properly
  • Tags inside markdown were parsed, breaking html/text
  • GET /users?ids= can now be @-usernames and user IDs
  • is_nsfw was not consistently handled (and sometimes ignored)

2017-01-15 v0.4.1

This is a minor update to pnut.io.

Fixes
  • Usernames were case-sensitive in password_flow
  • io.pnut.core.chat-type channels were not creatable
  • Public channels included you in the ACL unnecessarily when not authenticated
  • Deleting channel messages sometimes did not work
  • /users/me/actions not returning follow actions under some circumstances

2017-01-07 v0.4.0

This is a major update to pnut.io. The following is notable.

Features
  • raw data on posts, messages, users, and channels
  • Stream markers can be updated to the latest ID on post or message creation
  • Channel-specific sticky messages
  • Channel thread endpoint
Changes
  • Revising posts saves the complete original post, where it used to only preserve the original text and html
  • X-API-Version header changed to a major.minor.bugfix format, though in 0.x.x, all are minor or bugfix changes
Fixes
  • Avatars/covers not showing on pnut.io profiles
  • /users/me/channels/subscribed was ordered by ID only, now by most recent message or most recent creation, with clarifying pagination_id
  • Requesting a token did not return the list of scopes for it
  • New user creation did not properly handle the created "follow" action
  • Calls for user avatars/covers were not forwarding query parameters

2016-11-24 v0.3.0

This is a major update to pnut.io. The following is notable.

Features
  • More capable app directory
  • Mutes and blocks management from pnut.io
  • Channels
  • Stream markers
  • Client secret reset option
Changes
  • pagination_id added to user, post, message, and channel objects in paginated responses
  • Following, followers, muted, and blocked user lists are now paginated
  • PUT/DELETE bookmark returns the post bookmarked
  • presence endpoints now include a timestamp of the last time a user was seen (even when their status is not "offline")
  • Bookmarks are no longer restricted to the bookmarker
  • invited_by no longer included on user objects (simply able to look it up on the invite tree on pnut.io)
  • Developers required to enter password on every login
  • Markdown links and normal links are parsed by default. To prevent parsing, must include entities.parse_links=0
  • Requests for tokens respond with errors closer to OAuth 2.0 guidelines
  • Removed /posts/streams/feed, /posts/streams/link, /posts/streams/domain, /posts/streams/link (more appropriate to retrieve via future search)
  • Moved /system/configuration and /system/statistics to /sys/config and /sys/stats
Fixes
  • Inviting a user now creates a "follow" action when they auto-follow the inviter
  • Blocks are missing fewer edge cases
  • Revising a post parsing markdown links and normal links improperly
  • Users' list of actions executed against them could only filter by one type; now any number