- Is genj/social-feed-bundle compatible with Laravel?
- No. It is a Symfony bundle with a dependency injection extension, configuration tree, and likely Doctrine entities, while Laravel uses a different container, config repository, and Eloquent ORM. Nothing installs cleanly into a Laravel application as a drop-in dependency. Treat it as a reference implementation rather than a Laravel package.
- Can I install genj/social-feed-bundle with Composer in a Laravel project?
- Composer may resolve the package, but Laravel will not register the Symfony bundle or load its DI extension automatically. You would need a compatibility shim that recreates bundle bootstrapping, config merging, and Doctrine wiring inside Laravel. The effort exceeds a clean rebuild of the small domain, so installation is not recommended.
- What social networks does genj/social-feed-bundle support?
- The 2016 codebase targets providers such as Twitter, Instagram, and Facebook through adapter classes that normalize posts into a common feed model. Every HTTP client points at endpoints and auth flows that have since been retired or replaced, including Twitter API v1.1 timelines and pre-Graph Instagram endpoints. The adapter seams are reusable, but the provider calls must be rewritten against current APIs.
- Is genj/social-feed-bundle still maintained?
- No. The repository is archived, has no release since September 2016, zero dependents, and roughly 16 stars. There is no active security response path for OAuth token handling, credential storage, or dependency vulnerabilities. Do not expect fixes, compatibility updates, or support.
- Can I use genj/social-feed-bundle in production?
- Using it as a live dependency in production is not defensible. It is abandoned, its transitive dependencies such as Guzzle and OAuth libraries are pinned to old versions with known advisories, and its API endpoints are sunset. The safe use is a private fork or code audit to mine the data model and adapter interface.
- What PHP and Symfony versions does genj/social-feed-bundle require?
- The package dates from 2016, so its PHP and Symfony constraints will almost certainly conflict with modern runtimes. Expect to target PHP 8.2 or later and Laravel 11 or 12 for any rebuild. The original constraints should be treated as historical only.
- Does genj/social-feed-bundle handle caching and rate limits?
- Yes, the bundle includes built-in caching to reduce API calls and avoid rate-limit issues. That concept is worth keeping, but the implementation is tied to Symfony configuration and old HTTP clients. In Laravel, reimplement it with the cache repository, Http::retry, and the rate limiter.
- How does genj/social-feed-bundle normalize feed data for templates?
- It fetches posts from each configured provider and converts them into normalized post objects so templates receive a uniform feed structure. The provider-per-network adapter and normalization contract are the most reusable parts of the design. You can carry that shape into Eloquent models such as SocialAccount, SocialPost, and SyncCursor.
- How do I add a custom social network adapter to genj/social-feed-bundle?
- The bundle advertises extensible adapters, so in the original Symfony design you would add a provider class and register it through bundle configuration. In a Laravel rebuild, define a ProviderAdapter interface with methods like authenticate, fetchSince, normalize, and refreshToken, then bind implementations in a service provider. Register each adapter through config and resolve it from the container.
- What should Laravel developers use instead of genj/social-feed-bundle?
- Build a first-party Laravel package or standalone PHP library that reuses the domain model and adapter interface from the bundle. Use Laravel Socialite with community drivers for OAuth handshakes and token refresh, official or well-maintained SDKs for Graph, Instagram, and X, and Http::retry plus the rate limiter for throttling. Start with one provider end to end, such as Facebook or Instagram Graph, then generalize.