3 ms·

The dict protocol really show it's age, notably the stateful connection part. Having a new protocol based on HTTP and JSON similar to LSP would be nice but ther

by gwervc 2y ago

The dict protocol really show it's age, notably the stateful connection part. Having a new protocol based on HTTP and JSON similar to LSP would be nice but there is no real interest. (I made and used my own nonetheless in a research project. It may even be deployed but desactivated in another one) This biggest issue isn't technical, it's the fact organizations having dictionary data don't want third-party to interact with it without paid licensing.

steve_taylor 2y ago
I hate the fact that corporate IT collectively decided to block every port except 80 and 443, making it necessary to base new protocols on HTTP instead of TCP/IP.
- jolux 2y ago
  In my experience HTTP is a better foundation for novel protocols in most cases.
  - LambdaComplex 2y ago
    Doesn't HTTP require binary data to be converted to base64 encoding, thereby increasing its size on the wire? That seems suboptimal for a lot of use cases
    - kragen 2y ago
      no, it does not, neither in requests nor in replies. possibly you are thinking of smtp
      - LambdaComplex 2y ago
        > possibly you are thinking of smtp You're right, I definitely was
    - devmor 2y ago
      It does not - you are perhaps thinking of GET queries: URL data often must be base64 encoded as URLs are parsed as characters. HTTP bodies can be made up of any data in any encoding you wish.
cyanydeez 2y ago
Might be something LLM based for organization knowledge base
Towaway69 2y ago
There is always wiktionary, I would assume they have an api of some sort. That would cover the http & json bit! https://wiktionary.org https://wiktionary.org
- mavhc 2y ago
  There's not a specific Wiktionary API, just the general Mediawiki stuff https://en.wiktionary.org/wiki/User:Amgine/Wiktionary_data_%26_API https://en.wiktionary.org/wiki/User:Amgine/Wiktionary_data_%...
pushupentry1219 2y ago
> Having a new protocol based on HTTP and JSON This is just a HTTP/REST api? These exist already.

by gwervc 2y ago

steve_taylor 2y ago

I hate the fact that corporate IT collectively decided to block every port except 80 and 443, making it necessary to base new protocols on HTTP instead of TCP/IP.

jolux 2y ago
In my experience HTTP is a better foundation for novel protocols in most cases.
- LambdaComplex 2y ago
  Doesn't HTTP require binary data to be converted to base64 encoding, thereby increasing its size on the wire? That seems suboptimal for a lot of use cases
  - kragen 2y ago
    no, it does not, neither in requests nor in replies. possibly you are thinking of smtp
    - LambdaComplex 2y ago
      > possibly you are thinking of smtp You're right, I definitely was
  - devmor 2y ago
    It does not - you are perhaps thinking of GET queries: URL data often must be base64 encoded as URLs are parsed as characters. HTTP bodies can be made up of any data in any encoding you wish.

cyanydeez 2y ago

Might be something LLM based for organization knowledge base

Towaway69 2y ago

There is always wiktionary, I would assume they have an api of some sort. That would cover the http & json bit! https://wiktionary.org https://wiktionary.org

mavhc 2y ago
There's not a specific Wiktionary API, just the general Mediawiki stuff https://en.wiktionary.org/wiki/User:Amgine/Wiktionary_data_%26_API https://en.wiktionary.org/wiki/User:Amgine/Wiktionary_data_%...

pushupentry1219 2y ago

> Having a new protocol based on HTTP and JSON This is just a HTTP/REST api? These exist already.