1.6.0 - IPLD protocol, fixed `pubsub://`

Added support for the new ipld:// protocol which exposes the raw data model of IPFS.
You can now use GET ipld://cid/ to get raw data and auto translate it between codecs with the Accept header or the ?format search parameter.
This also means that you can view the raw data from an IPFS CID by passing it to IPLD.

On a similar vein, the pubsub:// protocol has been fixed so you can now use new EventSource('pubsub://topic_here?format=json') to subscribe to a stream of events, and use fetch('pubsub://topic_here/, {method: 'POST', body: JSON.stringify({some:"data"}}})` to publish data to the network.

1.5.0 - Update IPFS, remove GUN

• Support for gun:// has been removed for the time being due to lack of usage and that GUN itself works best as a JS API within web apps and didn't have obvious ways to map to URLs within a browser
• js-ipfs-fetch got updated with support for doing a GET to download data as CAR files or RAW blocks using the ?format query string. You can also upload a CAR file using POST ipfs://localhost/ {Content-Type: application/vnd.ipld.car}.
• go-ipfs got updated to 0.14 which should enable hole punching by default for better connectivity between home networks.
• hypercore-fetch got updated to fix a bug where using reponse.arrayBuffer() would yield junk data.

1.4.2 - Fix IPFS on M1 Mac OS

Fixes an issue where the IPFS gateway binary was not being referenced correctly on MacOS.

1.4.1 - Fixes for bt protocol and localhost urls

• Fixed bt:// protocol not loading due to a missing dependency (Thanks @resession )
• Navigating to localhost URLs will use HTTP by default instead of HTTPS (Thanks @techie177 )

1.4.0 - New System Tray, user agent fixes

@techie177 Added a new System Tray feature

• Now when you close all windows, any p2p protocols that you started to seed data will still be active
• You must explicitly quit the app by either using ctrl+Q, the menu, or the tray Quit menu.
• You can open new windows by clicking the system tray and pressing new window
• We also have some minor improvements to setting the User Agent string to properly contain AgregoreBrowser

1.3.4 - Fix extension loading on MacOS

Fixes an issue where extensions were not loading on MacOS due to a difference in how the application gets unpacked.

1.3.1 - Fix SSB rendering

The previous release didn't manage to load the updated version of the renderer, this fixes that.

1.3.0 - Web Archiving integration, rendering SSB posts

WebRecorder

We now have built-in support for WebRecorder via an integrated ArchiveWeb.page extension. This allows you to record "web archives" from any web page you visit which you can replay while offline or share with others.

A next step for this feature will be to integrate it's IPFS publishing feature with Agregore's built-in IPFS/IPNS protocol handlers and to test getting archives created on Desktop loaded on Mobile and shared over local networks.

SSB Rendering

When you load up an SSB post's JSON via the ssb:// protocol scheme, the built in extension renderer will now parse the post data and automatically render it as markdown. This lets Agregore act as a proper SSB viewer rather than just having the JSON. You can of course still access the raw JSON via the fetch() API

1.2.0 - Ublock Origin integration, fixes, Extension improvements

• Fixes for creating desktop shortcut "bookmarks" on linux @av8ta
• Updates to use the latest ssb-fetch (support for range requests, custom mime type for json responses) @av8ta
• Extensions updates/fixes:
  • Adds rendering of browser action badges
  • Updates browser action icons/text as it changes
  • Fixed auto-resizing of browser action popups
  • Adds some events to extension system that were needed for Ublock Origin
• Embeds uBlock Origin into Agregore by default.

1.1.1 - Fix pubsub protocol, add `tabs.onUpdated` extensions API

• Bumps the extensions system to support tabs.onUpdated which is needed for WebRecorder support
• Fixed pubsub:// protocol handlers not being invokable due to a missing protocol handler registration (the actual handler implementation was already there)