#coap — Public Fediverse posts

The diff on CSV data that #Forgejo (and thus #Codeberg) provides is really useful – right now for reviewing new #CoAP options and content formats as they go into the `coap-numbers` crate.

The diff on CSV data that #Forgejo (and thus #Codeberg) provides is really useful – right now for reviewing new #CoAP options and content formats as they go into the `coap-numbers` crate.

The diff on CSV data that #Forgejo (and thus #Codeberg) provides is really useful – right now for reviewing new #CoAP options and content formats as they go into the `coap-numbers` crate.

The diff on CSV data that #Forgejo (and thus #Codeberg) provides is really useful – right now for reviewing new #CoAP options and content formats as they go into the `coap-numbers` crate.

The diff on CSV data that #Forgejo (and thus #Codeberg) provides is really useful – right now for reviewing new #CoAP options and content formats as they go into the `coap-numbers` crate.

RFC 9953: DNS over the Constrained Application Protocol (DoC)

Le protocole #CoAP est un protocole léger, conçu pour les objets connectés. Ce #RFC décrit comment faire du #DNS au-dessus de CoAP. Si votre brosse à dents a besoin de faire du DNS, c'est ce RFC qu'il faut lire.

@miri64

https://www.bortzmeyer.org/9953.html

RFC 9953: DNS over the Constrained Application Protocol (DoC)

Le protocole #CoAP est un protocole léger, conçu pour les objets connectés. Ce #RFC décrit comment faire du #DNS au-dessus de CoAP. Si votre brosse à dents a besoin de faire du DNS, c'est ce RFC qu'il faut lire.

@miri64

https://www.bortzmeyer.org/9953.html

RFC 9953: DNS over the Constrained Application Protocol (DoC)

Le protocole #CoAP est un protocole léger, conçu pour les objets connectés. Ce #RFC décrit comment faire du #DNS au-dessus de CoAP. Si votre brosse à dents a besoin de faire du DNS, c'est ce RFC qu'il faut lire.

@miri64

https://www.bortzmeyer.org/9953.html

RFC 9953: DNS over the Constrained Application Protocol (DoC)

Le protocole #CoAP est un protocole léger, conçu pour les objets connectés. Ce #RFC décrit comment faire du #DNS au-dessus de CoAP. Si votre brosse à dents a besoin de faire du DNS, c'est ce RFC qu'il faut lire.

@miri64

https://www.bortzmeyer.org/9953.html

RFC 9953: DNS over the Constrained Application Protocol (DoC)

Le protocole #CoAP est un protocole léger, conçu pour les objets connectés. Ce #RFC décrit comment faire du #DNS au-dessus de CoAP. Si votre brosse à dents a besoin de faire du DNS, c'est ce RFC qu'il faut lire.

@miri64

https://www.bortzmeyer.org/9953.html

Preparing a demo for the @ariel booth at #CLT. If things goes to plan, you can control different #embedded systems running the same application from your browser.

#CLT2026 #IoT #CoAP

Preparing a demo for the @ariel booth at #CLT. If things goes to plan, you can control different #embedded systems running the same application from your browser.

#CLT2026 #IoT #CoAP

Preparing a demo for the @ariel booth at #CLT. If things goes to plan, you can control different #embedded systems running the same application from your browser.

#CLT2026 #IoT #CoAP

Preparing a demo for the @ariel booth at #CLT. If things goes to plan, you can control different #embedded systems running the same application from your browser.

#CLT2026 #IoT #CoAP

Preparing a demo for the @ariel booth at #CLT. If things goes to plan, you can control different #embedded systems running the same application from your browser.

#CLT2026 #IoT #CoAP

@nils I did have some reservations about using @ratatui_rs for embedded devices (mainly that they're natively pixel based, so why go through a typewriter interface when there's no legacy) -- but seeing how reasonable that looks in code already at this quick prototype makes me reconsider.

Don't hold your breath for a text based #CoAP web browser, but I'd love to build one.

@nils I did have some reservations about using @ratatui_rs for embedded devices (mainly that they're natively pixel based, so why go through a typewriter interface when there's no legacy) -- but seeing how reasonable that looks in code already at this quick prototype makes me reconsider.

Don't hold your breath for a text based #CoAP web browser, but I'd love to build one.

@nils I did have some reservations about using @ratatui_rs for embedded devices (mainly that they're natively pixel based, so why go through a typewriter interface when there's no legacy) -- but seeing how reasonable that looks in code already at this quick prototype makes me reconsider.

Don't hold your breath for a text based #CoAP web browser, but I'd love to build one.

@nils I did have some reservations about using @ratatui_rs for embedded devices (mainly that they're natively pixel based, so why go through a typewriter interface when there's no legacy) -- but seeing how reasonable that looks in code already at this quick prototype makes me reconsider.

Don't hold your breath for a text based #CoAP web browser, but I'd love to build one.

@nils I did have some reservations about using @ratatui_rs for embedded devices (mainly that they're natively pixel based, so why go through a typewriter interface when there's no legacy) -- but seeing how reasonable that looks in code already at this quick prototype makes me reconsider.

Don't hold your breath for a text based #CoAP web browser, but I'd love to build one.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

@reiver I think #CoAP is a good fit. It's easy enough to explain on a napkin, extensible, has the familiar REST semantics, and can be implemented on the smallest of devices.

Plus it has a well-vetted security mechanism that is lightweight enough to be implemented by a single person.

@reiver I think #CoAP is a good fit. It's easy enough to explain on a napkin, extensible, has the familiar REST semantics, and can be implemented on the smallest of devices.

Plus it has a well-vetted security mechanism that is lightweight enough to be implemented by a single person.

@reiver I think #CoAP is a good fit. It's easy enough to explain on a napkin, extensible, has the familiar REST semantics, and can be implemented on the smallest of devices.

Plus it has a well-vetted security mechanism that is lightweight enough to be implemented by a single person.

@reiver I think #CoAP is a good fit. It's easy enough to explain on a napkin, extensible, has the familiar REST semantics, and can be implemented on the smallest of devices.

Plus it has a well-vetted security mechanism that is lightweight enough to be implemented by a single person.

@reiver I think #CoAP is a good fit. It's easy enough to explain on a napkin, extensible, has the familiar REST semantics, and can be implemented on the smallest of devices.

Plus it has a well-vetted security mechanism that is lightweight enough to be implemented by a single person.

We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet. This includes security: I guess I just sent the first encrypted request over slipmux ever, and its security setup was unmodified from #ArielOS's CoAP example.
Implementation is available in #RiotOS (#C), and WIP for Ariel (#RustLang) and #aiocoap (#Python).

We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet. This includes security: I guess I just sent the first encrypted request over slipmux ever, and its security setup was unmodified from #ArielOS's CoAP example.
Implementation is available in #RiotOS (#C), and WIP for Ariel (#RustLang) and #aiocoap (#Python).

We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet. This includes security: I guess I just sent the first encrypted request over slipmux ever, and its security setup was unmodified from #ArielOS's CoAP example.
Implementation is available in #RiotOS (#C), and WIP for Ariel (#RustLang) and #aiocoap (#Python).

We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet. This includes security: I guess I just sent the first encrypted request over slipmux ever, and its security setup was unmodified from #ArielOS's CoAP example.
Implementation is available in #RiotOS (#C), and WIP for Ariel (#RustLang) and #aiocoap (#Python).

We're gathering momentum for slipmux, a transport of #CoAP over serial ports. That specification allows #embedded developers on simple boards that just have a UART to use the same tools with it as for talking to devices across the Internet. This includes security: I guess I just sent the first encrypted request over slipmux ever, and its security setup was unmodified from #ArielOS's CoAP example.
Implementation is available in #RiotOS (#C), and WIP for Ariel (#RustLang) and #aiocoap (#Python).

… and it was a success: We implemented runtime updates over #CoAP, and with our stack's access control, restricting changes to the VM code to authorized users is just a matter of four lines of config.

#IETFHackathon

… and it was a success: We implemented runtime updates over #CoAP, and with our stack's access control, restricting changes to the VM code to authorized users is just a matter of four lines of config.

#IETFHackathon

… and it was a success: We implemented runtime updates over #CoAP, and with our stack's access control, restricting changes to the VM code to authorized users is just a matter of four lines of config.

#IETFHackathon

… and it was a success: We implemented runtime updates over #CoAP, and with our stack's access control, restricting changes to the VM code to authorized users is just a matter of four lines of config.

#IETFHackathon

Development of aiocoap, my Python CoAP library, is approaching its next breaking release.

If there's anything about its usability as a library that has been bugging you, especially if it would require breaking changes: Let me know soon, either here or on the issue tracker at https://github.com/chrysn/aiocoap/issues

#aiocoap #Python #CoAP

Development of aiocoap, my Python CoAP library, is approaching its next breaking release.

If there's anything about its usability as a library that has been bugging you, especially if it would require breaking changes: Let me know soon, either here or on the issue tracker at https://github.com/chrysn/aiocoap/issues

#aiocoap #Python #CoAP

Development of aiocoap, my Python CoAP library, is approaching its next breaking release.

If there's anything about its usability as a library that has been bugging you, especially if it would require breaking changes: Let me know soon, either here or on the issue tracker at https://github.com/chrysn/aiocoap/issues

#aiocoap #Python #CoAP

Development of aiocoap, my Python CoAP library, is approaching its next breaking release.

If there's anything about its usability as a library that has been bugging you, especially if it would require breaking changes: Let me know soon, either here or on the issue tracker at https://github.com/chrysn/aiocoap/issues

#aiocoap #Python #CoAP

Development of aiocoap, my Python CoAP library, is approaching its next breaking release.

If there's anything about its usability as a library that has been bugging you, especially if it would require breaking changes: Let me know soon, either here or on the issue tracker at https://github.com/chrysn/aiocoap/issues

#aiocoap #Python #CoAP

@khalid Now that toot makes me kind'a feel bad about wanting to introduce coap:// to that list of #smolweb protocols.

Then again, #CoAP excels at proxying (and was carefully designed to facilitate it even across protocols), so a client could go through a CoAP proxy to access any of the others (unless it happens to implement any of the others as well).