Se habla de la berberina como la metformina natural, o un equivalente de los fármacos agonistas de GLP-1… Y aunque ...
The post Berberina y Cómo Tomarla: Control de Glucosa, Síndrome Metabólico, Pérdida de Peso… appeared first on Fitness Revolucionario.
Veamos cómo añadir el repositorio oficial de Firefox para instalar la versión Beta del navegador Firefox
En un artículo anterior, ya publiqué cómo poder instalar Firefox versión Nightly en openSUSE, mediante el repositorio oficial que mantiene Mozilla en el que se pone a disposición de los usuarios esta versión del navegador.
Ahora, también han creado un repositorio oficial desde el que podremos instalar Firefox Beta. Estas versiones experimentales del navegador Firefox se pueden tener instaladas junto con la versión estable y convivir sin problemas. Esto nos servirá para probar las novedades de este navegador.
Veamos cómo añadir el repositorio de Mozilla para instalar Firefox Beta en openSUSE. Si ya tienes configurado el repositorio RPM de Mozilla, puedes instalar Firefox Beta mediante zypper. Si no, sigue estos pasos.
Al instalar Firefox beta desde los repositorios oficiales de Mozilla, esto nos ofrece:
Vamos a añadir la firma de seguridad y el repositorio correspondiente. Para ello abrimos una terminal y ejecutamos los siguiente comandos:
sudo rpm --import https://packages.mozilla.org/rpm/firefox/signing-key.gpg sudo zypper ar --gpgcheck-allow-unsigned-repo https://packages.mozilla.org/rpm/firefox mozilla sudo zypper refresh sudo zypper install firefox-beta
El paquete del idioma se tendría que seleccionar automáticamente como dependencia.
Te vuelvo a recordar que puedes tener instaladas las tres versiones del navegador Firefox en tu equipo sin problema y utilizar una u otra cuando los desees, para probar novedades, reportar problemas, o lo que quieras.
Por: Carlos M.
Publicado el 23 de marzo de 2026
Hace tiempo Luis L. García Ventura hizo un simpático remake de Horacio Esquiador para GNU/Linux, el conocido juego en ordenadores de 8 bits.
Para quien lo quiera probar solo tiene que:
Otro juego sencillo que despertará una sonrisa a más de un nostálgico. :D
Hey everyone! So long no talk. It’s been a long time since a proper community update, but rest assured a “full size update” update is coming sometime in April (Charlie the Pinecorn returns!).
We are still planning to migrate to Codeberg for primary git hosting and committing to the move from mediawiki to our documentation site created by community member Funeral. We hope to make this happen sometime this year.
And a message to the team over at Genode, yes I did read your book :) - Caffeine
FOSDEM 2026 was a very productive meetup for members of the PINE64 Community, aside from the occasional shenanigans. We had the opportunity to work on the PineVoice (formally PineVox) and PineTime Pro in person which helped push forward bring-up. There were additional discussions on potential new products and the effect of the DRAM chip shortage.
The PineNote was shown off at FOSDEM with a few demos featuring hrdl’s Arch image and a pre-release image of QuillOS using hrdl’s kernel tree. With a massive thanks to Tom.K, Phantomas and hrdl for staying around and helping demo with his PineNote. Some demos included smoothly playing videos, playing doom (you had to be there to believe it!) along with its capabilities as an actual ebook reader.
Danct12 put together an image for FOSDEM with camera and support for h264 video decoding. The demo also included a copy of big buck bunny and a razor1911 demo.
Currently the DRAM shortage will impact the production of devices like the Pinetab2, PineNote and PinePhone. PineStore founder TL Lim has stated that he doesn’t wish to increase the price of hardware significantly so production is halted for the time being. Any remaining stock will be sold and that will be it for now.
This will not impact devices such as the PineTime, PineBuds, Pinecil or PineVoice.
The new device is an improvement on the original with an AMOLED display, GPS, a custom chip, a digital crown which also features an extra button and new sensors including a blood oxygen sensor. Power to individual components can be cut unlike the non pro watch which will improve battery life.
There has been discussion on if we do fund raising by baking in a small offset cost into the devices; or if we do a service with costs for fund raising. This decision has not been made yet.
More information to come!
Discussions were had concerning compensation and payment for work of developers working on PineStore devices.
Creating a community edition device requires PineStore to create a new SKU for a device, this means that the community needs to agree on purchasing a device at an extra cost as the price of the device will go up (which represents the portion that is going to be donated).
Devices like the PineNote or PineTab 2 are likely not going to get community editions due to this, and we’re very much at PineStores discretion in this regard. As long as a price is organized before a new device reaches production, it is okay. But this process can be difficult if a bulk of the development happens after release hardware production begins.
Donations are messy, sending money overseas is messy, deciding who gets how much is messy. It’s a mess.
The PinePhone 2 is a common topic within the community and was a hot discussion at FOSDEM in 2026. Aside from the current chip shortage, PineStore has determined that it is too high of a financial risk to release another phone. This is because the interest of the mobile Linux community has shifted to porting cheaper and more powerful Android devices to mobile Linux projects such as Sailfish and PostmarketOS.
This will inevitably create a gap in the Linux phone space as the PinePhone is one of the few devices that a user can flash their own bootloader and modem firmware.
However, potential components for another phone were discussed during the trip. A RK3572/6 as a potential SOC and a RedCap 5G modem which has an identical command set to the Quectel EG25-G modem found in the PinePhone/Pro. Though note none of these components are locked in for an actual device.
So to conclude, the PinePhone 2 is currently in limbo for a number of reasons (financial riskiness, DRAM shortage, old Android devices make cheaper and more powerful Linux phones). But hopefully PineStore will eventually bring out another model.
FOSDEM was a great turnout this year and we had a lot of fun meeting and catching up with people in the FOSS space. Thanks to everyone who came to FOSDEM and to those who came to say hi at our stand. Thanks to those who stuck around the stand with us, it made it a lot more enjoyable having you guys around. And of course, A special thanks to TL Lim from PineStore for sponsoring a group of our community members to visit FOSDEM.
If all things go alright (touch wood), a full community update should be out sometime in April (time/motivation permitting :P). See you in a tick!
Do you have news to share with the community? You can have your news posted on this blog by heading over to this tutorial and following the template. All community updates are written in markdown which you can learn how to write here.
If you get stuck, feel free to ask the folks in chat by finding your respective chat platform at https://pine64.org/community/.
Feel free to contact me if you have any concerns about community related topics. This can be about getting project support, sharing project updates, concern about prolonged wait times for support from PineStore (anything after 1-2 weeks) and any general feedback that could help improve the community.
Community manager: camden.b@pine64.org
If you have quality control issues with your device once you receive it, don’t wait, contact PineStore support.
The PineTime Pro was officially announced at FOSDEM26 on the Pine64 stand. The demo was a bit modest (more on that later on), but we were delighted to showcase the first prototype of the “next generation PineTime” along with a demo running on a development board!
We also mentioned the PineTime Pro in the FOSDEM 2026 Update blog post. In this blog post, we would like to provide a more in-depth look at the PineTime Pro.
The PineTime project started in October 2019, that’s more than 6 years ago! Needless to say, the PineTime has been a great success. The community has been very active in developing firmware for the device, companion apps, tools and more. And, according to PineStore, it sells very well.
The reason the PineTime Pro isn’t called the PineTime 2 is because it’s not meant to replace the original PineTime. The original watch still has a lot going for it: it is simple, hackable, efficient and already supported by great community projects like InfiniTime and WaspOS. It will continue production alongside this new model.
The PineTime Pro should be seen as a more powerful, more feature-rich sibling rather than a direct successor. If the original PineTime is a solid open smartwatch platform, the PineTime Pro is our attempt to push that idea much further with new and improved components.
Compared to the “OG” PineTime, the PineTime Pro brings a significant hardware upgrade.
At its core is a dual-core Cortex-M33 SoC, with one application core running at up to 200 MHz and a dedicated Bluetooth core. It also comes with 800 KB of internal SRAM and 8 MB of PSRAM.
Around that MCU, the hardware currently includes:
Yes, it’s still an embedded platform, but much more powerful. Here is a quick comparison between the PineTime and the PineTime Pro:
| OG PineTime | PineTimePro | |
|---|---|---|
| MCU | 1x ARM Cortex-M4 core | 2x ARM Cortex-M33 cores |
| RAM | 64 KB SRAM | 800KB SRAM + 8MB PSRAM |
| Flash | 512KB internal + 4MB SPI | 8MB SQPI |
| Display | 240x240px, 1.3" | 410x502px, 2.13" |
| Sensors | Heart rate + accelerometer | heart rate + blood oxygen sensor, 6D IMU |
| GPS | No | Yes |
| Debug port | Internal | Available on external pin |
Altogether, this opens the door to much more ambitious software (like PebbleOS ;) ) and use cases than what is practical on the original PineTime: fast, smooth and rich UI, fitness tracker, localization and tracking, external apps and watch faces and more!
The PineTime Pro has been in discussion for quite a while. Community members including JF, Gamiee and Ralim have been exploring the idea for a long time, and from the beginning, one thing was clear: choosing the right MCU would make or break the project.
Earlier iterations were based on a RISC-V MCU. In fact, the demo shown at FOSDEM 2024 was based on that platform. While the idea was exciting, we ultimately ran into issues with power consumption along with the quality of the available documentation and SDK. Those limitations made it difficult to see a good long-term path forward.
Things became much more concrete when PineStore started collaborating with a large smartwatch manufacturer in China that had developed its own chip. That collaboration has been very valuable so far: PineStore and the community have been working together on the hardware design, and documentation and SDK materials have been shared to help software development move forward. All of these resources will also be available to the community once the device enters production.
Along the way, we explored a few extra ideas too. For example, we looked at adding LoRa, but that introduced major challenges in terms of PCB space and RF design. A light sensor was also considered, but dropped it for similar reasons. On the other hand, adding a speaker and microphone turned out to be relatively easy, so those ended up becoming a nice bonus.
During FOSDEM 2025, we received the first two development boards based on the new Cortex-M33 platform. Throughout 2025, PineStore and community members, especially Gamiee and Ralim, continued reviewing the hardware design while JF was experimenting with the development board and the SDK.
Toward the end of 2025, the first two actual watch prototypes were sent to Gamiee and JF. Unfortunately, those boards had hardware issues that left the SWD port (the programming and debugging port) non-functional, which made software bring-up much more difficult than expected.
A second batch of prototypes arrived just before FOSDEM this year. We had hoped to show them running on the Pine64 stand, but another hardware issue got in the way: the flash memory was not working properly, so the demo had to run on the development board instead of the actual watch hardware.
That said, progress is still very real. After several rounds of review between PineStore and the community, a third hardware revision is expected at the beginning of April. We’re optimistic that this revision will finally resolve the remaining blockers and let software development ramp up properly.
Just like the original PineTime, we expect the community to enjoy this new device and develop many projects on top of it!
The good news is that developers from both InfiniTime and WaspOS are already involved, which gives the platform a strong starting point. The PineTime Pro is exciting not just because it is new hardware, but because it offers much more room for experimentation. Features that are extremely challenging to fit into the original PineTime due to resource constraints may become practical here.
Can it run Doom? Most probably, and I guess someone will take the challenge and make it happen!
On the InfiniTime side, the original PineTime is not being abandoned. InfiniTime is already a fairly mature project, and it will continue to exist. And I guess the same is true for Wasp-OS.
But realistically, the PineTime Pro is likely to keep developers busy for quite some time, simply because it creates so many new possibilities.
Right now, JF is mostly focused on low-level experiments and validation, with the goal of getting basic drivers and a demo application working as soon as possible. Gamiee is also expected to help with OpenOCD integration once he wraps up work on the PineVoice.
The next major milestone is simple: get the new hardware revision in hand, confirm that the remaining issues are solved, and continue pushing software bring-up forward.
There is still work ahead, and we are not pretending otherwise. But after a long period of exploration and hardware iteration, the PineTime Pro is finally starting to feel real.
We’re looking forward to sharing more as development continues.
Do you have news to share with the community? You can have your news posted on this blog by heading over to this tutorial and following the template. All community updates are written in markdown which you can learn how to write here.
If you get stuck, feel free to ask the folks in chat by finding your respective chat platform at https://pine64.org/community/.
Feel free to contact me if you have any concerns about community related topics. This can be about getting project support, sharing project updates, concern about prolonged wait times for support from PineStore (anything after 1-2 weeks) and any general feedback that could help improve the community.
Community manager: camden.b@pine64.org
If you have quality control issues with your device once you receive it, don’t wait, contact PineStore support.
https://lwn.net/Articles/1063735
Los pasos:
La entrada Side loading 24h se publicó primero en Linux Hispano.
Me han preguntado alguna vez que como se puede bloquear el acceso a vuestras páginas web en un servidor Apache a las IAs, y aunque bueno, teniendo en cuenta que los crawlers de IA son lo más desagradecido y busco del Mundo podemos pedirlo educadamente y luego bloquear por el user agent, de todos modos ya os digo que en un Mundo sin moral, muchos crawlers de IA deleznables se identifican simplemente como firefox, lamentable.
De todos modos os paso el contenido:
en robots.txt (para pedirlo educadamente)
# ── Crawlers de IA / LLM ───────────────────────────────── # OpenAI User-agent: GPTBot Disallow: / User-agent: ChatGPT-User Disallow: / User-agent: OAI-SearchBot Disallow: / # Anthropic User-agent: anthropic-ai Disallow: / User-agent: ClaudeBot Disallow: / User-agent: Claude-Web Disallow: / # Google IA (Gemini / Bard training) User-agent: Google-Extended Disallow: / # Meta User-agent: FacebookBot Disallow: / # Perplexity User-agent: PerplexityBot Disallow: / # You.com User-agent: YouBot Disallow: / # Common Crawl (usado para entrenar LLMs) User-agent: CCBot Disallow: / # Cohere User-agent: cohere-ai Disallow: / # Diffbot User-agent: Diffbot Disallow: / # ByteDance / TikTok User-agent: Bytespider Disallow: / # Apple User-agent: Applebot-Extended Disallow: / # Otros scrapers conocidos User-agent: ImagesiftBot Disallow: / User-agent: magpie-crawler Disallow: / User-agent: DataForSeoBot Disallow: / User-agent: AI2Bot Disallow: / User-agent: Omgilibot Disallow: / User-agent: Timpibot Disallow: / User-agent: FriendlyCrawler Disallow: /
En el .htaccess (para bloquear esos .user-agents)
<IfModule mod_rewrite.c>
RewriteCond %{HTTP_USER_AGENT} (GPTBot|ChatGPT-User|OAI-SearchBot|anthropic-ai|ClaudeBot|Claude-Web|Google-Extended|FacebookBot|PerplexityBot|YouBot|CCBot|cohere-ai|Diffbot|Bytespider|Applebot-Extended|ImagesiftBot|magpie-crawler|DataForSeoBot|AI2Bot|Omgilibot|Timpibot|FriendlyCrawler) [NC]
RewriteRule .* - [F,L]
</IfModule>
Foto de Markus Spiske: https://www.pexels.com/es-es/foto/hombre-policia-uniforme-de-espaldas-4682719/
BollyApagar hilos de la cpu
23 echo "off" > /sys/devices/system/cpu/smt/control
24 htop
25 echo "on" > /sys/devices/system/cpu/smt/control
26 htop
27 echo "off" > /sys/devices/system/cpu/smt/control
28 nproc
29 echo "on" > /sys/devices/system/cpu/smt/control
30 nproc
31 echo "off" > /sys/devices/system/cpu/smt/control
32 lscpu -e
33 echo "on" > /sys/devices/system/cpu/smt/control
34 lscpu -e
35 echo "off" > /sys/devices/system/cpu/smt/control
stopo
2014 sudo apt install hwloc
2015 lstopo-no-graphics
2016 sudo lstopo-no-graphics
2017 sudo lstopo
2018 lscpu
2019 sudo lstopo
2020 history