It's like someone should make a file... maybe in /etc ... and put short names for services in it... maybe it could be called /etc/services...

▲ maeglin 2 hours ago | parent | next [-]

Top reply, and clearly based on the article's title rather than its content, as are the follow-ups. You're making this site worse.

The article is short; go read it then come back and delete.

▲

an hour ago | parent | next [-]

[deleted]

▲

imtringued 2 hours ago | parent | prev | next [-]

I read the article and now I got the impression the author should delete their project and blog.

▲

ai_slop_hater an hour ago | parent [-]

Why?

	▲	stavros 43 minutes ago \| parent [-]
		What's up with the hate? It seemed like an interesting project to me, maybe not something I see myself using, but not something deserving hate.

▲

nsowz 2 hours ago | parent | prev [-]

The author should be thankful that people are not reading the article he wrote.

	▲	saidnooneever an hour ago \| parent [-]
		you go and look in etc services for what is bound to port 5009. the article might not be the most useful but these comments are completely off the mark and stupid.

▲ tolciho 6 hours ago | parent | prev | next [-]

And then they might code up some sort of service lookup tool thingy to use on the train wreck that is the modern web.

  $ getent services gopher
  gopher               70/tcp

▲ lloeki 2 hours ago | parent | next [-]

And if they want name resolution, maybe even names that reflect the scope of its location like .localhost or .internal

▲ otabdeveloper4 5 hours ago | parent | prev | next [-]

Heck, maybe even `resolvectl service`?

▲ pratyahava 5 hours ago | parent | prev [-]

this is a nice idea, but idk why, in macos if i do `nc -l 127.0.0.1 gopher` and then try to open url "http://127.0.0.1:gopher/" - safari does not open it, no requests visible in the `nc` output.

also `curl -v http://127.0.0.1:gopher/` gives error message

  * URL rejected: Port number was not a decimal number between 0 and 65535
  * Closing connection
  curl: (3) URL rejected: Port number was not a decimal number between 0 and 65535

so the ports are named, it is nice, but in practice it does not make life easier.

▲ bandie91 4 hours ago | parent | next [-]

> http://...:gopher

is it http or gopher? :)

	▲	pratyahava 4 hours ago \| parent [-]
		i chose gopher port just as an example. try with any other service name mapped to a port number from /etc/services and the result will be the same. the OP's goal was to use many http/https services, so we are talking about many http(s) services. i just wanted to make the point that even if you have service names in /etc/services, it is not possible to use that names easily to host/access http(s) services.

▲ Tepix 4 hours ago | parent | prev [-]

As bandie pointed out, you‘re explicitly making a http request. Duh.

nc is for generic connections and handles it well.

	▲	pratyahava 4 hours ago \| parent [-]
		i know, but the OP's goal was to host/access http(s) services with names and avoid port numbers, and gopher service name was chosen by me as an example. my point was that /etc/services cannot be used for the OP's need. if you host an http(s) service on port 11111 you can reach it with url http://127.1:11111, but url http://127.1:vce/ would not work in most software. `$ grep 11111 /etc/services vce 11111/udp # Viral Computing Environment (VCE) vce 11111/tcp # Viral Computing Environment (VCE)`

▲ meitham 4 hours ago | parent | prev | next [-]

Perhaps we could even make the file the port itself, perhaps calling it a “socket”? A “unix socket” would be a great name. If we could place all these files behind a local reverse proxy then we could use localhost/jekyll or localhost/fastapi. It’s just a dream

▲ fulafel 3 hours ago | parent | prev | next [-]

If the port number space was bigger, I wonder if we would have gotten a global naming service (ala DNS) for unique service names.

You can still publish port numbers along with addresses in DNS though (SRV records).

▲ TomK32 6 hours ago | parent | prev | next [-]

Sure, but they are running web-apps they've vibe-coded (hence the .vibe tld) and for that use-case of many web apps that I run in docker containers I use nginx-proxy [0]. All the container needs is a VIRTUAL_HOST environment variable with the domain and what my router needs is an address entry for the wildcard subdomains. I even have nginx-proxy on a internet-accessible staging server.

[0] https://github.com/nginx-proxy/nginx-proxy

▲ rdevilla 3 hours ago | parent | prev | next [-]

Not modern enough. Unix is too low level, antiquated, and discriminates against those who just want to get shit done instead of reading manpages or documentation by hand.

▲ loa_in_ 3 hours ago | parent | prev | next [-]

What about identifying different instances of the same service?

▲ npodbielski 4 hours ago | parent | prev | next [-]

This is exact problem I see with all of those vibe coded software: In few years everything will be super fragmented, everyone will be using their own set of tools, or vibe coding them, themselves. Communication between teams or even between team members will become very hard because of those differences. 'What do you mean production is down? On my vibe coded dashboard everything is green!'

	▲	spiderfarmer 4 hours ago \| parent [-]
		Why do people always assume that change is permanent? It's never. After decentralisation we always see decentralisation. After a period of growth, a decline will follow. After the vibe coding hype, consolidation will follow. After rain comes sunshine.

▲ locknitpicker 4 hours ago | parent | prev | next [-]

> It's like someone should make a file... maybe in /etc ... and put short names for services in it... maybe it could be called /etc/services...

People shit-talk container orchestration systems like Kubernetes, but if anything they greatly simplified (if not completely eliminated) the need for this sort of network bookkeeping.

	▲	nesarkvechnep 4 hours ago \| parent [-]
		You forgot the /s at the end.

▲ huflungdung 5 hours ago | parent | prev [-]

[dead]