Yeah, it’s only an aggregator that then points you to the original content. For legal reasons, I don’t think OpenSourcely would be able to host the original content natively.
Building a better web for all of us: hiram.io
Yeah, it’s only an aggregator that then points you to the original content. For legal reasons, I don’t think OpenSourcely would be able to host the original content natively.
I started a website called OpenSourcely to do exactly this.
It aggregates news, projects, and announcements related to open source.
I’m always on the lookout for new RSS feeds and outlets to add to it, so if anyone has any, feel free to send them my way.
This is why enshittification might be a good thing ¯_(ツ)_/¯
Canva.
Their feature set and functionality is great, but their vendor lock-in is really off-putting. Even just within their platform, it’s really difficult to move assets around within workspaces.
Let alone edit graphics that you made on Canva and edit them elsewhere, say Penpot, for example.
Selena - No Me Queda Más
Arctic Monkeys - 505
Eminem - Headlights
GnR - November Rain
Nope. I suppose in theory it could, but not necessarily—it’d be up to Apple/Google to make the color decisions regarding that.
The important thing here is that it’s not about the colors themselves, but about what the colors signify.
Apple chose blue to denote that the message you’re sending is to another Apple device. By default, this Apple-to-Apple message uses the iMessage protocol. If it uses iMessage, then that implies a certain security standard.
Apple also made the deliberate choice to denote non-iMessage texts with green. If it’s green, then it’s SMS/MMS, you lose iMessage encryption, and other features like reactions.
The colors are not gonna change by default—it’s up to them to coordinate what colors are used for what. Apple’s not gonna open up iMessage (at least not voluntarily, and we saw how far they’ll go with Beeper), so Google can’t do anything about that. Which is also why they’re pushing so hard to get Apple to adopt RCS.
If Apple does adopt RCS, maybe they’ll denote it with purple bubbles, who knows. Then you’d have iMessage as blue, RCS as purple, and SMS/MMS as green.
But again, this is all about what each color signifies in terms of privacy and security.
The thing is… The bubble colors do matter. But people aren’t caring about the colors for the right reasons.
The color matters because the color has to do with the security of that message.
Sending a message through the iMessage protocol is more secure than SMS/MMS.
People should care that their messages are secure and private (and they do care, they just don’t always realize it or know it yet). Unfortunately, the people behind the whole blue vs. green bubble culture war don’t seem to focus on this security aspect, which is actually what/why it matters.
As an Apple investor who would benefit from more iPhone sales, “Buy an iPhone” is not the right response/solution to this problem, despite what Tim Apple says.
Choose open source. Say no to walled gardens.
Use—and donate to—Signal.
Greetings from GrapheneOS, as a former iOS and stock Android user.
Any benefit over just downloading the APK directly without managing it through Obtanium? I ask cause I’m guessing that for Mull, since there are no releases on its GitLab repo, it’ll just have to be downloaded directly.
I use Obtanium too, but I can’t figure out how to install apps that are hosted on GitLab.
What do you have to change in Obtanium?
Here’s Mull, for example: https://gitlab.com/divested-mobile/mull-fenix
Daily:
Not daily:
I may not be fully understanding your use case, but Baserow has forms and is API-first. It sounds like it would do it, if I’m understanding correctly.
It’s open source and has both hosted and self-hosted versions.
Disclaimer: I’m part of the Baserow team.
How did you pull Mull into Obtanium? When I paste the GitLab URL into Obtanium, it says that there’s no APK found.
Should be required reading IMO for anyone ever ~on Github :P~
Fixed.
For some people it’s easy, for others it isn’t, and/or they’re afraid of messing it up.
This is the secondary reason why I created SwapMyOS, a GrapheneOS installation service that kicks back a percentage of every order to the GrapheneOS nonprofit to keep it funded.
Primary reason was to keep GrapheneOS alive and funded.
Risk it for the biscuit
Maybe a good idea for a blog post, but the general gist is this:
The messages will get delivered to your Mac, and then forwarded to your phone via AirMessage or BlueBubbles.
Signal for everything.
There are a couple people who are too lazy to get Signal, and they got iPhones, so I set up an iMessage server to forward messages to my GrapheneOS phone.
But the communication there is extremely sparse and surface level. It’s basically just a touch point. The real conversations all go through Signal.
I would if I could, but I built it without writing code. So there’s nothing to upload to GitHub/GitLab.
The page asking for your email simply serves as the delivery mechanism since I can’t put it on GitHub/GitLab.
A rip in the multiverse. Source: trust me bro