endyourenite wrote:

too long

Redstone1080 wrote:

I propose .obs3 as a file extension /j
Maybe .obsp (Obscure Project) could work? If that's taken, what about .obc (Obscure)?

endyourenite wrote:

(#360)
too long

i_eat_coffee wrote:

(#364)
.obsp reminds me of nbsp; which is basically the space bar in html

Catzcute4 wrote:

(#368)
guys, stop warring over file types. just use .txt

BigNate469 wrote:

(#370)
As I mentioned (at some point) earlier in this topic, why not just ignore file type (for now), because it seems everyone here can't come to a consensus on it, and just look at MIME type?

I don't think there would be any dispute over application/obscure (although also accept text/plain), because as far as MIME types go, that's about medium sized. In addition, application/* is specifically for program and executable files, and application/octet-stream (binary and unknown).

Also, regardless of people's objections to .obscure being too long for regular use, it should be a valid file extension for application/obscure files. Kind of like how .htm is a valid file extension for a HTML file- it's just slightly shorter.

50_scratch_tabs wrote:

BigNate469 wrote:

(#370)
As I mentioned (at some point) earlier in this topic, why not just ignore file type (for now), because it seems everyone here can't come to a consensus on it, and just look at MIME type?

I don't think there would be any dispute over application/obscure (although also accept text/plain), because as far as MIME types go, that's about medium sized. In addition, application/* is specifically for program and executable files, and application/octet-stream (binary and unknown).

Also, regardless of people's objections to .obscure being too long for regular use, it should be a valid file extension for application/obscure files. Kind of like how .htm is a valid file extension for a HTML file- it's just slightly shorter.

And how would this be stored for a file on your computer? I'm not entirely sure how mimetypes work with local files, and plus, there are many other scenarios where the server determines the mimetype by the file extension.

Could you please explain how mimetypes relate to this? I'm having trouble following.

BigNate469 wrote:

Also, Linux ignores file extension in general and only looks at MIME type to determine file type.

BigNate469 wrote:

50_scratch_tabs wrote:

BigNate469 wrote:

(#370)
As I mentioned (at some point) earlier in this topic, why not just ignore file type (for now), because it seems everyone here can't come to a consensus on it, and just look at MIME type?

I don't think there would be any dispute over application/obscure (although also accept text/plain), because as far as MIME types go, that's about medium sized. In addition, application/* is specifically for program and executable files, and application/octet-stream (binary and unknown).

Also, regardless of people's objections to .obscure being too long for regular use, it should be a valid file extension for application/obscure files. Kind of like how .htm is a valid file extension for a HTML file- it's just slightly shorter.

And how would this be stored for a file on your computer? I'm not entirely sure how mimetypes work with local files, and plus, there are many other scenarios where the server determines the mimetype by the file extension.

Could you please explain how mimetypes relate to this? I'm having trouble following.

All files have a MIME type; what it is tells you the true type of the file. MIME type is not inherently linked to file extension.

Computers as a general rule don't care what a MIME type is, only that a file has one, and if it is familiar with it. Most computer would just say something along the lines of “this file is not supported” to any file with applications/obscure, but like most program files, changing the extension to .txt should let you open it. Also, Linux ignores file extension in general and only looks at MIME type to determine file type.

davidtheplatform wrote:

MIME types are generally not stored at all in a filesystem, they have to be guessed based on other things. Windows does this purely based on the file extension. Linux looks at other filesystem metadata and the content of the file to determine what type it is, but it still doesn't know the MIME type for sure because it isn't actually stored anywhere.

50_scratch_tabs wrote:

davidtheplatform wrote:

MIME types are generally not stored at all in a filesystem, they have to be guessed based on other things. Windows does this purely based on the file extension. Linux looks at other filesystem metadata and the content of the file to determine what type it is, but it still doesn't know the MIME type for sure because it isn't actually stored anywhere.

So do we have to convince Microsoft to add detection for Obscure scripts? Could you possibly clarify on how mimetypes are guessed?

BigNate469 wrote:

(#377)

And none of this actually matters on a browser (Obscure's editor is a webpage) where the server sends the MIME type with the file for the browser to easily identify it.

i_eat_coffee wrote:

(#379)
what should I add to the editor other than the AI assistant and syntax highlighting?

50_scratch_tabs wrote:

BigNate469 wrote:

(#377)

And none of this actually matters on a browser (Obscure's editor is a webpage) where the server sends the MIME type with the file for the browser to easily identify it.

Right but what about opening local files in the editor?