You are not wrong. But there are things you can do to make a point. Make Reddit as a 2nd class citizen and drive people to lemmy, mastodon and the others. Like add posts with no comments, just relay bot, … Make it clear.

Same with GitHub, it’s mirror to my Gitea instance. You can see stuff but you have to move somewhere else to contribute and report issues. Not a terrible thing to use these proprietary services and yet make them 2nd class citizens.

I came here to say at least it’s not discord then I saw your comment. Yes, there s mattermost, matrix, IRC, … I am not installing Discord, I am not opening an account. I mean what s next? host your community in Skype?

I am curious why not docker? it s pretty convenient in my setup (docker compose + traefik). If I need to migrate it s really simple, if I am to nuke a service just bring it down and delete the path.

I use keepassxc + syncthing, super easy to setup and decentralized.

NextCloud is straight up unusable to me no matter how much resources I was throwing at it.

OpenCloud seems promising. I would definitely like to play with it a little. I would also like to check check how can I help with a thing or two there.

This seems like a similar story with matrix Synapse vs Dendrite.

All questions are welcome! By saying it’s intended to tech people earlier I meant if you know what are the different components of an HTTP query, then you know enough to use it.

The end goal is for me to give this my email creds, it will then monitor my email and when I get a match it’ll run the API call, right?

That’s not what I wanted to express. Not requesting your email credentials is an intended design decision (it’s more challenging also). Because personally, if I was a user, I wouldn’t feel comfortable giving my email credentials to a random website online. The alternative solution is to generate an email controlled by the website like I did.

So yeah, the intended use case isn’t to monitor your email address. But rather give you an email address that you can plug in an alerting system for example that would result in a webhook call (that would notify you on matrix or telegram, create a github issue, create Jira ticket,…).

I would use this for email -> matrix but I’d have to self host it. I’m sure others would use it if you had some built in API calls that less techy people could use.

Self hosting isn’t necessary if you don’t want to, you can already add your matrix webhook and generate a random email address you can use. You can configure your current gmail account for example to forward certain or all emails to that randomly generated address and that would trigger a webhook (matrix msg in our example). It involves an extra step (configuring gmail) at the benefit of not having to share your personal creds with a random website online (gossip).

I can provide an example on how to do that if you want to test that.

I do agree with you though on the second part, I will be adding some ready-to-use blocks for the most common services. That’s already a planned feature.

Do you allow users to matched regex from the email and use it the API Call?

For now, it matches on the From Address only (to avoid spamming the API), but it will be very easy to add another field to match on the content or subject of the email if you think it’s a worthy feature.

I have never heard of ActivePieces. I took 30 min now to review it and play with it.

From that alone, I can say:

• you can definitely achieve what gossip does using ActivePieces (in other words, Gossip covers a small subset of what ActivityPieces does if you want to create your email manually and plug it into what they call an IMAP Piece)
• Yep, Gossip is much lighter and reacts instantly thanks to golang concurrency constructs (it’s now running on a tiny VPS there are few jobs and it’s consuming 22MB of RAM, I will be able to keep it free and scale really really high without much struggle)
• Gossip is geared more towards tech people (if you can put together a curl query to cover your needs than you can do almost anything you want - trigger a telegram msg, matrix chat, create a Jira ticket, …)
• Gossip doesn’t handle any complex automations now, it simply connects an email it generates into a webhook you input (that seems to cover all the use cases I needed in my workplace)

The last example will be equivalent to the following curl:

curl -L \
  -X POST \
  -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer github_pat_xxxx" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/repos/idrissbellil/cryptomonitor/issues \
  -d '{"title":"Found a bug","body":"I'\''m having a problem with this.","assignees":["idrissbellil"]}'

Thanks for having a look!

Monitor my email and when I get one that matches the regex it’ll make an API call?

It’s this first one with a slight twist. It generates a random email for you rather than asking you to give your username & password (I don’t want to handle securing people’s usernames and emails at this stage). It makes an API call when the From Email matches the regex.

Example from demo:

URL: https://api.github.com/repos/idrissbellil/cryptomonitor/issues
Method: POST   (The HTTP Method: POST, GET, PUT, ..)
From Regex: .*  (only trigger the call given certain `From` emails so you it doesn't create a thousand tickets if somebody floods you with emails)
Payload: {"title":"{{ .Subject }}","body":"{{ .Body }}","assignees":["idrissbellil"]}  (the data part of the POST/PUT/even GET query - here you can re-use parts of the email you received like Subject, Body, To, From
Headers: {"Accept":"application/vnd.github+json","Authorization":"Bearer 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","X-GitHub-Api-Version":"2022-11-28"}