I may leave this open until there is a real need for it. Seems like most use cases could process the lat/long natively and create trail tails on the fly on the client side.
I may leave this open until there is a real need for it. Seems like most use cases could process the lat/long natively and create trail tails on the fly on the client side.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Maybe process all object locations into one polyline on the server side, then deliver that through the API as a separate endpoint.
I may leave this open until there is a real need for it. Seems like most use cases could process the lat/long natively and create trail tails on the fly on the client side.