* add native ios code outside of ios project
* helper script
* going to be a lot of these commits to squash...backing up
* save
* start of an expo plugin
* create info.plist
* copy the view controller
* maybe working
* working
* wait working now
* working plugin
* use current scheme
* update intent path
* use better params
* support text in uri
* build
* use better encoding
* handle images
* cleanup ios plugin
* android
* move bash script to /scripts
* handle cases where loaded data is uiimage rather than uri
* remove unnecessary logic, allow more than 4 images and just take first 4
* android build plugin
* limit images to four on android
* use js for plugins, no need to build
* revert changes to app config
* use correct scheme on android
* android readme
* move ios extension to /modules
* remove unnecessary event
* revert typo
* plugin readme
* scripts readme
* add configurable scheme to .env, default to `bluesky`
* remove debug
* revert .gitignore change
* add comment about updating .env to app.config.js for those modifying scheme
* modify .env
* update android module to use the proper url
* update ios extension
* remove comment
* parse and validate incoming image uris
* fix types
* rm oops
* fix a few typos
* Show tabbar on desktop
* Make bottom border always 1px
* Don't hide/show navbar when switching tabs
* two rows WIP
* Top bar tweaks
* Make scroll adjustement native-only
* Add new web scroll behavior
* Fix translations
* Handle loooong words
* Truncate on desktop web, revert mobile changes
* Break the words
* Small enough for mobile web
* Fix alignment on mobile web
* Clarify
* Add bare minimum hashtags support (#2804)
* Add bare minimum hashtags support
As atproto/api already parses hashtags, this is as simple as hooking it
up like link segments.
This is "bare minimum" because:
- Opening hashtag "#foo" is actually just a search for "foo" right now
to work around #2491.
- There is no integration in the composer. This hasn't stopped people
from using hashtags already, and can be added later.
- This change itself only had to hook things up - thank you for having
already put the hashtag parsing in place.
* Remove workaround for hash search not working now that it's fixed
* Add RichTextTag and TagMenu
* Sketch
* Remove hackfix
* Some cleanup
* Sketch web
* Mobile design
* Mobile handling of tags search
* Web only
* Fix navigation woes
* Use new callback
* Hook it up
* Integrate muted tags
* Fix dropdown styles
* Type error
* Use close callback
* Fix styles
* Cleanup, install latest sdk
* Quick muted words screen
* Targets
* Dir structure
* Icons, list view
* Move to dialog
* Add removal confirmation
* Swap copy
* Improve checkboxees
* Update matching, add tests
* Moderate embeds
* Create global dialogs concept again to prevent flashing
* Add access from moderation screen
* Highlight tags on native
* Add web highlighting
* Add close to web modal
* Adjust close color
* Rename toggles and adjust logic
* Icon update
* Load states
* Improve regex
* Improve regex
* Improve regex
* Revert link test
* Hyphenated words
* Improve matching
* Enhance
* Some tweaks
* Muted words modal changes
* Handle invalid handles, handle long tags
* Remove main regex
* Better test
* Space/punct check drop to includes
* Lowercase post text before comparison
* Add better real world test case
---------
Co-authored-by: Kisaragi Hiu <mail@kisaragi-hiu.com>
* Make dim color scheme dim
* Tweaks
* Overall tweaks
* We have to go darker
* Tweak saturation of blues in dim
* Increase contrast on dark-dark mode
* adjust dim
---------
Co-authored-by: Eric Bailey <git@esb.lol>
Co-authored-by: Paul Frazee <pfrazee@gmail.com>
Co-authored-by: Hailey <me@haileyok.com>
* show uiState errors in the box as well
simplify copy
update ui for only letters and numbers
add ui validation to handle selection
* simplify names
* Fix accidental text-node render
---------
Co-authored-by: Paul Frazee <pfrazee@gmail.com>
* Move home-related files to view/com/home
* Add HomeHeader in front of FeedTabBar
* Move isDekstop check outside FeedsTabBar
* Remove PWI logic from tabbar
* Separate platform-specific layout from shared logic
* Switch to new RT
* Allow early exit from links
* Build in tracking to text atoms
* Clean up FeedSourceCard
* Clean up leading after new default
* Add deprecated notice
* web height adjustment
border radius incase of dark/dim mismatch
rm country codes
adjust height
general form refactor
more form refactor
refactor form submission
activity indicator after finished
remove remaining phone stuff
adjust captcha height
adjust state to reflect switch
move handle to the second step
pass color scheme param
ts
ts
update state when captcha is complete
web views and callbacks
remove old state
allow specified hosts
replace phone verification with a webview
* remove log
* height adjustment
* few changes
* use the correct url
* remove some debug
* validate handle before continuing
* explicitly check if there is a did, dont rely on error
* rm throw
* update allowed hosts
* update redirect host for webview
* fix handle
* fix handle check
* adjust height for full challenge
* Reveal parents in chunks to fix scroll jumps
Co-authored-by: Hailey <me@haileyok.com>
* Prevent layout jump when navigating to QT due to missing metrics
---------
Co-authored-by: Hailey <me@haileyok.com>
* Split skeleton gen into replies and parents
Co-authored-by: Hailey <me@haileyok.com>
* Move REPLY_PROMPT out of the generator
* Move the rest of visual logic out of gen
---------
Co-authored-by: Hailey <me@haileyok.com>
* move `IconCircle` to `components` for reuse
* add copy to feeds page
* start of a header
* saveit
* add lg size
* add your feeds
* don't show Your Feeds if you don't have any
* Minor ui tweaks
* cleanup
* remove unused activity indicator
---------
Co-authored-by: Paul Frazee <pfrazee@gmail.com>
* basic export repository link in settings
Absolutely no prior React experience, and limited TypeScript, so
probably doing all kinds of things wrong!
I tried to make it a download button instead of link but that didn't
work.
There is probably a safer way to construct the URL string.
I think having the download open in the browser is reasonable, as
opposed to an in-app save flow in mobile. But i'm not sure.
* Remove appview proxy toggle
* Move Settings screen to a subfolder
* Add support for the download attribute on links in web
* Rewrite ExportRepository modal using ALF
* Mobile ui tweaks
---------
Co-authored-by: Paul Frazee <pfrazee@gmail.com>
