MonkderVierte

cross-posted from: https://lemmy.zip/post/66082776

I never see in public git projects something like a declaration of scope. There's also no convention, unlike a README.md (which rarely contains some sort of scope definition) or LICENSE file.

Is this unusual in open source projects, that you first define what you want and not want in your project and how you want to do it, to combat scope creep and sabotaging yourself?

I'm in a postition in live (short of a burnout) where it's actively a pain to just start things and then wing it; i even add a scope comment to larger shell scripts.
Maybe it's experience, because i already know that i'm then not satisfied afterward or (in case of shell scripts) just create a unfinished mess. Nobody else?

cross-posted from: https://lemmy.zip/post/66082776

I never see in public git projects something like a declaration of scope. There's also no convention, unlike a README.md (which rarely contains some sort of scope definition) or LICENSE file.

Is this unusual in open source projects, that you first define what you want and not want in your project and how you want to do it, to combat scope creep and sabotaging yourself?

I'm in a postition in live (short of a burnout) where it's actively a pain to just start things and then wing it; i even add a scope comment to larger shell scripts.
Maybe it's experience, because i already know that i'm then not satisfied afterward or (in case of shell scripts) just create a unfinished mess. Nobody else?

I never see in public git projects something like a declaration of scope. There's also no convention, unlike a README.md (which rarely contains some sort of scope definition) or LICENSE file.

Is this unusual in open source projects, that you first define what you want and not want in your project and how you want to do it, to combat scope creep and sabotaging yourself?

I'm in a postition in live (short of a burnout) where it's actively a pain to just start things and then wing it; i even add a scope comment to larger shell scripts.
Maybe it's experience, because i already know that i'm then not satisfied afterward or (in case of shell scripts) just create a unfinished mess.

Nobody else? Or am i looking for the wrong term?

cross-posted from: https://lemmy.zip/post/65977452

Has anyone attempted to use controlled browning via cut & bent paper/allu foil masks to create art on buns (especially pretzel)?

I have this image laying around...

Has anyone attempted to use controlled browning via cut & bent paper/allu foil masks to create art on buns (especially pretzel)?

I have this image laying around...

I've got a marketing@ unsubscribe mail from a certain service, with the unsub link going over jcabjd.r..bh.d.sendibt3.com. Firefox refuses a cookie for invalid domain, the unsubscribe does only work in Chrome.
Looking this up, whois refuses my request, but the site who.is says, the Nameservers are cloudflare ones, with all contact info being REDACTED FOR PRIVACY.

In short, is this domain safe? And why can public companies' entries be redacted for privacy?

slow in performance (short-lived bursty TCP connections) if it was ever used to transfer resource heavy HTML pages.

https://en.wikipedia.org/wiki/Gemini_(protocol)#Reception

Well duh. A bicycle is also overloaded and cumbersome, if it was ever used as a car.

Edit: to clarify, the whole point of the gemini web is to avoid heavy and complex site layouts. Automatic embedding and stuff just doesn't happen there. Also doesn't use HTML but Gemtext. So, short-lived and bursty connections, are a ideal fit.

Please add a comma to your short options (-o, --option). This makes it easier to look it up.

Just something i wanted Linuxers to be aware of.

I want to write a reader for multiple lightweight markup languages. It must only support pretty basic "rich text" features (bold, indent, lists, such things), complicated formatting and not-matching tags will be entirely ignored.

I don't want to use a intermediate markup like pandoc does, since it should not convert but only display.
Which is why i thought of using a "mapping file" for each language. Guess it should support hierarchies, since formats like Markdown require context (prior line has this and next line that), so it will likely be in YAML/TOML/JSON.

Is this sufficient, or is there any better approach for simple addition of markup languages?
Or other projects doing similiar, i could learn from?

The context is a simple mbox/eml reader for a start (html and markdown), and the experience/ideas will be used in a bigger project later, with more language support.

This is why i like webshops, for the info and sorting they provide and hate them for the need to compare, eating my day to save me from a bad experience.