diodb VS lazyblorg

Perhaps: https://disclose.io/programs/

Hi, I want to make some experience with web pentesting and I wanted to take some small bug bounty programs from disclose.io/programs/ . But to be honest I am scared that maybe I will do something wrong and I will face legal consequences 😱 . I am scared that by making the report they will see that I exploited the bug too much and put them in danger or something like that. I heard about white hat hackers reporting vulnerabilities and facing legal action but they discovered them without a bug bounty program like in this case https://www.bleepingcomputer.com/news/security/ethical-hacker-exposes-magyar-telekom-vulnerabilities-faces-8-years-in-jail/ What is your opinion about this ?

2) https://disclose.io

Helped develop coordinated vulnerability disclosure frameworks to allow security researchers to report security issues in good faith

I would also suggest contacting https://disclose.io/ and your National CSIRT team and ask for help. Good luck :)

Yeh, these are the different orgs that run programs on behalf of companies. For a list of the orgs running programs there’s about 2,300 of those here (also open-source and a contact work in progress): https://github.com/disclose/diodb

Another method is used via Memacs filename module: it generates a text file with all files that start with a date- or time-stamp. This file can then be used for all sorts of workflows for retrieving files. For example, this is how I include images in my blog using lazyblorg and its "Smart tsfile Image File Search".

For my own Python tools, I wrote multiple naïve parsers myself (not following the usual lexical/syntactical parsing model from the books) in order to get something working. While my parsers are not considered general purpose parsers, they get the job done on my side. You might take a look at https://github.com/novoid/lazyblorg/blob/master/lib/orgparser.py for a dirty but fairly complex example. It's also using pypandoc as a fall-back for stuff I didn't parse on my own. It runs my static web blog generator.

Minimal preferred? Then lazyblorg might be an option, although it's just a works-for-me project with a few restrictions such as an empty line between different syntax elements like a paragraph and a list.

Between the first idea and the actual start of the implementation of lazyblorg there was a time span of several years. ;-)

My website is generated by lazyblorg which is using DuckDuckGo for searches. A query looks like that:

Shameless plug: I blog about Emacs but since I was too lazy to implement topic-specific feeds yet, you could add my general feed to get my Emacs-related articles as well. I'm sure that decent feed aggregators are able to filter for specific topics/words.

When your focus is "fast and easy creating a blog entry anywhere in my Org files" and you don't have special needs for JavaScript-foo, you might love https://github.com/novoid/lazyblorg which I built for https://karl-voit.at/

I've seen Weblorg, which is Native Elisp, but rewrites me to create a new file for each blog-post. Then there's Lazyblorg, but it's written in python, and also searches across all your .org files, not just a single one.

Therefore, I implemented my own (very naïve and nasty) Org parser for lazyblorg.