A Minimalist Blogger, Website Developer and Privacy Enthusiast.

Proud to Be a FOSS User.

Settled on Fedora Workstation.

Heavy Reader.

Enjoy coding and learn by mistakes.

Extremely Introverted Individual Who Prefers Solitude.

  • 20 Posts
  • 45 Comments
Joined 10 months ago
cake
Cake day: December 9th, 2025

help-circle





  • I use ghostwriter to write blogs in markdown. Then with the help of a converter i convert it into html format and modify it from there.

    Why not directly write in HTML?

    Because for me writing blogs in direct html feels so hard for several reasons,

    • Adding tags every-time affects my writing flow.
    • Markdown is so simple compared to HTML and ghostwriter shows a direct live preview on the side.
    • Markdown to HTML converters work so well by converting the markdown symbols into proper HTML tag.

    But why I may switch?

    I would consider to switch to directly writing blogs in HTML when i have enough knowledge about web development. The reasons are,

    • It is harder to correct or tweak lines of converted HTML, when compared to directly written HTML.
    • Converters are not perfect either, they make mistakes when identifying equivalent tags. Then later it will become a headache to review again and again.
    • Later we have to implement CSS and class by reading each line of converted HTML, which actually doubles the effort.
    • If I learned HTML, CSS and JavaScript well, and get comfort with it, then there is no need to write in Markdown format, use Hugo/Zola, find a good pre-built theme and keep it from breaking, etc. HTML, CSS, JavaScript manages itself everything.
    • Managing our own website and writing blogs in it is actually very interesting and exciting than writing blogs in someones else’s template/theme. (No matter we get viewers or not).

    I recommend directly writing on HTML rather than Markdown to reduce the effort needed.

    Thank you for the resources. It looks very helpful.








  • Sideloading MV2 Extensions, doesn’t seems to work. If it’s a MV2 extension, then no need to sideload, can install directly from web store.

    Vivaldi supports custom filterlists, but way less effective than even MV2 extensions. No cosmetic, network filtering like uBlock Origin does. Am saying so because vivaldi ad-blocker is not a brand new feature. It’s there for a longer time, but without any improvemrnts on it’s blocking rate or privacy things also.

    Another thing is browser fingerprint, there is not a single way to harden vivaldi at all. Every data like operating system, timezone, canvas, audio, etc. can be easily fingerprinted. I used NoScript to atleast block third-party scripts but after blocking/unblocking a site in noscript webpage didn’t auto reload like in other browsers. We have to manually does it.

    The web pannel, speed dials and customizations are standing out features, but those alone can’t be a reason to choose a browser in modern web. Vivaldi lags very behind in privacy and security wise.







  • First of all, avoid giving your mobile number on instagram. It is a very unique identity to identify you. Firefox private browsing mode alone won’t help you but browser/profile isolation can be a better solution.

    keep in mind that your privacy is not only in your control but other people who saved your number on their phone with real name, other services you used before or the isp iself can sell this data to data brokers. If you used whatsapp with this same number, then that’s too a reason behind this.

    Furthermore, device fingerprinting, browser fingerprinting, network fingerprinting, etc. pose significant drawbacks in privacy on platforms like instagram.