Engineer and coder that likes memes.

  • 1 Post
  • 59 Comments
Joined 2 years ago
cake
Cake day: July 29th, 2023

help-circle

  • I guess we just have to agree to disagree then. Which is fine.

    Your points are valid and thank you for detailing them for me. If I was in their shoes making others able to steal my IP, even if they’re not allowed due to licensing and having to deal with constant scrutiny of the source code are k.o.-criteria, which hinder the project and lead to potential revenue loss.





  • That’s a bit naive imho. Remaining closed source is a form of IP protection and that’s really ok for what Obsidian is (a markdown editor). There’s just not any benefit for them other than appreciation from FOSS enthusiasts. Also maintaining an open source repository causes a higher workload and they lose a lot of freedom.

    If privacy is your concern you don’t need source code anyway. It’s quite easy to sandbox an application like that and analyse network traffic and such. Also Obsidian is built using Electron. That means with enough motivation one could quite easily reverse engineer most of the app. Most of the applications behaviour can also be observed via the integrated dev console, which lets you view source code.

    In short I don’t really see the need, unless I want to build or maintain it myself. And I think the negatives far outweigh the positives from the perspective of Obsidians team.


  • I don’t necessarily like a few takes in the comments here.

    Vibes wise the Obsidian team seems to be great and they don’t seem to have shown any reason why I should distrust them. I love FOSS but gifting others my work doesn’t put food on my table, so in that sense they need to have a lucrative business model which they seem to have established.

    I could use SyncThing, Git or other solutions to do synchronisation between my devices but I choose to buy their Sync offer, since I want to support them (they also have EU servers, which need to be GDPR compliant by law afaik).

    The closest comparison I could make is NextCloud. NextCloud open sources their software, but they sell convenience. Sure, you could self host it, but paying them to do so for you may be more attractive. In comparison Obsidian is not really complicated to set up or maintain. It’s literally just a MD-editor. So the only convenient thing to sell is synchronisation if you don’t want to put a price tag on the software.

    If they open source all their code, some tech wizard will implement a self hosted obsidian sync server with the same convenience as theirs in a day, and the company will lose their revenue stream.

    We’ve all been burned by tech bros in one way or another, but I think it’s ok for people to profit off of their IP. And they seem to be doing so with a positive vision. Feel free to let me eat my words if they ever go rogue, but that’s my 2 cents.





  • prof@infosec.pubtoScience Memes@mander.xyzGRINDSET MINDSET
    link
    fedilink
    English
    arrow-up
    24
    ·
    2 months ago

    Yes, because the hard thing about writing papers is the actual writing.

    Jokes aside, of course I can just write whatever, but if I don’t have any actual research to write about, all of those 4000 words I write a day are just filler that will get deleted after someone remotely intelligent reviews it.

    Academia is not fun 😂







  • My point is sematics.

    You can style your whole webpage with divs, but using main, nav, footer or whatever blocks is semantically more correct, because you group elements together that have a certain purpose.

    A HTML Tag in the middle of a sentence is not wrong per se, but when parsing it a line break could signify two sentences where one has missing punctuation, instead of a complete sentence as your original intention was.

    I don’t really care how the design you want is achieved to be honest, but I don’t get why the prof didn’t argue against.


  • Oh boy.

    We had a class in the first semester of uni where we had to create a static html page based on a screenshot.

    There was this one textbox at the top of the site, where the only way you could recreate the screenshot was by using a <br> in the middle of the text.

    The prof was very picky about your HTML being semantically thorough and correct, so that was super weird that that was necessary.