They claim to be independent https://www.newsdemon.com/independent-usenet-provider

It seems like a really interesting idea, but yea, reaching critical mass is hard. Having a module instead of a full rewrite would be too big indeed, but the module mentioned in the comments would be a better idea. Sadly having something even half as big as AO3 would be quite the effort to maintain.

Don’t even need the good looking tbh

Only within a relatively recent stretch of history, before that you only needed to pay for fancy stuff (think pyramids or castles or whatnot)

Oh, I forgot those were a thing. Ad blocking DNS does wonders

People can have more than one problem. Last time I checked, humans aren’t 2D. Or even if that’s the main reason the person went to therapy, perhaps they weren’t looking for a “how do I turn this frown upside down” solution, instead hoping to get some advice on how to better channel their frustrations, or gain clearer focus, or just to have someone to help sort out own thoughts. There can be many reasons.

Is the reason why I have a Gmail. It’s the same one I’ve had for a long time, last time I checked it, the unread emails count was past 9999. I wonder what Google thinks of me 🤔

A pigeon? How dare you! That’s almost as bad as calling someone an absolute walnut!

There’s a journalist that did a video walking down a hallway in one of the gov buildings in Washington. One office door after the next had a “I stand with Israel” sign

It’s like being psychology adjacent and having to double check which CBT do people mean

Are you really having a good time when the munchies hit but you’re out of snacc?

Oh, Monica is a FOSS site you can selfhost, hence my question. But an offline version is pretty neat, especially if it directly integrates with the device systems (e.g. notifications, calendar, etc).

How is it different from Monica? Just that it’s a mobile app?

Even if I was a *illionaire I’d rather gargle lava rocks than touch Oracle with a mile long pole

In any case, good luck with your project, I hope it turns out wonderful, and you get all the hype and support 😁

Thanks for elaborating. To me, it looks like you could definitely use an experienced dev-background person to help organise the project. For example, login is low priority imo - it’s not needed until you’re going into testing. And I mentioned the project being US-focused since I noticed stuff like eligible_1099 in the table design - not a thing outside the US.

Also, I’m working on a project for a non-profit, and as part of it I’m doing an audit trail functionality. Ended up thinking real hard over what’s PII you actually need. Turns out, don’t actually need to store phone numbers, for example. Makes life easier. And for data anonymisation - if someone makes a GDPR request, then the email gets replaced with a unique hash + @redacte.d, and the IP gets salted + hashed, so that the same IP is the same hash in all entries. This is to ensure continuity in the audit trail, plus if someone gets banned for DDoSing, then does a data redaction request, then tries to access again, they can still be blocked since their IP still matches the hash (same logic as to how passwords work). I’m mentioning it since that’s the kind of details that are worth thinking about - however, it’s deep down the rabbit hole of details.

Speaking of details, if you’re thinking of mobile, then there’s also the decision of app VS mobile-friendly site. If you want an app, then it’s worth swapping to React right now, since React Native (the framework for creating mobile apps) has a larger community and is more mature. If you’re OK not having a native mobile app, then go with whatever, have fun 😁

I asked about the MVP and day to day useage since that can inform you about what order to implement things. As mentioned above, having a login page is lower priority when starting a project. For example, if based on your knowledge and the feedback from existing cooperative(s) shows that the most heavily used functionality is ex. inventory tracking, then it’s worth building a good inventory tracking system first, and grow from there. Is also why I mentioned forking an existing project - is a huge project, and if you’re going at it solo, it’s gonna be painful.

But, there’s also alternative to forking - copy-paste. Just like artists use references, developers can also reference existing code. So, for example, I don’t know if you’ve seen this sheet (from this post) for additional info how people think co-ops should work, but it’s another piece of info to consider. Though it’s Java, you can still take high level structure or direct code inspiration from Adempiere, they’ve been around long enough to make a bunch of mistakes. There’s also a fork of Adempiere, Metasfresh, which is worth looking at re: how things work. Also Tryton, though that one’s in Python. Mentioning Tryton since it also uses the party approach, and has an architecture that’s worth considering: modularity. Essentially, having the core functionality that ties everything together, and a whole bunch of “modules” that each contain their own logic, SQL, etc.

Which brings me to my last point: it’s great to work on a new project, but learn from my mistakes - think of what it would be like to maintain in 6, 12, 24, 60 months. If you tightly couple everything, all things depend on all other things, the system is going to be fragile, hard to maintain, and less likely to be used. With your background I’m sure you’re already familiar with trying to update something someone else created in a way that doesn’t make sense to you.

So yea, basically, I’m trying to caution you to KISS (keep it simple silly), and not overcommit, lest your project ends up the same way my uncountable exciting startings have ended - in some random dusty git repo, untouched for years, too big or hard or no longer relevant to finish 😅

This looks interesting, though a mighty undertaking. Any reason why not take an existing project and fork it? Or even just an ERPNext module? Would help cover a bunch of potential issues rather than start from scratch. Alternatively, have you thought of what would the MVP be to test it out? That way won’t fall into the do-everything-now trap (been there, done that, don’t recommend). Also, it looks very US-centric, so not gonna ask about GDPR, data security, etc. Instead, re: FE - for prototyping, don’t need design, just functional HTML + forms. Or, can try and poke at some premade or quick-assemble templates. Have you thought about functional (not design) requirements for the user experience, AKA how you imagine the users of this would use it? That is, full day in the office VS checking it once-monthly VS yearly for taxes, etc.

removepaywall.com to the rescue

Pro tip: you know companies get branded shirts right? There are other companies that print/embroider them. And those companies do samples of blank shirts. Look for your local custom print shop 😉

TBF with sufficient force and/or velocity you can stab someone with a carrot. Would probably have to pick a softer spot, but still