Oops, my bad. Clicked the wrong button and unwillingly let the spam in.
Sorry.
___
Replicant mailing list
Replicant@osuosl.org
https://lists.osuosl.org/mailman/listinfo/replicant
, dllud (both Replicant contributors) and
several people we met during the 37C3 or on the train going to it
converged to the same points and together we identified several
issues:
Replicant has not enough people:
- A diversity of profiles helps solving issues
Yes. That's the expected behaviour.
Forum and mailing list are independent and unconnected.
On 27/01/2023 20:04, J05HYYY via Replicant wrote:
> Hi,
>
> I responded to John R
> on the forum https://redmine.replicant.us/boards/15/topics/15942
>
> Then I checked my emails and saw that GNUtoo had
Hi Loïc,
Unfortunately the application deadline was on the 15th of December 2020
at 21:00 UTC as detailed on the call[1]. Although you sent a very
impressive resume, we cannot accept it. It would be unfair to all other
contenders that sent their application on time.
Regards,
dllud
[1] https
This is an application to Community Manager Call.
Alexey first contacted us through the blog:
https://blog.replicant.us/2020/12/call-for-a-community-manager/#comments
On 08/12/2020 10:22, Alex Ivanov wrote:
> Hello. My name is Alexey and I live in Russia. I really like free
> software and its
Hi Paul,
Thanks for the tip. I actually knew about FOSSjobs and perhaps others in
the Replicant community knew about it too.
We purposefully opted to post the "Call for a community manager" just in
Replicant channels (blog, mailing list, IRC and forum) because that
helps narrow things down to
/platform_hardware_libhardware
https://github.com/anbox/platform_hardware_libhardware_legacy
https://github.com/anbox/platform_system_core
https://github.com/anbox/platform_system_netd
https://github.com/anbox/platform_system_vold
https://github.com/anbox/device_anbox
I took a quick look at the
graphics thanks to the Lima
driver. That will help a lot with the user experience.
Regards,
dllud
On 28/07/2020 10:24, J. R. Haigh wrote:
> Hi Replicant team,
> I've recently preördered a PinePine (Community Edition Convergence
> Package, PostmarketOS-branded), and having had a poor e
On the 1st and 2nd of February 2020, 4 Replicant contributors
(FilBerg, GNUtoo, GrimKriegor and dllud) attended FOSDEM
2020[1] in Brussels.
FOSDEM (Free and Open source Software Developers' European
Meeting) is an annual conference organized by volunteers, to enable
users and contributors to meet
Could you please document it at
https://redmine.replicant.us/projects/replicant/wiki/Graphics#Choosing-the-default-software-renderer-on-Replicant-60-0004
?
On 03/07/2020 04:28, Denis 'GNUtoo' Carikli wrote:
> Hi,
>
> I've now pushed this patchset.
>
> Denis.
>
>
>
On 25/01/2020 12:53, a wrote:
> Does it change anything regarding if
> the pinephone is suitable to get
> a ported version of replicant?
It seems suitable for Replicant. Although not ideal.
It will have similar issues to the currently supported phones, like
non-working WiFi and Bluetooth, due to
Lukasz Erecinski from PINE64 just wrote a blog post where he explains in
detail:
- the non-free firmware blobs needed for the PinePhone;
- the type of data connections between the main CPU and the chips that
run non-free firmware.
card.
On 17/01/2020 19:32, dllud wrote:
> Hi everybody,
>
> From those coming to FOSDEM, does anyone have a camera and microphone(s)
> that we could use to livestream the Replicant Meetup[1]?
> I am also CCing Michiel from NLnet and John Sullivan from the FSF, in
> case your or
Hi everybody,
From those coming to FOSDEM, does anyone have a camera and microphone(s)
that we could use to livestream the Replicant Meetup[1]?
I am also CCing Michiel from NLnet and John Sullivan from the FSF, in
case your organizations happen to have such kind of gear.
It would be much useful
Acked-by: David Ludovino
On 03/01/2020 17:50, Denis 'GNUtoo' Carikli wrote:
> Using libagl for everything had the side effect of making it
> impossible to use applications like IceCatMobile, as libagl
> OpenGL implementation was not complete enough. Using LLVMpipe
> fixes that.
>
> Using
Acked-by: David Ludovino
On 02/01/2020 14:44, Denis 'GNUtoo' Carikli wrote:
> From: Andrés Domínguez
>
> When using LLVMpipe by default, some system binaries are too
> slow to make the device usable.
>
> This overrides the OpenGL implementation for the following
> binaries:
> - bootanimation
Starting today (December 27th), the 36th Chaos Communication Congress
(36C3)[1] is taking place in Leipzig. Replicant will be there as part of
the Critical Decentralization Cluster[2].
Replicant’s assembly[3] will feature demos of the current Replicant 6 as
well as the upcoming Replicant 9. It is
Hi Lauren,
Yes, Q2 2019 seems like an achievable deadline.
Regards,
David
On 22/12/2019 15:57, Laurent F wrote:
> Hello,
> Is there an approximate release date for Replicant 9? Is it reasonable
> to expect it during the first half of 2020?
> Best regards,
> Lauren
>
>
new version/revision.
>
> Em 20/12/2019 15:07, dllud escreveu:
>> - Could you rotate the Safari icon? Making the compass needed visible
>> will make it easier to identify the icon.
>
> Done, however Apple itself used transparency in the logo, so these don't
> transl
Another thing that makes the Instragram icon look quite different is
that the white lines inside it are thinner than the original, and are
away from the center.
On 20/12/2019 17:57, dllud wrote:
> Hi Adonay,
>
> Thanks a lot!
>
> * The Good Enough front
> - Add spaces around
he icon smaller and adding it in the corner of K9-Mail logo).
- Add Thorium
On 19/12/2019 02:05, Adonay Felipe Nogueira wrote:
> Hi there,
>
> Following the requests made by dllud, here is a new revision/version
> with .PNGs for preview.
>
> The andOTP and it's non-free counter
Hi Adonay,
Thanks a lot for keeping up the effort! My comments:
* Since there is some blank space on the front of "The Good Enough" and
"The Ugly Hack", how about adding more apps in there? This would balance
the arrangement. You may need to reduce the font size of the labels though.
I was
> Is this the best device you could recommend?
Yes. The i9300 is currently supported on Replicant 6 and will be most
surely supported on Replicant 9, as it is the device where Replicant 9
is being developed upon.
You can also try the N7100 (Samsung Galaxy Note 2), which is supported
on Replicant
Thanks Denis.
Here's my follow-up comments.
> * The [...]
> * The [...]
> * The [...]
> * The [...]
It was omitted on purpose. This is directed, bulleted communication.
It's usual to omit articles in such cases.
>> * Hardware locked with proprietary screws.
>> * Non-replaceable battery.
> The
Thanks a lot for the effort Adonay. Here's a summary of all the comments
I and GNUtoo wrote on IRC.
1. Bullets on the back side need to be reworked. Problems:
- "The Bad subjugation" has fast graphics rendering. But it doesn't have
fast graphics rendering with only free software.
- "The Bad
Acked-by: David Ludovino
On 12/12/2019 22:11, Denis 'GNUtoo' Carikli wrote:
> From: Jeremy Rand
>
> Replicant will soon merge patches to set the default renderer
> for each application:
> - Libagl was previously used for all applications. That prevented
> to use applications like
d be.
On 12/12/2019 23:01, Denis 'GNUtoo' Carikli wrote:
> On Thu, 12 Dec 2019 02:35:34 +
> dllud wrote:
>
>> Sorry, my bad, as Joonas correctly reviewed, the last patch shouldn't
>> be merged.
>> Instead, "ro.libagl=0" should be set in
>> vendor/rep
the system will be too slow.
On 11/12/2019 15:43, dllud wrote:
> The last patch (PATCH 7/7) should be pushed alongside with a new patch
> that includes the content of the following two commits available on
> adjtm's personal repo:
> https://github.com/andresdju/v
The last patch (PATCH 7/7) should be pushed alongside with a new patch
that includes the content of the following two commits available on
adjtm's personal repo:
https://github.com/andresdju/vendor_replicant/commit/19fe4dddff99ba0a12b4ff2545df65562170847b
ps this is an issue you can leave unfixed, if keeping both text and
path is deemed useful.
On 11/12/2019 10:32, Adonay Felipe Nogueira wrote:
> Em 11/12/2019 00:55, dllud escreveu:
>> When I open the Scribus file it tells me that the following font is
>> missing: AR PL UKai CN
Good for printing. I think you can export the final PDF in the correct
colour space.
The only detail that needs a fix is the contributor's list in the
document properties. It currently looks like this:
> * dllud on irc://chat.freenode.net/#replicant
> * Fil Berg on the Replicant mailin
. I would say they should be as far away from the
phone bezel as the button (on the other side) is.
On 08/12/2019 20:33, Adonay Felipe Nogueira wrote:
> Em 08/12/2019 00:21, dllud escreveu:
>> Yesterday, after you left, I and GNUtoo decided it would be better to
>> hang the addon be
Hi Adonay,
Thanks again for keeping up the good work. Sorry that I couldn't reply
in due time at IRC.
> I left a space below the main phrase so as to give room
> for the add-ons.Could you please remove it, and occupy the space with the
> sentence and logo?
Yesterday, after you left, I and
Thanks for looking into it Denis. I hope you can find the time to review
all the rest, there's surely much more to fix.
On 06/12/2019 21:58, Denis 'GNUtoo' Carikli wrote:
>> Tor Browser:
> We'd need to look if it's FSDG compliant. If not the best way to make
> it FSDG compliant would be to make
them right now due to time constraints, as what matters so
far is the content discussion. I will add the logos latter.
On December 6, 2019 7:20:26 PM GMT+00:00, Fil Lupin
wrote:
>Hi dllud,
>thanks you for this work.
>
>
>do you think we could use the real logo of each of those ap
o consider, now that we are going minimal, is whether we
should keep the phone mockup on the banner.
I think we should keep it. It takes little space and adds a lot of context.
On 05/12/2019 02:14, dllud wrote:
> Hi Adonay,
>
> First all a big thanks for stepping in and help out on this.
Hi Adonay,
First all a big thanks for stepping in and help out on this.
For those that want to follow, the long discussions about this are
happening on the #replicant IRC channel between me (dllud) and Adonay
(adfeno).
After looking at the sketch bellow I had the following main comments:
- I
Hi Fil,
Thanks a lot for the effort.
First of all, one important correction. As I tried to explain in a
previous email[1], we got the meaning of the "The Good, the Bad and the
Ugly" wrong at first. As Wikipedia explains[2]:
> the respective phrases refer to upsides, downsides and the parts that
Just spent a couple of hours giving a push to this.
According to the 36C3 assembly organization, the table we will get
should be around 1.40m wide. They cannot tell us the precise size as
there are different models around.
To be on the safe side, I think we should opt for a banner that is
> And maybe nothing is gained
> from a repnonfree system compared to a lineage os system.
Exactly.
> Wrongly I had the
> impression that replicant search for unwanted monitoring pieces of software
> and remove it should they find something.
Replicant searches for all non-free software and
On 06/11/2019 00:37, dllud wrote:
> "The Good enough, the Bad hack, the Ugly subjugation"
Ohhh just a correction. The correct reinterpretation of "The Good, the
Bad and the Ugly" should be something like:
"The Good enough, the Bad subjugation, the Ugly ha
I had a fruitful discussion with Denis about the ideas for the flyer.
This email summarizes our conclusions.
To get everybody on the same page: Fil and I were exploring the idea of
creating a double-sided flyer/handout that would have the mockup of the
front and back sides of a phone on either
The wiki says we can set up WiFi access points in the assembly area for
experiments just like this. Though we have to abide by some rules:
https://events.ccc.de/congress/2019/wiki/index.php/Static:Network#Rules
The demo seems simple and interesting enough to be worth the effort.
It's probably
Sure. I mentioned that on a previous email. In the final version we
should have a line drawing of a generic phone. No need for a bitmap
mockup of a specific model.
On 05/11/2019 14:09, Denis 'GNUtoo' Carikli wrote:
> If the phones are used somehow in the final versions, we'd probably need
> to
Hi TJ,
Thanks for taking your time to explain your reasoning. Much appreciated.
My main remaining objection against writing "Replicant.us" is that all
Replicant branding does not include the ".us". Everywhere throughout the
website/forum there are banners featuring the Replicant logo on the left
Bad luck.
I've just got word from two sources (36C3 assembly organization and
CDC) that there is no way to hang anything from the ceiling on the hall
where we will be located.
Poles (for the banners) would be hard to carry on the airplane, even the
extensible or foldable ones. And that's the
I think there is not enough space for both. Would lead to too much
clutter. IMO the banner should be kept as simple and as direct as
possible. Full information can be offered when people approach the table
and pick a flyer or talk with us.
On 03/11/2019 10:25, Fil Lupin wrote:
> I wonder if we
Hi Jeremy,
Thanks for voicing in.
I am not a big fan of flyers for a couple of reasons:
- Environment: non reusable, meant to be thrown away.
- Hard to predict how many you'll need.
People could later look for the same images on Replocant's website. We would
surelly publish the illustrations
Great idea! Thanks a lot for sharing.
The "Freedom and privacy/security issues" page contains the major points
that make Replicant stand-out from all other Android distros out there.
Finding a way to illustrate it would indeed help visitors understand why
Replicant is needed.
I see that you were
Hi Fil,
Thanks a lot for reviewing this.
> About the url replicant.us, I wonder if it would not be useful to add it
> since I saw recently GNUtoo identified some company using Replicant as its
> name which could create confusion.
Well thought, though I still feel it is unnecessary.
The main
Thanks a lot for helping out!
My comments:
- I liked a lot the "Preparing phone" idea. With it there is no need to
put the Replicant logo inside a phone mockup. It alone conveys the
message that Replicant is for phones. Great!
- The website address "Replicant.us" is not that important.
- Instead
> Canvas Banner - however they can be made from a range of other materials
> such as Vinyl.
> Generally made to order, with options such as metal grommets (holes),
> adhesive grommets (canvas colour, stronger), or pole pockets.
>
> For 183x90cm banner (table size?) you'd need to budget about
Hi everybody,
== Intro (skip if you know all about CCC) ==
As some of you may know, the 36th edition of the Chaos Communication
Congress (36C3)[1] is going to take place on December 27-30 in Leipzig
(Germany). The Chaos Communication Congress (CCC)[2] is one of the
largest hackers' gatherings in
Acked-by: David Ludovino
On 27/10/2019 16:06, dllud wrote:
> Seems good to me.
>
> On 27/10/2019 15:28, Joonas Kylmälä wrote:
>> This should be applied to vendor/replicant.
>>
>> Joonas Kylmälä:
>>> Signed-off-by: Joonas Kylmälä
>>> ---
>
Seems good to me.
On 27/10/2019 15:28, Joonas Kylmälä wrote:
> This should be applied to vendor/replicant.
>
> Joonas Kylmälä:
>> Signed-off-by: Joonas Kylmälä
>> ---
>> CHANGELOG.mkdn | 10 ++
>> config/common.mk | 2 +-
>> 2 files changed, 11 insertions(+), 1 deletion(-)
>>
>>
> wondering how to export clock alarm settings, I did not found the name
> of the app on replicant. In this case, it seems the app is Lockclock.
I use oandbackups or adb backup for that.
If you opt for oandbackups install version 0.2.13. Later versions, on
the 0.3 series, do not work properly on
> My personal suggestion would be Siskin IM, since it has complete OMEMO
> support and does not suffer from bugs like the one for ChatSecure above. You
> can find out more here:
>
> https://siskin.im/
Great tip! Had never heard about this one. Thanks!
Hi Andrés,
Could you also let him know about the problem with the non-free firmware
for the WiFi chip? Perhaps, on a later version of the phone, they can do
something similar to what Purism did with the firmware for the RAM
controller: load the firmware from a separate flash chip, which would
not
Hi Nick,
Yes, Replicant 9 will greatly improve on this area.
On the development build, software rendering is already working a bit
faster than on Replicant 6 (
https://grimkriegor.zalkeen.net/public/alaunch.mp4 ) and we should be
able to squeeze some more performance out of it.
Better still, it
Good to know it no longer uses GCM. Sorry for the outdated info.
Still, if you are starting from scratch, like Fil apparently is, better
opt for a federated network like XMPP or Matrix.
Nick, for XMPP (with OMEMO) on iOS you can use https://chatsecure.org/
Regards,
David
On 16/10/2019 11:48,
Hi Fil,
If I remember correctly Signal uses Google Cloud Messaging or other similar
Google service for push messages. Thus it depends on the non-free Google Play
services. That's the reason why it isn't available on F-Droid.
Furthermore Signal is a centralized service, with all clients
Hi Fil,
Thanks for taking a look at it.
1. I have now removed the Replicant prefix from the pages where it was
clearly redundant. The index looks much better now:
https://redmine.replicant.us/projects/replicant/wiki/index
The only thing left to do is deleting the deprecated pages.
2. The
t
> maybe adtjm, dllud, GrimKriegor or GNUtoo are?
>
> Joonas
>
> ni nhar:
>> After asking the ceo of pine64, the company which
>> manufactures the pinephone, some
>> questions in a pm on the pine64 forum, he answered me.
>>
>> He says, he want
Hi Fil,
That would be perfect! Thanks for the initiative.
Please note down the costs so we may split them later.
Did anyone made an head count? Fil should need to know approximately how
many we are.
Does April have a kitchet or similar where we can prepare the salad?
Regards,
David
On
Hi ni nhar,
Writing that email to pine64 is a good first step.
Then, if you get positive feedback, you can start looking for a
developer that is willing and skillful to do the port.
You do not have to act as a middleman forever, you just have to do the
bridging and connect people.
I am
Hi,
IMHO, before spending Replicsnt funds on buying this device, someone should
first ask the vendor if they are willing to sponsor a phone to a Replicant dev
willing to take this task. Just as Necuno did.
It is quite on the interest of these vendors to have support on multiple OSes.
: Mauro Rossi
Sent: July 15, 2019 9:08:32 AM GMT+01:00
To: dllud
Subject: Re: Does Android-x86 still use Mesa's llvmpipe?
> Previously Android-x86 was explicitly enabling LLVM for swrast (
> https://osdn.net/projects/android-x86/scm/git/external-mesa/commits/61025f0b269c8c31ec76dba5f72d98590d
Hi Fil,
The dates (27-28 July) are already confirmed. I've already got my plane tickets
and Putti too.
The only pending confirmation is the location.
Regards,
David
On June 19, 2019 9:26:05 AM GMT+01:00, Fil wrote:
>Hi all,
>
>On 18/06/19 16:50, Denis 'GNUtoo' Carikli wrote:
>
>> Here's an
Hi again,
Per Michiel Leenaars (NLnet) suggestion I got into contact with Julia
Morawski from Cap Digital. They have nice facilities in a perfect
location and would be willing to host us. Unfortunately their space is
closed during the weekend, which is a no go for us.
April's location (
Hi everyone,
I will prepare a presentation about the graphics stack together with
Grim. That's something I had thought about once we started making
plans to attend the meeting.
However, it seems that the basics of the Android 9 graphics stack is
something that all prospective attendees know
70 matches
Mail list logo
