Channels

Public threads, grouped by where they are happening. Pick a place to read its topics.

announcements

Filed under this by 25 pieces from 1 source · the whole ledger

  1. Introducing Spotify Soloistspotify.comstory
  2. Web API quota updates for Development Modespotify.comstory
  3. Introducing refresh token expirationspotify.comstory
  4. Update on Developer Access and Platform Securityspotify.comstory
  5. Reminder: OAuth Migration - 27 November 2025spotify.comstory
  6. Updating the Criteria for Web API Extended Accessspotify.comstory
  7. Increasing the security requirements for integrating with Spotifyspotify.comstory
  8. Introducing some changes to our Web APIspotify.comstory
  9. Security Notice: Deprecation of TLS 1.0 and 1.1spotify.comstory
  10. Introducing the new Spotify for Developersspotify.comstory
  11. Introducing Spotify's Guide for Developing Accessible Applicationsspotify.comstory
  12. An update on the deprecated mobile streaming SDKsspotify.comstory
  13. Sunset of libspotify on May 16, 2022spotify.comstory
  14. The Ads API is now on Spotify for Developersspotify.comstory
  15. Introducing the iFrame APIspotify.comstory
  16. Web Playback SDK is out of beta!spotify.comstory
  17. Introducing the Web API status pagespotify.comstory
  18. Create native mobile and desktop apps with Spotify using PKCEspotify.comstory
  19. The Spotify for Developers forum is now openspotify.comstory
  20. Search, browse and follow podcasts using the new Podcast APIsspotify.comstory
  21. New: Build offline Spotify experiences using our iOS and Android SDKsspotify.comstory
  22. The public repo of the old Spotify mobile streaming SDKs will shut down Nov 1st 2019spotify.comstory
  23. Update to our iOS SDKspotify.comstory
  24. Updates to our Mobile Developer Platformspotify.comstory
  25. Play from any starting position with Spotify Connectspotify.comstory

A topic here is a label each publisher printed on its own piece. Equal labels from different publishers are shown together; that does not make them one subject.

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Where this comes from

Solid branches are exact SourceFrontier census edges used by this page. Folded branches share the publisher but did not supply these items.

Hacker News

1 feed · 1 available · hn.algolia.com

text1 channel · 1 available
  1. Used here by hn-new hacker-attention Hacker News
    used on this pagehacker-attention

Latest

It's enough - vibecoding tag crossed from useless to harmfulThe vibecoding tag has been getting more and more useless for a while now. It lost the original meaning as the culture of software engineering with LLMs matured a bit. It got silly when posts talking about LLMs in general got tagged. It got useless when posts even mentioning some project created with LLMs in passing got tagged. Now it actually got harmful to the community when tagging posts turns away very valuable members https://lobste.rs/c/vecuxj I sighed and moved on for a while now as almost everything gets tagged - you can skip a word. But now it not only carries no signal whatsoever, it turns away people creating original technical content - which is what I assume anti-vibecoding people would actually like to see more of. Please split it or kill it. But we'd be better off without what exists today. Added: To be clear, I totally support people filtering out llm-generated or llm-centric posts. But right now everyone loses. And every day we lose a little bit more. Whether it's an original, interesting arviraptor lobste.rs