darkhz

This is part of the cross-platform work for bluetuith, and is essentially a demo of the bluetooth-classic library.

This daemon provides a REST API interface to control Bluetooth Classic functions.

Features are:

• Pairing (with authentication)

• Connection (automatic and manual profile based connection)

• Object Push (Send and receive files)

And currently only on Linux, it additionally supports:

• Bluetooth network tethering (PANU/DUN)

• Media playback control (AVRCP)

It also provides an interactive API viewer (courtesy of Scalar Docs) via the "/docs" endpoint. Also, it provides an openapi command to output the entire OpenAPI specification of the REST API.

This is currently in preview (i.e. alpha).

Any feedback is appreciated.

This is part of the cross-platform work for bluetuith, and is essentially a demo of the bluetooth-classic library.

This daemon provides a REST API interface to control Bluetooth Classic functions.

Features are:

• Pairing (with authentication)

• Connection (automatic and manual profile based connection)

• Object Push (Send and receive files)

And currently only on Linux, it additionally supports:

• Bluetooth network tethering (PANU/DUN)

• Media playback control (AVRCP)

It also provides an interactive API viewer (courtesy of Scalar Docs) via the "/docs" endpoint. Also, it provides an openapi command to output the entire OpenAPI specification of the REST API.

This is currently in preview (i.e. alpha).

Any feedback is appreciated.

Hello Lemmy,

This is an extension of the bluetuith TUI Bluetooth Manager project, which was initially developed for Linux, and is now being ported to Windows as well. This will allow the TUI to manage Bluetooth on Windows. Note that this is just a shim, the TUI will be ported to adapt with this shim later.

This tool offers a simple command-line interface and a socket-based interface (as an interprocess communication layer) to control Bluetooth Classic based functions, like:

• Getting adapter information, performing device discovery, setting power states
• Getting device information, pairing/unpairing a device
• Connection to a device using various Bluetooth profiles
  • The supported profiles are A2DP, MAP, PBAP and OPP
  • Each connectable profile appears as a subcommand of the connect command
  • Every subcommand has multiple functions. View the documentation for more information.

This is currently alpha stage, so do expect bugs. Any bugs can be reported in the issue tracker.

I hope you enjoy this release, and any constructive feedback is appreciated.

Hello Lemmy,

This is an extension of the bluetuith TUI Bluetooth Manager project, which was initially developed for Linux, and is now being ported to Windows as well. This will allow the TUI to manage Bluetooth on Windows. Note that this is just a shim, the TUI will be ported to adapt with this shim later.

This tool offers a simple command-line interface and a socket-based interface (as an interprocess communication layer) to control Bluetooth Classic based functions, like:

• Getting adapter information, performing device discovery, setting power states
• Getting device information, pairing/unpairing a device
• Connection to a device using various Bluetooth profiles
  • The supported profiles are A2DP, MAP, PBAP and OPP
  • Each connectable profile appears as a subcommand of the connect command
  • Every subcommand has multiple functions. View the documentation for more information.

This is currently alpha stage, so do expect bugs. Any bugs can be reported in the issue tracker.

I hope you enjoy this release, and any constructive feedback is appreciated.

cross-posted from: https://lemm.ee/post/33211685

Hello Lemmy,

I am the author of bluetuith, an open-source TUI-based bluetooth manager for Linux only. I have been working on this project for over 2 years on and off, and I was wondering about extending support to other platforms as well.

To begin with, the Bluetooth Classic (BR/EDR) implementation on Linux is fairly standardized (via bluez APIs), but on other platforms, especially windows, Bluetooth APIs are finicky, and tricky to deal with, and also there is no standardized management in general.

I would like to start creating a centralized Bluetooth server or a daemon for other platforms (natively maybe), mainly Windows and Linux, which can expose relevant APIs so that clients can use them to handle Bluetooth-based operations. I know this is quite an uphill task, but I would like suggestions on how to implement it, or if anyone has a better idea, please do suggest that as well.

To summarize, my current plan is this:

• Create bluetooth servers natively for each platform, utilizing the platform's proven APIs to handle bluetooth-based functions and expose a standard API to clients
• Adapt clients to use said APIs provided by the daemons to allow the user to control bluetooth in general.

For the server implementation (mainly to other platforms), I will require contributors, so contributors are highly welcome to be involved in the project. I am in the process of securing an NLnet grant to invest into this project and mainly pay contributors to implement this platform-wise (the proposal has been accepted, and the negotiation call will be hosted in a few weeks, more details about this can be further published if anyone has questions about this. If contributors are confirmed, maybe the budget could be adjusted as well).

I apologize if the post is naive or does not fit this community's guidelines, and if it doesn't, a comment on where to redirect this question would be great.

Constructive feedback is appreciated. Thank you.

Note: By Bluetooth operations, I mainly mean Bluetooth Classic based operations.

cross-posted from: https://lemm.ee/post/33211685

Hello Lemmy,

I am the author of bluetuith, an open-source TUI-based bluetooth manager for Linux only. I have been working on this project for over 2 years on and off, and I was wondering about extending support to other platforms as well.

To begin with, the Bluetooth Classic (BR/EDR) implementation on Linux is fairly standardized (via bluez APIs), but on other platforms, especially windows, Bluetooth APIs are finicky, and tricky to deal with, and also there is no standardized management in general.

I would like to start creating a centralized Bluetooth server or a daemon for other platforms (natively maybe), mainly Windows and Linux, which can expose relevant APIs so that clients can use them to handle Bluetooth-based operations. I know this is quite an uphill task, but I would like suggestions on how to implement it, or if anyone has a better idea, please do suggest that as well.

To summarize, my current plan is this:

• Create bluetooth servers natively for each platform, utilizing the platform's proven APIs to handle bluetooth-based functions and expose a standard API to clients
• Adapt clients to use said APIs provided by the daemons to allow the user to control bluetooth in general.

For the server implementation (mainly to other platforms), I will require contributors, so contributors are highly welcome to be involved in the project. I am in the process of securing an NLnet grant to invest into this project and mainly pay contributors to implement this platform-wise (the proposal has been accepted, and the negotiation call will be hosted in a few weeks, more details about this can be further published if anyone has questions about this. If contributors are confirmed, maybe the budget could be adjusted as well).

I apologize if the post is naive or does not fit this community's guidelines, and if it doesn't, a comment on where to redirect this question would be great.

Constructive feedback is appreciated. Thank you.

Note: By Bluetooth operations, I mainly mean Bluetooth Classic based operations.

Hello Lemmy,

I am the author of bluetuith, an open-source TUI-based bluetooth manager for Linux only. I have been working on this project for over 2 years on and off, and I was wondering about extending support to other platforms as well.

To begin with, the Bluetooth Classic (BR/EDR) implementation on Linux is fairly standardized (via bluez APIs), but on other platforms, especially windows, Bluetooth APIs are finicky, and tricky to deal with, and also there is no standardized management in general.

I would like to start creating a centralized Bluetooth server or a daemon for other platforms (natively maybe), mainly Windows and Linux, which can expose relevant APIs so that clients can use them to handle Bluetooth-based operations. I know this is quite an uphill task, but I would like suggestions on how to implement it, or if anyone has a better idea, please do suggest that as well.

To summarize, my current plan is this:

• Create bluetooth servers natively for each platform, utilizing the platform's proven APIs to handle bluetooth-based functions and expose a standard API to clients
• Adapt clients to use said APIs provided by the daemons to allow the user to control bluetooth in general.

For the server implementation (mainly to other platforms), I will require contributors, so contributors are highly welcome to be involved in the project. I am in the process of securing an NLnet grant to invest into this project and mainly pay contributors to implement this platform-wise (the proposal has been accepted, and the negotiation call will be hosted in a few weeks, more details about this can be further published if anyone has questions about this. If contributors are confirmed, maybe the budget could be adjusted as well).

I apologize if the post is naive or does not fit this community's guidelines, and if it doesn't, a comment on where to redirect this question would be great.

Constructive feedback is appreciated. Thank you.

Note: By Bluetooth operations, I mainly mean Bluetooth Classic based operations.

Hello Lemmy,

invidtui is a TUI-based Invidious client, which can:

• Search for and browse videos, playlists and channels
• Play audio or video from any instance
• View, open, edit and save m3u8 playlists
• Download video/audio in any format
• Authenticate with the preferred instance, and show user feed, playlists and subscriptions

This release contains the following new features/fixes:

Embedded Recommendations tab

Recommendations for the video that is currently being played is now shown in a separate tab within the queue.

A demo and instructions are posted here

YouTube timestamps

Timestamps found within Youtube URIs are now seeked to on playback.

A demo and instructions are posted here

Custom seeking

A separate modal is shown to modify the playback position. Positions can be seeked to relatively/absolutely.

A demo and instructions are posted here

I hope you enjoy this release, and any feedback is appreciated.

Hello Lemmy,

invidtui is a TUI-based Invidious client, which can:

• Search for and browse videos, playlists and channels
• Play audio or video from any instance
• View, open, edit and save m3u8 playlists
• Download video/audio in any format
• Authenticate with the preferred instance, and show user feed, playlists and subscriptions

This release contains the following new features/fixes:

Embedded Recommendations tab

Recommendations for the video that is currently being played is now shown in a separate tab within the queue.

A demo and instructions are posted here

YouTube timestamps

Timestamps found within Youtube URIs are now seeked to on playback.

A demo and instructions are posted here

Custom seeking

A separate modal is shown to modify the playback position. Positions can be seeked to relatively/absolutely.

A demo and instructions are posted here

I hope you enjoy this release, and any feedback is appreciated.

Hello Lemmy,

invidtui is a TUI-based Invidious client, which can:

• Search for and browse videos, playlists and channels
• Play audio or video from any instance
• View, open, edit and save m3u8 playlists
• Download video/audio in any format
• Authenticate with the preferred instance, and show user feed, playlists and subscriptions

This release contains the following new features/fixes:

Dynamic theming

Themes can now be applied from theme files dynamically within the application as well as from command-line and configuration options.

A demo and instructions are posted here

Channel 'Releases' tab

A new 'releases' tab is added to the channel page, to show new content from channel authors.

Enhanced configuration handling

Configuration handling is now done in the most cross-platform way as possible.

I hope you enjoy this release, and any feedback is appreciated.

Hello Lemmy,

invidtui is a TUI-based Invidious client, which can:

• Search for and browse videos, playlists and channels
• Play audio or video from any instance
• View, open, edit and save m3u8 playlists
• Download video/audio in any format
• Authenticate with the preferred instance, and show user feed, playlists and subscriptions

This release contains the following new features/fixes:

Dynamic theming

Themes can now be applied from theme files dynamically within the application as well as from command-line and configuration options.

A demo and instructions are posted here

Channel 'Releases' tab

A new 'releases' tab is added to the channel page, to show new content from channel authors.

Enhanced configuration handling

Configuration handling is now done in the most cross-platform way as possible.

I hope you enjoy this release, and any feedback is appreciated.

Hello Lemmy,

invidtui is a TUI-based Invidious client, which can:

• Search for and browse videos, playlists and channels
• Play audio or video from any instance
• View, open, edit and save m3u8 playlists
• Download video/audio in any format
• Authenticate with the preferred instance, and show user feed, playlists and subscriptions

This release contains the following new features/fixes:

Dynamic theming

Themes can now be applied from theme files dynamically within the application as well as from command-line and configuration options.

A demo and instructions are posted here

Channel 'Releases' tab

A new 'releases' tab is added to the channel page, to show new content from channel authors.

Enhanced configuration handling

Configuration handling is now done in the most cross-platform way as possible.

I hope you enjoy this release, and any feedback is appreciated.