• 8 Posts
  • 44 Comments
Joined 6 months ago
cake
Cake day: September 2nd, 2024

help-circle




  • i literally have to spell everything out

    Yes. You do. That’s just the way it goes.

    It doesn’t matter if you’re doing OSS or looking for venture capital, you need to sell your project/product to users. In an OSS project, prospective users need to understand why they should invest their time. You always need an elevator pitch or one liner. In github, the elevator pitch is the “About” section on the right hand side of the page (on desktop).

    If you want to see what a good sales job looks like for Open Source, check out hoarder. It’s one of the best I’ve seen and certainly one of the main reasons it has received over 13 thousand stars in about one year.







  • tkw8@lemm.eetoPrivacy@lemmy.mlHow to harden fennec for privacy?
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    2 months ago

    Does anyone know about the team in this project? I’m concerned that development stalls after a little while when things get hard or they get tired of it.

    For me, customizing a new browser is a heavy lift so I don’t usually jump headfirst into browsers without first knowing a little about the team’s background.









  • I appreciate your effort here & the screenshots. Unfortunately, this isn’t what I was looking for. This just imports a “dumb” feed and doesn’t actually integrate with the API. Integrating with FreshRSS’ API, (the app OP mentioned), allows the RSS reader to interoperate with the FreshRSS application. For example, if I read an article on my mobile device, it will be marked as read on FreshRSS. So if I later pull up my feed on Newsboat (on my linux machine) or Readrops (my android tablet), those same articles won’t be presented to me again. Also, if I’ve made any customizations regarding my home feed in FreshRSS those will also be reflected in these other RSS Readers. That’s why the API is the preferred way to connect to these other readers.

    I just didn’t see a place for a user/API key input within feeeed.





  • … plans emerged last week when the Australian Signals Directorate (ASD) published guidance for High Assurance Cryptographic Equipment (HACE) – devices that send and/or receive sensitive information – that calls for disallowing the cryptographic algorithms SHA-256, RSA, ECDSA and ECDH, among others, by the end of this decade.

    With regard to the algorithms used to hash data – particularly SHA-224 and SHA-256 – Buchanan expressed surprise that neither will be approved for use beyond 2030.

    “The migration within five years will not be easy, as every single web connection currently uses ECDH and RSA/ECDSA,” he wrote. “These methods are also used for many other parts of a secure infrastructure.”

    Looks like we could be in for interesting times.