Republican tech elites like Peter Thiel were once enticed by the prospect that Trump would usher in a new, ultra-capitalist era of Republican politics. Now they’re adrift.
Tech heavyweights who helped ignite Trump’s candidacy have told close associates they feel alienated from the GOP and are casting about for a candidate who more closely aligns with their extreme pro-business agenda.
Non-paywall: https://archive.ph/LLAMY
“Everyone, the anti-trans attacks didn’t work out for Virginia. Get out the dart board, let’s try this again.”
Completely agree! Gnome is nice but never been able to move past KDE if I had to pick a full blown DE.
The really weird part was this:
The amendment's language is dangerously vague and unconstrained, and can be weaponized to attack parental rights or defend rapists, pedophiles, and human traffickers.
I mean I know that they love to mix things together, but this might be the first time I’ve seen abortion linked to pedophilia and supporting rapists.
Just as an aside, donating does not have to be monetary. Helping (if possible) with development, triaging issues or helping with support/forums of any kind, along with in general filing good issues goes miles for FOSS projects, especially larger ones with only a few developers.
Serious thanks for all of your hard work, as well as everyone else working on Lemmy through software of running instances.
Memmy is ready 👍
PayPal is notorious for displaying meaningless errors for just about everything, even when it is intentional. Might not be the case here, but they definitely do things like this.
Though if I had to put my money on it, if it isn’t a bug it’s an anti fraud measure of some sort.
Another word on a more upbeat topic.
First, I have a Giphy implementation in the works to add to Memmy. In terms of privacy, I have taken steps to mitigate tracking that comes along with the use of a Meta product while also helping to allow users to communicate with more than just text.
Giphy has a SDK already made for React Native. Unfortunately, it has some “analytics” wrapped in. The API itself can be used without those analytics, but that comes at the cost of the almost certain tracking they do with just the searches and your IP.
As a result, this is what I came up with:
- You submit a search for a GIF (think Discord’s GIF search
- The request is sent to a Memmy server which then processes the request for you
- You receive a response with both the direct URL to each of the GIF results as well as a proxy URL. All of the results are displayed to you through the proxy.
- When you select a GIF, the direct link is added to your post or comment as an image embed.
- In a future update, there are plans for Lemmy to offer built in proxying of images. Hopefully this will be available soon. However if it is not, for 30 minutes the GIF you added to the comment will continue to be proxied through Memmy so as not to create an immediate link to you creating the request for the image.
This is somewhat similar to the Signal implementation of Giphy some time ago. I’m focused on cleaning up some other issues right now, but I’d like to add this in sometime in the near future. Will keep you posted.
A sincere thank you for the kind words :)
As I mention above, the second half of this message is not intended for the vast majority of users. And even for the users it is geared toward, it isn’t meant to be rude at all but to be informative.
I completely get how easy it is to forget that large projects are often times the result of a handful of people all with their own daily lives to deal with. I’ve run into a number of projects recently that have absolutely blown my mind when it comes to the difference in the size of the team vs the size of the product.
There were some issues over the past week with logins.
I migrated from storing JWTs in the app’s file system to using the iOS Keychain to store them. This prevents - mainly for users with jailbreaks - other applications being able to access tokens.
The issue was caused by the iOS Keychain not being updated whenever the JWT was changed. So, if you signed into an account that already had an existing but invalid JWT, it would have not removed and overwritten the old one. This is fixed now along with ensuring that Memmy operates fine with 0.19. (Version 1.1.4, still waiting on Apple to approve the App Store release).
Now, this isn’t for 99 percent of you, but yet it still needs to be said. I have said before and will continue to say: I am a single person (Sean has his own obligations) working on this right now. It has consumed a lot of time, and that is fine to me. However I also have life commitments.
I totally understand that if the app is not functioning that you are going to migrate - at least temporarily - to another app. That’s fine. I would do the same. What is not helpful is rude comments or store. You’re more than welcome to bring up issues or leave reviews on the store (I do get notified of them) but doing so with “doesn’t work, devs can’t even be bothered to….” provides me with absolutely nothing to work off of.
This issue is a perfect example of that. There have been a handful of people who were unable to sign in for a few days now (more than I know of, I am sure). Of those people, a number either made comments here (and I do apologize for not reading those, please read below) or have left negative reviews without information. I was left to speculate about the issue and assume it was fixed and the user was just using an old version. It was not until today that someone reached out to me over email with details about the issue that I was able to pin it down and fix it.
I am extremely grateful for the people who have either created GitHub issues or emailed me directly with logs and information. I’ve had interactions with a number of you over the past few weeks that have been great, and that is what open source software is all about.
It should be noted too that - as of right now - this community is mainly used for me being able to make an announcement easily. I do not have the time to monitor this community however. If you directly reply to me or message me I’ll get the notification, but I do not pay attention to posts. If you have a question, it is much more helpful to send me an email (along with the debug log) or open an issue on GitHub.
Know that this isn’t just a request for myself. I’m asking you to treat every developer working on Lemmy. related projects, or frankly any open source software with the same respect. I’ve seen numerous times on this site (and frankly this was something that made me want to take a step away for a moment) rude remarks and negativity made towards developers. It isn’t constructive at all and is the opposite of the energy that we as a community should be putting out.
Please, all I ask is that we be respectful in both directions. As long as the community continues to be great I have no issue at all putting time into this. And outside of just myself and Memmy, the only way this community will continue to thrive and grow is if everyone is treated with that respect.
Remember, too, that Lemmy in terms of size and Memmy in terms of existence have only been around for mere months. Nothing comes perfect out of the box. Lemmy is still - I think we can agree - in its early stages. So is Memmy and the rest of the applications out there. What should be remembered is that the next wave of people is bound to come at some point. Your help in development can make that transition easier than it was for you, whether it be help toward me, toward Voyager or Avelon or the other available options, to the instances, or to the Lemmy devs themselves.
Thank you all. Long live Lemmy 💪(fuck /u/spez)
Should be fine now. (Assuming that you’re on TestFlight. Waiting for Apple for the App Store.
I am a single person working on this right now. I am totally fine with you using whichever app you need to use, and I understand that if it wasn’t working for you that you’re going to switch. I have my own life commitments as well that I have to make, and managing issues through email, GitHub, and Lemmy is not feasible in the slightest.
That said, these issues are fixed now. If you want to update and use it, that’s great. If you prefer voyager that is fine too.
Absolutely one of my favorite games when I was a kid.
Wow, a whopping 100k from Shopify, that’s awesome!
Oh for sure. I’m just glad they keep doing this harmless shit. But, the scary thing is that the more they escalate and see it doesn’t work, the more they will keep escalating.
High praise to all the people working the elections these days ❤️
Don’t understand what these people think would be accomplished by sending the stuff in the mail like that. Touching it isn’t going to do anything. Inhaling I supposed, but it would be rather difficult to accidentally inhale it especially after being packed during mailing.
Funny, I’m on the shitter after some tacos right now. This one was a false alarm I think though. Will be back in an hour or so.
Is putting a ! infront of a markdown link not standard for an image? That’s why it’s doing it.
Lemmy does use some different markdown formats than I have usually seen, so maybe it’s not a standard just the common thing.
Edit: oh you meant the other way around. Anyway, weird that Reddit used that for links.
With how much those things cost, I wouldn’t be surprised if some horseshoe crab blood was mixed in to really make the color pop.
Howdy all! Hopefully you are doing well.
It has been quite some time since the last update, and for that I do apologize. Both personal commitments and just the need to take a step back have had both Sean and I not really working much on the app. However, here is some news from Memmy.
The initial releases of Memmy taught me a lot about React Native. Making an app this feature filled is fairly difficult, and it grew quickly and fell apart in a lot of areas. Seeing all of those short comings, I have gone ahead and addressed them from the ground up.
The number one issue was the UI framework that was in use. Somehow, the arguably most used UI framework for React Native had exceptionally terrible performance. That has now been completely removed from Memmy. What we are working with now produces renders in within 2ms of base React Native components.
Additionally, the state has been completely reworked. No longer should there be any real issues there. I’ve taken care to try and make sure there is only one source of truth for posts and comments as well as making sure proper memoization is being used.
Swipe gestures can be fully customized now, so feel free to do whatever setup you want.
I have some code ready to test for push notifications again. Originally, I disabled them because of rate limit issues at the request of Lemmy.world. I’ll make sure I’m still in the clear, but I was given some numbers to work with before that I think will work fine.
The community drawer can be opened from anywhere in the app by pressing and holding on the home icon now. Double tapping will refresh the feed. Small stuff, but highly requested.
Drafts get stored for everything. You can start replying to a comment, close out and reply to another one, then go back to the first. Your changes will be waiting for you.
There are other changes all over the place that should really just make performance light years better. There are sleek animations now as well on community and profile views, and loading is no longer “jarring”. Animations and fade ins are used throughout the app for all loading of data.
There’s some more stuff to implement but I anticipate having something up on the store by the middle of next week. I’ve submitted something to TestFlight for approval already, so if you are still in there you can download that.
I should note that there are no plans at all to monetize Memmy. No advertisements, paywalls for features, etc. frankly, I am happy to bite the small bill for push notifications if it comes to it. The intention is just to make an environment that you all can easily use.
Feel free to come back to memmy if you left, or stay where you’re at. As long as you’re happily using Lemmy in general that’s all that really matters :)
Cheers!
Hey guys! Sorry for being AWOL for the past few days. I’ve been taking some personal time and stepped away for a bit. Going to be cleaning up some more stuff and pushing out some good stuff to you guys soon.
This build here - for real this time - offers significant performance enhancements. There is more to be done, but this is a great start.
Here’s some changes:
- Hide username in the tab bar
- Some context menu refactors
- Add bug report option
- We have replaced the old UI library with a new one. There are still some quirks to work out, and we will be handling those over the next few days. This offers quite a significant performance boost over the last library.
- Using more stable variables to prevent unnecessary re-renders. This is one part of the performance improvements.
- Fix infinite refreshing attempts of an empty community
- Added option to delete posts. This was something I threw in tonight and will be finishing edit post tomorrow. I also have the mod tools ready to go, just a matter of adding them where they need to be in the menus
- Comment chains are collapsed after either the first 4 2nd level comments or after 3 replies to a 2nd level comment. Much easier to scroll through comments now. This is a WIP so there might be issues. Let us know.
- Added a comment jump button. Speaks for itself. Might have some issues and is still a WIP. Let us know if anything goes wrong
- Should have fixed a few crashes that were getting reported while I was away.
Again, sorry for the downtime. I’ll be more active over the next week and we should see some big stuff.
As the title says. Features are now available on TestFlight. Apple should approve the release on Monday, so let's hope that happens and it's available everywhere. Cheers.
Edit: Noticed a problem with the marking as read. Fixed now and I'll update here shortly.
Hey all!
It may have seemed to be a slow week, but I have been toiling rewriting a significant portion of the codebase while staring at graphs so that we can better implement new features. Currently, the state management was a bit too spread out, so I have taken the time to centralize that. This is going to make things like mod tools a cinch to integrate, and I plan to do that this coming week (seriously).
These changes should also provide some pretty good performance enhancements. To be sure, this is not a complete effort yet, however I have overhauled the two biggest things: feeds and posts/comments. These are the two biggest performance bottlenecks, and I think I’ve gotten about 80% of the way there in improving the performance there. Still more work to do though!
Additionally, we should see another significant performance boost in the next portion of the rewrite, which will remove off the current UI library that we use and replace it with a much better performing library. That is a process that will happen over time.
The great news is that now, we should be able to iterate at a higher speed with these changes, and we should be rolling out some big changes here in the next few days!
For now, there are a few changes - and things that should be fixed because of this rewrite
- I keep saying this, but I have a feeling that this should resolve some NSFW issues
- I also keep saying this, but I am pretty certain that this should fix the issues with language ID issues. At least for posts, comments should be fixed in a day or so.
- The profile screen has been reworked
- Much better (but still lacking, and this will improve further in the coming days) performance with the traverse
As this is a rewrite of a lot of state things, there is a chance that some things might have broken. However, I have done a good bit of testing here and think things are alright. If you see anything funky, please do let us know!
We do plan (and should be able to do so more easily now) have some tab bar options that will allow you to customize the functions there. For example, you will be able to visit the traverse tab from a button on the tab bar if you wish to swap it out with another one.
Like I said, this coming week will be more feature-full rather than behind the scenes work. Thanks for hanging in there while we get this stuff sorted out!
Cheers!
Hey all!
I am doing a rewrite right now of the state management so that we can scale a lot better. This is going to allow for a super seamless integration of mod tools as well as other integrations throughout the app.
I am aware of some issues with the drawer right now, especially whenever a user has a large number of subscriptions. We are working on clearing that up.
I'm also aware of some performance issues, especially on older devices. Two things are being done to correct this:
- Better state management
- Stripping out one of the UI libraries that is used and replacing it with either another library or raw React Native components.
These will probably be done by the end of the week. I think these are two things that are super important to knock out now to keep things scalable. I'm learning here as we move along, and am fixing things up as I see issues arise 👍
Thanks for all the feedback, and know that some absolutely great things are coming your way very soon! Cheers
Hey all!
This should be available sometime later in the day. Huge thanks for a few new contributors - @joshua-davis-rose and @bohn002 - for putting in a lot of work as well.
- Subscriptions now available in a drawer instead of "Traverse". More of an Apollo-esque style
- Switch accounts by pressing and holding the profile button. Feed header now allows you to select Local/All/Subscriptions
- Continuing to improve image viewer
- Saving images and sharing images now uses the cached files to share, so you don't need to re-download them
- Alphabetized subscription list
- Community about screen now shows moderators
- You can swipe back using anywhere in the tab bar (I've been experimenting with full-screen swipe back as well, once I get that ironed out a bit more we will add that too)
- UI now uses the iOS 14+ dropdowns for context menus
- Cleaned up some issues with longer community names, but there are still more to handle. Keep an eye out.
- Subscriber count is now in the community search
- All NSFW image issues should be fixed
- Lots of performance enhancements around the app
- Also lots of bug fixes, especially for a few newly discovered crashes
Please be sure to report any issues to the GitHub if you can. It is much easier to track there than it is here. There's a lot of traffic, so it's hard to keep track of all of it!
Stay tuned for more coming throughout the week!
Edit: Want to make this a sugestion thread, so please let us know your ideas on themes or names below.
Howdy all!
We have been internally discussing a rebranding of Memmy to another name. This has been a discussion for some time, and although we have certainly tried to see the upsides of not rebranding, we don't think this is a viable long-term option, for - among others - the following reasons:
- Eventual support for non-Lemmy services such as Kbin or Mastodon
- User awareness of Lemmy. Right now, the vast majority of people who are finding the app most likely are specifically searching for "Lemmy". While that's great and (based on trends on downloads/day) shows that there's obviously a big demand for Lemmy, we think this might not be the best way to grow - not just for ourselves but for Lemmy as a whole. We want the fediverse to grow and the best way to do that is to make it acceptable and easy to access without specifically targeting people who already know about Lemmy
- Community feedback in general about the name. None of this is taken personal or anything, but there's definitely negative feedback for multiple reasons about it, and honestly I think we agree with most - if not all - of that feedback.
Like I said, this is not something that we are doing lightly and we want to make sure we make the right choice before moving forward.
Mind you, we are not talking about a short-term goal here of supporting multiple Fediverse platforms. That probably isn't even in the one-year plan if I'm being honest. But I personally believe the way that we make the Fediverse work is by making the whole experience awesome, and that means offering users with options and ease-of-use.
So, with that said, we want to see what you guys think. We have had internal discussion about the possibility of using the name Badger, and while we all think that's a pretty good option, we are not 100% sold and want to gauge feedback before we do anything. Edit: It seems like that might not be something the community is interested in, so we likely won't be going that route.
Please drop your suggestions for themes or names below! We will go through them all sometime later in the day.
Let us know your thoughts!
Coming to the App Store tomorrow!
Hey all! We still have some more QOL updates coming tomorrow or Saturday. Working on getting comments all sorted up (more like the Apollo style) and getting post editing/deletion as well as mod tools underway.
This update provides a VAST improvement to the image viewer. There shouldn't be any more issues with the swiping to close.
There are some issues still but they are minor and I'll get them cleaned up here soon. I've spent the day writing this viewer from scratch, so it's been a process.
The "white flash of death" should be fixed here as well when you open up the app.
We also now support localization! German is officially supported now, and we will be sourcing other languages to improve the experience for everyone.
Other minor fixes as well in this build, including a fix for a crash that was happening with the new spoilers.
Stay tuned, and happy scrolling!
Over night I had a LOT of reports come in about a crash. I have fixed these issues and this version is now live on both the App Store and TestFlight.
Please keep sending that information in! Thanks!
There is currently something going on over at Lemmy.world causing authentication issues. This isn't a memmy specific issue but is also plaguing the PWA. https://lemmy.world/post/1364490
Until this is fixed, the best bet it to just keep "retrying". This would explain some of the issues I thought were linked to issues inside the app but might be something else.
I have an update ready that will fix a bunch of these internal issues with the app, but unfortunately it's going to break Lemmy.world terribly for anyone using it, so I'm going to hold off on releasing that until they figure out what is going on.
App store version is up.
If you are on Lemmy.world, you need to update your JWT token. Sorry, this was not intuitive and there is no proper error message. This is my fault and we seriously just never got around to this.
Please go to "Manage Accounts" and then tap your Lemmy.world account. Hit "Edit Account", enter your password, then hit save. You should be back up and running.
Note
This information is based off of early reports I have seen. I don't claim to know the extent to which any damage was done and as such recommend a password reset (two-factor authentication would not be of use if authentication tokens were compromised), but we do know that this was a Javascript injection.
Update
As of right now, it seems that the vulnerability should have only exposed JWTs, which have been invalidated by those instance administrators. I'd still recommend a password rotation just because, but you should be alright.
==========
With the recent Lemmy.world incident, I'd like to update you all. This vulnerability could not have affected you had you been using only Memmy while browsing. It was a Javascript injection, and as Memmy does not execute any Javascript, there is no attack surface here.
The only case where this could have affected you would be if you had been signed in to your account inside of the in-app browser or the default browser and opened one of these posts. That however would not be something with Memmy itself, but rather the accessing of the PWA.
Regardless, as we don't actually know what happened, I'd recommend changing passwords. If any JWTs were compromised during this, regardless of 2FA status these tokens could be used to authenticate with your account.
From what I have seen, this was an issue that was limited to Lemmy.world, as supposedly they were running a custom frontend build. Other than that, I don't know anything else.
Also, for the record, there is only one instance in this application where a webview is used, which is when viewing the terms of service which simply loads a local file from the app assets.
Any questions, I'll try to answer them but you'd be better off asking people more knowledgeable about the incident.
As always, this is a good time to go over your online security practices.
It is strongly recommended that you use a password manager such as Bitwarden or 1Password if you do not use one already. This can help prevent credential surfing if you have used the same password over many sites, preventing you from having several of your accounts breached from a single breach.
If you have used a password on Lemmy.world that you have used on other sites, you should change those other sites passwords immediately.
Email addresses may have been breached during the attack and this may result in increased spam and phishing emails. It is strongly advised that you throughly verify any emails that you receive after this, particularly ones relating to login requests, messages from banks or payment providers, such as PayPal or government institutions.
Thank you for using Memmy and stay safe!
Hey all. A serious family medical emergency came up today. I do not really know how it's going to turn out right now, so you might not see as much from me for a few days. The release to the App Store is still in process, we are just waiting for a review from Apple, this will not affect that.
If it goes on for a bit, I will make sure that Sean knows how to process a build and release to TestFlight and subsequently to the App Store. I am hopeful that things will turn out alright but it's a pretty scary situation and I'm honestly not sure.
I'll be around in the evenings and will do a bit of work, but I likely will not be reading or replying to anything here. Your feedback will still be monitored and we will be going over that. Additionally, for bug reports, I highly recommend opening an issue on GitHub. It is incredibly easier to read and follow issues opened there. Things here are quickly buried and hard to find.
Thanks for all the support
In order to get up to speed with the people that are coming here without TestFlight, I've submitted a build to Apple with all of the current features and fixes.
I'd anticipate this to take about 24 hours, but it's possible it will be reviewed today. Apple is weird. I've had things get approved in like 8 hours on Saturdays before, so there's a chance it will happen today. I'll update you all when that happens.
Improvements and additions:
- New icon and options for changing icon color
- New and improved swipe animation (by the way, this is better than the last update wink)
- Improvements to image viewer (double tap works now too)
- Performance enhancments throughout the app
- Hide read posts
- Images in comments
- Collapsible posts
- Default comment sort
- All of the "Top" sort options
- Show a loading modal while downloading images
- Added a manage accounts button to accounts dropdown
- Add option for reader in webview
- Settings improvements
- Added embark theme
- Added buttons in comments for upvoting and replying
- Adjustments to splashscreen
- Username doesn't link to user profile in compact mode now
- Add option to use the default browser instead of in-app browser
Fixes:
- Fix issues with toast not changing color or disappearing
- Fix cake day showing the wrong year
- Fix issue where links with an internal IP address would ask for permission to local network
- Fix issues with account disappearing after app launch
- Read icon now uses the correct color
- Fix crash caused when pressing Matrix links
- Fix crash when searching for a community with an @ at the end
If any of these issues are bothering you now, rest assured they will be fixed for you quite soon.
Edit: Other features that were not on the list:
- Hide read posts (with a button)
- Collapsible posts
- Images in comments
- Default comment sort
- All of the "Top" sort options
- Fixed issues with askign for local permissions: See these commits for what caused this: https://github.com/Memmy-App/memmy/commit/5a1ed47fd92f76c6b0931e4b2e5700584ee469d8 https://github.com/Memmy-App/memmy/commit/cdf9421e4955f7c93af0e750612e9db3dc4d6c61
Hey all!
For all of the testers, we have submitted a 0.1 build to TestFlight that needs to get approved. These usually only take a few hours unlike a full store release which usually takes 12-24 hours, so expect that here soon.
First, let me detail what is already fixed in the current TestFlight version and will be in the next store release:
- Sharing images inside of the image viewer will now download the image to be shared as an image, not as a link
- Link helper respects the theme and uses the URL keyboard for the link
- The post viewport should respect keyboard height and fill the remainder of the space
- Read icon now uses the correct theme/accent color (thanks ktgd)
- All /c/community links should now work (thanks ktgd)
- The last account you used is now remembered (thanks jderose)
- Search will automatically take you to the community or user if you include the @instance
- All refresh controls will respect the theme (no longer invisible)
- Added top hour, top six hours, and top twelve hours (I need to add them to defaults, I’ll do that here in a bit)
- Fixed image save/share not being present in compact mode
- Made sure that images that are both present in the URL and in the body of the post don’t show up twice
- Profile reload issues (i.e. if it fails to load) should be fixed
- Link info not displaying in posts is now fixed
- Blur respects the current theme
- Voting on a post in search now reflects that vote
- Modifications to the profile screen. This will help with load times when all you’re doing is looking at someone’s profile
- Performance improvements in the feed
- Performance improvements in comments
- Collapsing large comment chains no longer causes freeze/crash
- Performance improvements in profile
- Performance improvements in inbox
Here are the things being addressed that will be making their way into 0.1 TestFlight builds and should be available on the store either on Friday or Saturday:
- New swipe animation. Much improved, more performant, and without the visual bugs we have right now
- Error reporting. You'll get actual error messages now instead of the generic error codes Lemmy sends
- Markdown enhancements. Pictures in comments should be there, and more than one image in a post will be shown
- Editing or deleting a post
- Improvements to image viewer. I cannot PROMISE that swiping through images (like a gallery) will be there but I CAN promise that there shouldn't be any further issues with swipe to dismiss or issues with swiping to close some images
- Also, iPad users shouldn't have issues with viewing images in landscape mode anymore
- Other improvements (I'll list them as we add them)
- Other bug fixes (Same thing, I will list them as I add them)
Things to note:
I've seen some issues with subscriptions not showing up in the Traverse screen. I think this is a server issue, but I will verify that to be sure. I am experiencing this on Lemmy.ml and I think others are experiencing it on Lemm.ee. I wonder if a recent update (lemmy.ml seems to have updated) caused this. I also noticed that my upvote count on the profile has changed, not sure what that might be because of...
For issues, I strongly suggest reporting them on GitHub: https://github.com/memmy-app/memmy
While Sean and I do try to go through posts here, it's MUCH more difficult than it is on GitHub. We have an internal issue tracker that syncs with GitHub that we use to triage and develop roadmaps. It's hard to do that with posts here.
Thanks for all of the INCREDIBLE support over the past day from you guys!