Research
Security News
Malicious npm Package Targets Solana Developers and Hijacks Funds
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
club.minnced:discord-webhooks
Advanced tools
Provides easy to use bindings for the Discord Webhook API
Originally part of JDA, this library provides easy to use bindings for the Discord Webhook API.
Here we will give a small overview of the proper usage and applicability of the resources provided by this library.
Documentation is available via the GitHub pages on this repository: Javadoc
Webhooks on discord are only capable of sending messages, nothing more. For anything else you either have to use OAuth2 or a bot account. This library does not provide any functionality for creating or modifying webhooks.
The first thing to do is to create either a WebhookClient
or a WebhookCluster
. The WebhookClient
provides functionality to send messages to one webhook based on either a webhook URL or the ID and token of a webhook. It implements automatic rate-limit handling and can be configured to use a shared thread-pool.
// Using the builder
WebhookClientBuilder builder = new WebhookClientBuilder(url); // or id, token
builder.setThreadFactory((job) -> {
Thread thread = new Thread(job);
thread.setName("Hello");
thread.setDaemon(true);
return thread;
});
builder.setWait(true);
WebhookClient client = builder.build();
// Using the factory methods
WebhookClient client = WebhookClient.withUrl(url); // or withId(id, token)
// Create and initialize the cluster
WebhookCluster cluster = new WebhookCluster(5); // create an initial 5 slots (dynamic like lists)
cluster.setDefaultHttpClient(new OkHttpClient());
cluster.setDefaultDaemon(true);
// Create a webhook client
cluster.buildWebhook(id, token);
// Add an existing webhook client
cluster.addWebhook(client);
Sending messages happens in a background thread (configured through the pool/factory) and thus is async by default. To access the message you have to enable the wait
mechanic (enabled by default). With this you can use the callbacks provided by CompletableFuture<ReadonlyMessage>
.
// Send and forget
client.send("Hello World");
// Send and log (using embed)
WebhookEmbed embed = new WebhookEmbedBuilder()
.setColor(0xFF00EE)
.setDescription("Hello World")
.build();
client.send(embed)
.thenAccept((message) -> System.out.printf("Message with embed has been sent [%s]%n", message.getId()));
// Change appearance of webhook message
WebhookMessage message = new WebhookMessageBuilder()
.setUsername("Minn") // use this username
.setAvatarUrl(avatarUrl) // use this avatar
.setContent("Hello World")
.build();
client.send(message);
You can use the webhook clients provided by this library to send messages in threads. There are two ways to accomplish this.
Set a thread id in the client builder to send all messages in that client to the thread:
WebhookClient client = new WebhookClientBuilder(url)
.setThreadId(threadId)
.build();
client.send("Hello"); // appears in the thread
Use onThread
to create a client with a thread id and all other settings inherited:
try (WebhookClient client = WebhookClient.withUrl(url)) {
WebhookClient thread = client.onThread(123L);
thread.send("Hello"); // appears only in the thread with id 123
client.send("Friend"); // appears in the channel instead
} // calls client.close() which automatically also closes all onThread clients as well.
All WebhookClient
instances created with onThread
will share the same thread pool used by the original client. This means that shutting down or closing any of the clients will also close all other clients associated with that underlying thread pool.
WebhookClient thread = null;
try (WebhookClient client = WebhookClient.withUrl(url)) {
thread = client.onThread(id);
} // closes client
thread.send("Hello"); // <- throws rejected execution due to pool being shutdown by client.close() above ^
WebhookClient client = WebhookClient.withUrl(url);
try (WebhookClient thread = client.onThread(id)) {
thread.send("...");
} // closes thread
client.send("Hello"); // <- throws rejected execution due to pool being shutdown by thread.close() above ^
Since the clients use threads for sending messages you should close the client to end the threads. This can be ignored if a shared thread-pool is used between multiple clients but that pool has to be shutdown by the user accordingly.
try (WebhookClient client = WebhookClient.withUrl(url)) {
client.send("Hello World");
} // client.close() automated
webhookCluster.close(); // closes each client and can be used again
By default, this library will log every exception encountered when sending a message using the SLF4J logger implementation. This can be configured using WebhookClient#setErrorHandler to custom behavior per client or WebhookClient#setDefaultErrorHandler for all clients.
WebhookClient.setDefaultErrorHandler((client, message, throwable) -> {
System.err.printf("[%s] %s%n", client.getId(), message);
if (throwable != null)
throwable.printStackTrace();
// Shutdown the webhook client when you get 404 response (may also trigger for client#edit calls, be careful)
if (throwable instanceof HttpException ex && ex.getCode() == 404) {
client.close();
}
});
This library also supports sending webhook messages with integration from other libraries such as
public void sendWebhook(Webhook webhook) {
MessageCreateData message = new MessageCreateBuilder().setContent("Hello World").build();
try (JDAWebhookClient client = JDAWebhookClient.from(webhook)) { // create a client instance from the JDA webhook
client.send(message); // send a JDA message instance
}
}
public void sendWebhook(Webhook webhook) {
try (D4JWebhookClient client = D4JWebhookClient.from(webhook)) {
client.send(MessageCreateSpec.create()
.withContent("Hello World")
.addFile("cat.png", new FileInputStream("cat.png"))
);
}
}
Note: Replace %VERSION%
below with the desired version.
repositories {
mavenCentral()
}
dependencies {
implementation("club.minnced:discord-webhooks:%VERSION%")
}
<dependency>
<groupId>club.minnced</groupId>
<artifactId>discord-webhooks</artifactId>
<version>%VERSION%</version>
</dependency>
gradlew shadowJar
-all.jar
in build/libs
class MyAppender extends AppenderBase<LoggingEvent> {
private final WebhookClient client;
@Override
protected void append(LoggingEvent eventObject) {
if (client == null)
return;
WebhookEmbedBuilder builder = new WebhookEmbedBuilder();
builder.setDescription(eventObject.getFormattedMessage());
int color = -1;
switch (eventObject.getLevel().toInt()) {
case ERROR_INT:
color = 0xFF0000;
break;
case INFO_INT:
color = 0xF8F8FF;
break;
}
if (color > 0)
builder.setColor(color);
builder.setTimestamp(Instant.ofEpochMilli(eventObject.getTimeStamp()));
client.send(builder.build());
}
}
This is an example implementation of an Appender for logback-classic
FAQs
Unknown package
We found that club.minnced:discord-webhooks demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.