kaiteki-fedi / kaiteki Goto Github PK

• Text interpolation with variables

Blocks

• Text
• Counter
  • Custom increment value
• If
• Compose note (#54)
• Section
• Images
• Text area
• Canvas
• Button
• Choice
• Text input
  • Multiline
• Numeric input
• Switch

Variables

• Values
  • Text
  • Text (multiline)
  • Text list
  • Number
  • Variables
  • Functions
• Flow control
  • Branch
  • Repeat
• Logical operation
  • NOT
  • OR
  • AND
• Computation
  • Add
  • Subtract
  • Multiply
  • Divide
  • Remainder
  • Round
• Comparison
  • Greater than (gt)

Feature

A title bar that blends into the app, similar to Discord and so on.

Design sketch

N/A

Resources

https://pub.dev/packages/bitsdojo_window

The goal of this issue is to remove irrelevant features that were implemented, so they can be implemented properly at a later date.

Cut out code should be put inside a non-compiled directory so they can be looked at if they need to in future.

Things to remove

• Theming menu
• Chats
• Notifications

• Initial implementation
  • Pleroma
  • Misskey
• Proper design

Future thought

Kaiteki can store 2FA secrets and fill out challenges automatically at the convienience of the user.

• Reduce animations like animated images (reducing widget rebuilds)

Currently the classes inside fediverse_objects are handwritten, generated from JSON strings.
There should be a GitHub action/tool that automates code generation (optionally with original documentation from the APIs itself). The tool should be able to fetch the most recent API specifications from each platform and regenerate classes.

Wanted features

• Code generation
  • Automatic nullable (?) declaration
  • Automatic dartdoc comments ///
  • Automatic imports
  • Automatic constructor
    • Automatic required declaration
  • Automatic json_serializable methods (Class.fromJson(), Class.toJson())
• Enhancements
  • Exclude objects
  • Apply different settings for certain objects
  • Hints for properties (e.g. array property is missing information what type its items have)
  • Support for generating files out of pure JSON files (not OpenAPI)
• Applied to
  • fo/misskey
  • fo/pleroma
  • fo/mastodon

• User Interface
  • Fluent version of Kaiteki's icon
• #397

Prerequisites

• Translation input (2 possible ways)
  • Translators have a GitHub account, work on a JSON file and push changes directly.
  • Crowdsourcing translation instance, like Weblate, for users to work on translation strings.
    As translation plaform I recently started a Weblate instance: https://wl.craftplacer.moe/
• Automatic releases of translations
  • ... provided via GitHub Actions (weekly/monthly builds?)

Things to consider

• Use pre-existing strings from Pleroma
  • ask in advance and credit translators

Contains a list of threads that you want to watch and a notification count badge. Grouping of interactions would be a good idea too.

Feature

Some instances like Misskey (maybe Mastodon too) deliver BlurHash'es which can be used as temporary image or blurred version for NSFW posts.

Design sketch

N/A

Resources

• https://pub.dev/packages/flutter_blurhash
• https://pub.dev/packages/blurhash

That behavior is a bit undesirable as it makes the emoji illegible

Simulated responses should be integrated into the app for faster debugging and development.

(quality) make a better data structure to represent different backends.

Line: 52
https://github.com/Craftplacer/kaiteki/blob/1e02f69b8f96193734b8ece317452147239064aa/src/kaiteki/lib/constants.dart#L50-L57

Pushed by Craftplacer [email protected]

Feature

• Create a hidden developer mode
• Show tabs in the login screen that change between "Normal" and "Token"

Design sketch

N/A

Resources

N/A

It would be nice if there could be another shortcut (one icon for normal Fediverse, another one for chatting) to launch Kaiteki in "chatting-only" mode.
It will be a cut down version of the app experience just for chatting with people.

This would split the app into two modes, but under the same binary.

The question remaining if this is desirable for users, especially in daily use, and whether if the user has to switch between those two modes often.

• Follow endpoints implemented in adapters
  • Fetch current state (not following, request sent, following)
  • Being able to request a follow to someone
• Functioning UI
  • Display current state
  • Send follow request
  • Update itself
• Use providers to share state

• Only show up to 4 attachments
• Hint at more attachments (by displaying the amount of attachments that aren't shown)
• Hide sensitive attachments

design drafts

When compiling to web, it could be possible that server admins could adopt Kaiteki as their frontend, given if Kaiteki could run in a "single instance" mode.

Features would include locking the instance and backend type when adding a new account, to make it easier to login. Since this is a bit user unfriendly, another thought might be to advertise the standalone client, where users are free to choose their backend.

Providing a default app theme (that might include wallpaper) would be nice to, reminiscent to Pleroma-FE.

Windows build fails due to improper symbolic links.

The symbolic link should be a relative path, as in the following version.
https://github.com/Craftplacer/Kaiteki/blob/351bcdd72ae6f6f7cdfc1072080267a5aba0a0cf/src/kaiteki/windows/runner/resources/app_icon.ico

In the current version, it is an absolute path, which means that the file cannot be found outside of your environment.
https://github.com/Craftplacer/Kaiteki/blob/master/src/kaiteki/windows/runner/resources/app_icon.ico

I have just fixed session persistance for the latest Kaiteki builds. I still have fears of how the code interacts with each other not being the smartest or most elegant.

I would love to get a discussion going how to rewrite it so it's flexible / has less code smell.

The problem that I'll have is that the account manager (AccountContainer), Fediverse API clients (e.g. MastodonClient) and the secret data classes (AccountSecret and ClientSecret) will have to be rewritten or modified, which I did with a9197e7.

Describe the bug

ThemeContainer is initialized once with a set theme and does not update when the user changes theme.

• Replying
  • Display
  • Requests
  • Update
• Liking/Favoriting
  • Display
  • Requests
  • Update
• Repeating/Boosting
  • Display
  • Requests
  • Update
• Reacting
  • Display
  • Requests
  • Update

• Depends on #49
• Fetch from Misskey's Asset Store
• Dynamic values
  • Functions
  • Property references
  • Constant references
  • CSS parsing

• Customization menu in settings
  • Theme list
  • Theme customization
• Kaiteki/Material themes

When compiling to Linux, non-western text becomes unknown character boxes or straight up don't render at all.

This should be looked into.

Currently Kaiteki works with text in this way:

This primarily only works for backends like Mastodon and Pleroma who send off sanitized HTML for web clients. But instances Misskey do things client side so it might be favorable to make it smarter.

This new code structure should make it possible to parse more diverse text input.

Now since Flutter 2, null safety is advised to migrate to, currently it's not possible to some depedency constraints. Packages listed down below are ones that are outdated and still haven't migrated. This issue is for tracking.

packages left to migrate

• fediverse_objects

  • json_serializable (4.0.2) google/json_serializable.dart#821
  • build_runner (1.12.1) dart-lang/build#2996 (comment)
  • #90

• kaiteki

  • fediverse_objects
  • client_cookie (2.2.1) Repository dead
  • logger_flutter (0.7.1)
    • might throw out and substitute with custom code
  • json_serializable (4.0.2) google/json_serializable.dart#821
  • build_runner (1.12.1) dart-lang/build#2996 (comment)
  • #115

• Instance metadata
• Local instance ID <-> user@instance
• Sticker attachment IDs
• Profile pictures

• Mastodon-based
  • Fedibird
  • Glitch-soc
• Pleroma-based
  • #212
• Misskey-based
  • #196
  • #259
• GNU social
• Goldfish
  • They have like literally no API, only server-side frontend.

Relevant code:
https://github.com/Craftplacer/Kaiteki/blob/58d44d97c9a54671d2960e5e756c5bcfce18f9ec/src/kaiteki/lib/utils/text/text_renderer.dart#L135-L142

Feature

The user is capable what widgets/columns are visible to them. Some widgets might offer themselves to be columns itself (notifications, timeline, etc.)

Design sketch

For desktop mode, there could be a sort of designer settings menu:

Resources

Insert links to documentation, libraries and other pieces of information that might help us implement this feature.

The difference between AppBar and Scaffold background are too big

Shortcuts are taken from Twitter as a start:

Navigation

• Home g+h
• Notifications g+n
• Settings g+s
• Bookmarks g+b

Actions

• New postn
• Send post Ctrl+Enter
• Reply r
• Repeat t
• Like l
• Bookmark b

It makes more sense to remove Mastodon, Pleroma and Misskey prefixes from classes and instead call them like usual, while also importing their respective library dart files as pleroma; etc. making it possible to use pleroma.ChatMessage or similar.

google/json_serializable.dart#678 may cause issues and require hand-editing JSON generated files though.

The missing feedback of logging in to an instance is irritating many users, it should be fixed ASAP.

Feature

Use Windows' compositing APIs to make the application see-through with acrylic background.

Design sketch

Resources

https://pub.dev/packages/flutter_acrylic

Feature

A GIF button in the toolbar when writing a post that opens a little bottom sheet with GIF search.

Design sketch

N/A

Resources

https://tenor.com/gifapi/documentation
https://github.com/justkawal/tenor

• Depends on #49
• Fetch themes
  • ... offered by instance
  • ... offered by Volpeon's Pleroma theme repository
• Map Pleroma theme properties to Material
  • Background
  • Colors
  • Shadows
  • Advanced
  • Roundness
    • Buttons
    • Input fields
    • Checkbox
    • Avatar
    • Tooltip
    • Attachment
    • Chat messages

• PostScreen ➜ ComposeScreen
• ThemeContainer ➜ ThemeManager
• StatusWidget ➜ PostWidget

Scrolling across the timeline makes you encounter artifacts of a previous frame. The circumstances when this appears are unclear right now -- unproducable.

Flutter returns following console warning:

WebGL INVALID_OPERATION bindTexture object does not belong to this context

Originally reported by @[email protected]

Currently, tested on Linux, big images in small space have bad quality. Providing a FilterQuality value either makes it too sharp/pixelated or too blurry.

• #114
• Post form
• Select formatting (if applicable)
• Select emojis
• Attach files
  • Pick files
  • Upload files
• Select stickers (if applicable)
  • Upload them

You'll be able to have read-only access to instances, just by typing their domain, most functionality will be disabled.

While migrating API entities inside Kaiteki it became apparent that Mastodon and Pleroma do part ways heavily, Pleroma is missing what Mastodon has and vice versa.

The solution will be to copy Mastodon's current set of entities into the Pleroma namespace and apply changes accordingly (add/remove fields).

Problems that mixed entities show are that fields have mixed nullable-states. This situtation is already bad when the user is authenticated or not, or the instance missing information, etc.

Store which account the user last used

Line: 62
https://github.com/Craftplacer/kaiteki/blob/e98dd9217528da63fbbd92d9eb08643edc8f1544/src/kaiteki/lib/account_container.dart#L60-L67

Pushed by Craftplacer [email protected]