The kahla from aiursoftweb

Prevent the API response AES key and max lifetime if the user did not join the group

Access media file in SDK.

Send file via:

Local path
Stream
Internet path

SomeoneLeftEvent typo

Kahla/Kahla.Server/Events/KahlaEvent.cs

Line 14 in 71a4ca7

SomeoneLeftLevent = 6,

If you use any character in the middle of a nickname, it's not necessarily, but most of it, you can use AT instead of that nickname.

Can not add a user after deleting him

After deleting a friend, the sentRequest value of that user is true but should be false.

Global search enable emails search.

Save bot HTTP service cookies to files to maintain login status.

Send the contributor and Email if he reports other.

Build more robots.

We are planning to build more robots. 😋

Kahla security robot which tells you your account sign-in alerts and Kahla upgrade notes.
The weather robot which tells your current weather and weather alert.
Earthquake robot that alarms you incoming earthquake.
Alarm robot that wakes you up at a specified time.
A more powerful translate robot can translate from any source to any language.
Chat robot which can sell 萌.
Google robot which can help you google your question and give you the result.
Wikipedia robot which returns you definition on Wikipedia.
...

Any more advice? Or we gonna work on those interesting robots! 🤖🤖🤖 Long live robot!

Use JWT to maintain users' status.

Handle invalid subscription exception and delete it

At here.

Group name length limitation is not working

Creating a group with three whitespaces will cause the error -5, using one or two letters with whitespace will create group successfully.

Return if has request in the discover API

Describe the solution you'd like

When I wanna at everybody in a group I own, I have to I have to at each other.

Describe alternatives you've considered

If I am the owner of one group, I can at @all at once. When the client is calling API, for the ats part, add all members' ID.

Additional context

Nothing.

Invalid Operation exception when trying to delete one device using multi threads.

Allow saving and getting theme settings.

Make `RequestSent` from `SentRequest` true if the target user sent me a request.

Make RequestSent from SentRequest true if the target user sent me a request.

Move the check version API to Kahla home.

Auto reconnect to stargate for bot.

Mute conversations

Disable notification
Not count the unread number

Move the following code to another independent controller.

https://github.com/AiursoftWeb/Kahla/blob/master/Kahla.Server/Controllers/AuthController.cs#L256-L357

The code has no relationship with authentication. And it makes the auth controller works slow.

Move it away to another controller calls DevicesController.

Don't forget to delete any useless dependency injections.

Don't push notification if the conversation is muted

Multi thread sending notification.

Support friend or group suggestion

Support blocking a conversation.

Cannot send friend request again.

In UserDetail

Kahla/Kahla.Server/Controllers/FriendshipController.cs

Line 320 in 6b436dd

    
           model.SentRequest = _dbContext.Requests.Any(t => t.TargetId == target.Id && t.CreatorId == user.Id);

But in CreateRequest

Kahla/Kahla.Server/Controllers/FriendshipController.cs

Lines 121 to 124 in 6b436dd

    
           var pending = _dbContext.Requests 
        
               .Where(t => t.CreatorId == user.Id) 
        
               .Where(t => t.TargetId == id) 
        
               .Any(t => !t.Completed);

Supports offset in getMessage API

Add a parameter offset in getMessage API, it can be the message id. And take parameter can be negative. For example: getMessage(10, 12, -15) will get 15 messages before the message with id 12 in conversation 10. If offset is -1, it means the latest message.

Save bot settings to files. So when start there do not require input.

Rate limit friend request email notification

What do you suggest us to do?

In Kahla 3.6.0, email notification for pending friend requests would be sent frequently until the user accepts or rejects all of them.

If Kahla limits the email notification to once (or maybe once per month) for each request, users on vacation won't have their inbox spammed and the sending email address/domain is less likely to be blacklisted.

Current

NewFriendRequestEvent: only requestId
WereDeletedEvent: nothing
FriendAcceptedEvent: nothing

TODO

Friend's id, email, nickName

	var pending = _dbContext.Requests
	.Where(t => t.CreatorId == user.Id)
	.Where(t => t.TargetId == id)
	.Any(t => !t.Completed);

aiursoftweb / kahla Goto Github PK

kahla's People

Contributors

Stargazers

Watchers

Forkers

kahla's Issues

Describe the solution you'd like

Describe alternatives you've considered

Additional context

What do you suggest us to do?

Current

TODO

Recommend Projects

Recommend Topics

Recommend Org