Either way, someone shared a much more minimal version [1] on my gist, which should be safe to use as long as you're not signing up for a Zendesk site. Most of the recent spam emails have been about Zendesk sign-ups specifically.

I just didn't want to keep maintaining this script if they find some other way to exploit Zendesk in the future, hence my nuclear approach.

[1]: https://gist.github.com/hampuskraft/780c8fbcc4042689153533ef...

[1]: https://gist.github.com/hampuskraft/780c8fbcc4042689153533ef...

I suspect the recipient email address they're using (which I don't share widely) might have been exposed in one of Discord's recent support breaches, because I can't work out where else they could've got it from.

I'm using Proton Mail, so I set up a Sieve filter [1]. I'm doing this because this email address isn't used for anything even remotely related to Zendesk. I mostly use a separate custom domain address for everything.

[1]: https://gist.github.com/hampuskraft/7325ba2ad23a9445ebd93c64...

I'm Hampus Kraft [1], a 22-year-old software developer nearing completion of my BSc in Computer Engineering at KTH Royal Institute of Technology in Sweden. I've been working on Fluxer on and off for about 5 years, but recently decided to work on it full-time and see how far it could take me.

Fluxer is an open source [2] communication platform for friends, groups, and communities (text, voice, and video). It aims for "modern chat app" feature coverage with a familiar UX, while being developed in the open and staying FOSS (AGPLv3). The codebase is largely written in TypeScript and Erlang.

Try it now (no email or password required): https://fluxer.gg/fluxer-hq – this creates an "unclaimed account" (date of birth only) so you can explore the platform. Unclaimed accounts can create/join communities but have some limitations. You can claim your account with email + password later if you want.

I've developed this solo, with limited capital from some early supporters and testers. Please keep this in mind if you find what I offer today lacking; I know it is! I'm sharing this now to find contributors and early supporters who want to help shape this into the chat app you actually want.

~~~

Fluxer is not currently end-to-end encrypted, nor is it decentralised or federated. I'm open to implementing E2EE and federation in the future, but they're complex features, and I didn't want to end up like other community chat apps [3] that get criticised for broken core functionality and missing expected features while chasing those goals.

I'm most confident on the backend and web app, so that's where I've focused. After some frustrating attempts with React Native, I'm sticking with a mobile PWA for now (including push notification support) while looking into Skip [4] for a true native app. If someone with more experience in native dev has any thoughts, let me know!

Many tech-related communities that would benefit from not locking information into walled gardens still choose Discord or Slack over forum software because of the convenience these platforms bring, a choice that is often criticised [5][6][7]. I will not only work on adding forums and threads, but also enable opt-in publishing of forums to the open web, including RSS/Atom feeds, to give you the best of both worlds.

~~~

I don't intend to license any part of the software under anything but the AGPLv3, limit the number of messages [8], or have an SSO tax [9]. Business-oriented features like SSO will be prioritised on the roadmap with your support. You'd only pay for support and optionally for sponsored features or fixes you'd like prioritised. I don't currently plan on SaaS, but I'm open to support and maintenance contracts.

~~~

I want Fluxer to become an easy-to-deploy, fully FOSS Discord/Slack-like platform for companies, communities, and individuals who want to own their chat infrastructure, or who wish to support an independent and bootstrapped hosted alternative. But I need early adopters and financial support to keep working on it full-time.

I'm also very interested in code contributors since this is a challenging project to work on solo. My email is hampus@fluxer.app.

~~~

There’s a lot more to be said; I’ll be around in the comments to answer questions and fix things quickly if you run into issues. Thank you, and wishing you all the best in the new year!

[1] https://www.linkedin.com/in/hampuskraft

[2] https://github.com/fluxerapp/fluxer

[3] https://news.ycombinator.com/item?id=46376201

[4] https://skip.tools/

[5] https://news.ycombinator.com/item?id=40533484

[6] https://news.ycombinator.com/item?id=37502258

[7] https://news.ycombinator.com/item?id=39569843

[8] https://news.ycombinator.com/item?id=46383675

[9] https://sso.tax/

Comments URL: https://news.ycombinator.com/item?id=46468725

Points: 11

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=43424644

Points: 5

# Comments: 0

[1]: https://www.fastmail.com/company/about/

Comments URL: https://news.ycombinator.com/item?id=43347908

Points: 3

# Comments: 0

If you'd like to delete your Discord messages en masse, I made an open-source tool for that [2]. It leverages a fairly undocumented process using your Discord data package, providing a UI to explore it and choose what to export. The tool gives you step-by-step instructions and a CSV file that Discord expects when you contact their privacy team. It works across all channels in both servers and DMs, even those you no longer have access to.

[1]: https://news.ycombinator.com/item?id=43276504

[2]: https://discorch.org

[1]: https://discorch.org

[1] https://discord.com/servers [2] https://discord.com/blog/maxjourney-pushing-discords-limits-...

Comments URL: https://news.ycombinator.com/item?id=42829063

Points: 1

# Comments: 0

Discord's bulk deletion process is complex and poorly documented. With their recent push toward monetization and ads, users need better tools to control their data. Discorch makes this accessible by guiding you through the process step by step, with a simple and intuitive interface.

Includes a Go CLI for attachment downloads. Search functionality needs improvement and there are some known bugs, but it works well for most use cases. Issues and PRs welcome at https://codeberg.org/discorch/discorch.

I'll keep an eye on the comments for feedback and bug reports!

Comments URL: https://news.ycombinator.com/item?id=42744138

Points: 11

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42574902

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42306463

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42304758

Points: 21

# Comments: 4

Comments URL: https://news.ycombinator.com/item?id=42299141

Points: 6

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=42216436

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=42198635

Points: 153

# Comments: 35

Comments URL: https://news.ycombinator.com/item?id=42196197

Points: 3

# Comments: 0